# Path Manifests

When uploading files to Arweave, each file is assigned its own unique transaction ID. By default these IDs aren't grouped or organized in any particular manner.

Path Manifests are a special kind of Arweave transaction which group files under a single identifier.

# Use Cases

The two most common use cases for path manifests are for NFT collections and building static websites.

Typically, uploading 100 images to Arweave would result in 100 different transaction IDs.

Path Manifests are a way to link multiple transactions together under a single base transaction ID and give them human readable file names. In relation to the cat example, you could have one base transaction ID to remember and use it like a folder - accessing your cat pictures with more memorable filenames like {base id}/cat1.jpgopen in new window, {base id}/cat2.jpgopen in new window, etc.

Creating grouped sets of readable file names is essential for creating practical applications on Arweave, and unlocks the ability to host websites or other file collections as explored in the examples below.

# Examples

Any time you need to group files in a hierarchical way, manifests can be useful. For example:

• Storing NFT collections:
  • https://arweave.net/X8Qm…AOhA/0.pngopen in new window
  • https://arweave.net/X8Qm…AOhA/1.pngopen in new window

This mirrors the common base path approach used by NFT collections when linking to NFT images and metadata on a storage API or IPFS.

• Hosting websites:
  • https://arweave.net/X8Qm…AOhA/index.html
  • https://arweave.net/X8Qm…AOhA/styles.css
  • https://arweave.net/X8Qm…AOhA/public/favicon.png

# Manifest Structure

Path Manifests are a special format of transaction created and posted to Arweave using the Tags:

{ name: "Content-type", value: "application/x.arweave-manifest+json" }

and having JSON formatted transaction data that matches the example below.

{
  "manifest": "arweave/paths",
  "version": "0.2.0",
  "index": {
    "path": "index.html"
  },
  "fallback": {
    "id": "cG7Hdi_iTQPoEYgQJFqJ8NMpN4KoZ-vH_j7pG4iP7NI"
  },
  "paths": {
    "index.html": {
      "id": "cG7Hdi_iTQPoEYgQJFqJ8NMpN4KoZ-vH_j7pG4iP7NI"
    },
    "js/style.css": {
      "id": "fZ4d7bkCAUiXSfo3zFsPiQvpLVKVtXUKB6kiLNt2XVQ"
    },
    "css/style.css": {
      "id": "fZ4d7bkCAUiXSfo3zFsPiQvpLVKVtXUKB6kiLNt2XVQ"
    },
    "css/mobile.css": {
      "id": "fZ4d7bkCAUiXSfo3zFsPiQvpLVKVtXUKB6kiLNt2XVQ"
    },
    "assets/img/logo.png": {
      "id": "QYWh-QsozsYu2wor0ZygI5Zoa_fRYFc8_X1RkYmw_fU"
    },
    "assets/img/icon.png": {
      "id": "0543SMRGYuGKTaqLzmpOyK4AxAB96Fra2guHzYxjRGo"
    }
  }
}

Path Manifests also offer a fallback attribute, an object that accepts the sub attribute id, which defines an Arweave data item transaction id for the resolver to fall back to if it fails to correctly resolve a requested path.

# Source and Further Reading

• Arweave Docsopen in new window