Choosing decentralized storage for a CMS is really a choice about how content is identified, how long it is retained, and how readers retrieve it. IPFS, Arweave, and Filecoin address different parts of that problem. None is a complete replacement for an editorial workflow or a reader-facing website.
Start with a retention policy. Private drafts, frequently corrected pages, final public reports, and long-term archives should not automatically share the same distribution path. Decide what should remain public before deciding where to upload it.
IPFS: content addressing and distribution
IPFS is a content-addressed peer-to-peer file system, not a blockchain. Its content identifiers describe particular data representations. This can be useful for version-specific website releases and portable references to public files. A human-readable domain or gateway is an additional access layer.
Ongoing availability requires retained copies. The IPFS persistence documentation explains pinning and the distinction between identifying content and keeping it available. An unpinned copy can be removed during garbage collection; a CID does not guarantee that another provider will retain the material.
Arweave: an archival storage objective
Arweave is designed around permanent information storage and the permaweb. That makes archival intent central to evaluation. It can be relevant to material deliberately approved for long-term public preservation, but the storage network does not independently supply an editor, permissions policy, or correction interface.
Do not describe permanence as a universal fit or a risk-free guarantee. Review what happens when content is inaccurate, sensitive, or no longer appropriate to recommend. A public index can direct readers to a correction while earlier distributed material may remain accessible. Preserve the distinction between issuing a new edition and deleting an older one.
Filecoin: storage arrangements and retrieval
Filecoin provides a storage marketplace and mechanisms for storage commitments. It can be part of an IPFS persistence arrangement, but it is not synonymous with IPFS or Arweave. Ask how long an arrangement lasts, who maintains it, and how data is actually retrieved for a reader-facing website.
A provider that combines several technologies should still explain each responsibility. Does it retain the original package? Does it serve the content through an online gateway? Can another operator recover the data without the same account? Integration should make those answers clearer, not hide them.
Compare the complete publishing service
| Decision | IPFS-based publishing | Arweave-oriented publishing |
|---|---|---|
| Primary question | Who retains and serves this identified release? | Is this material intended for long-term public preservation? |
| Editorial updates | Publish a new version and update the preferred pointer. | Publish a new edition and keep version relationships clear. |
| Reader access | Configure a gateway or other retrieval route. | Evaluate the gateway and delivery route separately from storage. |
| Cost review | Include retention, bandwidth, delivery, and operations. | Include storage submission, delivery, and surrounding operations. |
| CMS features | Supply editing, approval, taxonomy, and navigation separately. | Supply editing, approval, taxonomy, and navigation separately. |
The table is a planning framework, not a ranking of providers. Current fees and service terms need verification for the particular deployment. Use representative release sizes and test retrieval instead of estimating from a tiny demonstration file.
Domain names are not content addresses
DNSLink can associate a domain with an IPFS path. IPNS can provide a mutable name. ENS and conventional DNS may play different roles in an access design. None of those naming layers means that a particular file is retained or that a gateway is available. Domain control and HTTPS delivery still deserve operational owners.
The IPFS deployment guide distinguishes DNSLink signaling from direct custom-domain hosting. For a broader decision, read Arweave versus IPFS and define your correction, retention, and recovery policies before choosing a destination.
