Storage is cheap. Persistence is not. IPFS and Arweave both answer a real problem, but they encode different payment models, and that difference decides where each one belongs in a stack.
IPFS: Write once, pay forever (or not)
IPFS resolves content by CID, a deterministic hash of the file. Deduplication is automatic; two nodes holding the same block can trade it over Bitswap. Write access costs nothing. Gateways like ipfs.io make HTTP-based retrieval work without a node.
The protocol stops there. IPFS does not specify retention. Nobody pays for your blocks. A file with zero pins is equivalent to a file that does not exist, because DHT lookups only return provider records from online peers that actually have the blocks. The persistence burden is externalized to pinning services (Pinata, Filebase) or to Filecoin deal markets.
Filecoin tries to rebundle that cost: clients pay storage miners, who prove continued storage via Proof-of-Replication and Proof-of-Spacetime. The economic shape is clear:
- IPFS alone: free writes, opt-in persistence, garbage collection risk.
- IPFS + Filecoin: recurring rent per byte per epoch.
Pricing depends on deal negotiation, not on the protocol. For mutable content, this is workable. For a dataset you write once and update every hour, the cost model is fair. But for a static proof-of-existence record, you keep paying rent for the same bits year after year.
Arweave: Pay once, forget forever
Arweave is an append-only blockweave. Every new block references both the previous block and a random older block. Consensus uses Succinct Proofs of Random Access, so miners have an economic reason to retain old blocks, not just the latest one. A transaction you submit is bundled, mined, and then kept as part of the weave indefinitely.
The fee is upfront. That fee splits between the miner who includes it and a storage endowment. Arweave's pricing mechanism targets a ratio between the cost of storing the weave and the size of the endowment, with a plan that estimates 200 years of coverage.
The economic shape is inverted:
- Arweave: one-time CapEx, zero marginal cost forever.
For immutable data (NFT metadata, artifact archives, software release hashes), Arweave is mathematically cheaper after a single continued-retention interval. For data you rewrite constantly, you pay the full write cost every time. Arweave's GraphQL interface and ANS-104 bundles improve write throughput, and wildcard retrieval makes any transaction fetchable by ID, but the economics do not love hot mutable state.
Selecting by lifecycle, not hype
Use IPFS/Filesystem when:
- you have a dynamic dataset with frequent updates;
- you need content-addressing per version, but you can tolerate a pinning layer;
- you accept IPNS propagation delays (seconds to minutes) as the price of mutable references.
Use Arweave when:
- your data is write-once, read-many;
- you need a tamper-evident timestamp for a registry or claim;
- you want to remove the recurrence of storage billing from your operating budget.
The real scoring is by retention interval and write frequency. Run this yourself: take a 10 MB test file, pin it at Pinata's free tier, collect six months of per-GiB pricing, then pull Arweave's current per-byte cost from https://arweave.net/price/10485760. Compare total cost of ownership over 1, 5, and 10 years. That will be more honest than any vendor claim.
Both projects are open-source and license-progressive. Neither is a replacement for the other. The question is whether you want physics-style permanence or software-style mutability. Pick the one whose cost curve matches your data's lifetime.
Top comments (0)