Manifest Bundles on Arweave

Package multiple Arweave transactions into a navigable directory structure — accessible via standard HTTP paths. Host entire web applications permanently on the permaweb.

Bundle multi-file experiences into one addressable permanent artifact.

Manifests take Evercore beyond single-file storage and into deployable sites, packaged evidence sets, and structured asset collections.

Value

Publish web experiences, not just files

Static apps, microsites, and bundled records can be served through a structured path map instead of disconnected transaction IDs.

Reduce operational sprawl

Teams can ship one manifest for a multi-file release instead of manually tracking every child asset.

Improve customer-facing permanence

A clean path structure is easier to explain and distribute than raw low-level object references.

Use cases

dApp Hosting

Deploy React, Vue, or Svelte front-ends as a single permanent Arweave artifact. No IPFS pinning, no cloud CDN — permanently accessible via arweave.net.

Documentation Sites

Publish versioned developer documentation that cannot be taken offline. Link to a specific manifest TX ID to guarantee a frozen snapshot of your docs.

NFT Media Bundles

Package NFT metadata, preview images, and full-resolution assets into a single manifest. The manifest TX ID becomes the canonical NFT content reference.

Security guarantees

Deterministic path resolution

Each manifest maps explicit URL paths to immutable Arweave transaction IDs, so the same URL always resolves to the same content snapshot.

Immutable release snapshots

Publishing a new version creates a new manifest TX ID. Previous releases remain intact and verifiable for rollback and audit history.

Gateway-native compatibility

Manifest bundles use Arweave-native structure, enabling standard gateway path routing without custom edge infrastructure.

For operators

• Upload manifests once underlying files already exist and need a stable navigable layer.
• Pair with CDN operations for better delivery behavior on public-facing assets.
• Use ArNS when a manifest should resolve behind a human-readable permanent name.

For buyers

• Ideal for product teams selling permanent hosting, packaged disclosures, or public archives.
• Helpful for customers who need path-based delivery rather than isolated file retrieval.
• Expands the platform story from document retention into web-grade publishing.

Can I update a manifest after publishing?

Manifests are immutable once submitted to Arweave. To 'update' a site, publish a new manifest TX and update your ArNS name to point to the new TX ID. The old version remains accessible via its original TX ID.

What is the arweave-manifest+json format?

A JSON document that maps URL paths to Arweave TX IDs. Arweave gateways resolve manifest paths by fetching the corresponding TX for each path component — enabling multi-file directory structures from a single root TX ID.

Can I use a custom domain with a manifest?

Yes — via ArNS (Arweave Name System). Register a name and point it to your manifest TX ID. Gateways resolve ar://yourname to the manifest and serve files by path.