# NFTs and IPFS: a content address is not a storage guarantee IPFS content identifiers identify content addressed data, but do not guarantee that a reachable node will retain and serve it forever. An NFT can reference IPFS metadata or media while its ownership stays on Ethereum. Check the token’s actual URI, whether the referenced data is pinned and whether the contract can change that URI; these are different durability questions. Evidence: [IPFS content addressing](https://docs.ipfs.tech/concepts/content-addressing/); [IPFS persistence and pinning](https://docs.ipfs.tech/how-to/pin-files/); [ERC-721 NFT standard](https://eips.ethereum.org/EIPS/eip-721) Canonical: https://degreesofsatoshi.com/encyclopedia/nft-ipfs-storage/ Published: 2026-10-02 Substantively modified: 2026-10-02 Independently verified by an automated reviewer: 2026-10-02T19:27:58.939Z Data current through: 2026-10-02 AI-assisted research and drafting with a separate automated source-verification pass; no external expert or named human review is implied. ## Key facts - **Content identity:** A CID identifies content within a specified encoding and structure. ([IPFS content addressing](https://docs.ipfs.tech/concepts/content-addressing/)) - **Availability:** Pinning protects retained data from a node’s garbage collection. ([IPFS persistence and pinning](https://docs.ipfs.tech/how-to/pin-files/)) - **Pointer:** An ERC-721 metadata URI can refer to offchain content. ([ERC-721 NFT standard](https://eips.ethereum.org/EIPS/eip-721)) ## An identifier is not a storage contract Content addressing lets software verify that retrieved data corresponds to the requested identifier. It does not create an obligation for every node to store that data. If no reachable provider retains it, retrieval can fail. Different chunking, codecs or directory layouts can produce different CIDs for representations of the same apparent file. Avoid treating the CID as a universal hash of the original file bytes. Evidence: [IPFS content addressing](https://docs.ipfs.tech/concepts/content-addressing/); [IPFS persistence and pinning](https://docs.ipfs.tech/how-to/pin-files/) ## Metadata and the image may have separate dependencies Suppose an NFT points to an IPFS metadata file whose image field points to another IPFS object. Keeping only the metadata accessible does not establish that the separate image is retained. Check both references and the pinning arrangement. A gateway failure can also prevent one browser path from loading data that other providers still have. Distinguish one inaccessible gateway from proven loss of every copy. Evidence: [ERC-721 NFT standard](https://eips.ethereum.org/EIPS/eip-721); [IPFS content addressing](https://docs.ipfs.tech/concepts/content-addressing/); [IPFS persistence and pinning](https://docs.ipfs.tech/how-to/pin-files/) ## Inspect who keeps the data available Pinning can be local or handled by a remote service. A recursive pin retains referenced children in that object’s data structure, but unrelated URLs inside a metadata document need their own handling. Check the actual retention setup rather than rely on the word IPFS. Finally, immutable content at one CID does not automatically make the NFT’s pointer immutable. The collection contract determines whether token metadata references can later change. Evidence: [IPFS persistence and pinning](https://docs.ipfs.tech/how-to/pin-files/); [ERC-721 NFT standard](https://eips.ethereum.org/EIPS/eip-721) ## Questions ### Does minting an NFT automatically pin its image? No. Token creation and storage retention are separate operations. A project must arrange for the referenced content to remain available. Evidence: [ERC-721 NFT standard](https://eips.ethereum.org/EIPS/eip-721); [IPFS persistence and pinning](https://docs.ipfs.tech/how-to/pin-files/) ### Can I rely on one working gateway as proof of permanent storage? No. It demonstrates current retrieval through that route. Long-term availability depends on retained copies and reachable providers. Evidence: [IPFS persistence and pinning](https://docs.ipfs.tech/how-to/pin-files/) ## Claims and scope ### nft-ipfs-storage-quick-answer IPFS content identifiers identify content addressed data, but do not guarantee that a reachable node will retain and serve it forever. An NFT can reference IPFS metadata or media while its ownership stays on Ethereum. Check the token’s actual URI, whether the referenced data is pinned and whether the contract can change that URI; these are different durability questions. Scope: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null} ### nft-ipfs-storage-fact-content-identity Content identity: A CID identifies content within a specified encoding and structure. Scope: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null} ### nft-ipfs-storage-fact-availability Availability: Pinning protects retained data from a node’s garbage collection. Scope: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null} ### nft-ipfs-storage-fact-pointer Pointer: An ERC-721 metadata URI can refer to offchain content. Scope: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null} ## Sources - [IPFS content addressing](https://docs.ipfs.tech/concepts/content-addressing/) — IPFS contributors. A CID identifies content rather than promising a continuously available server. Locator: Content identifiers; content addressing. Retrieved: 2026-10-02T18:55:25.788Z. - [IPFS persistence and pinning](https://docs.ipfs.tech/how-to/pin-files/) — IPFS contributors. Availability depends on nodes retaining and serving content; pinning prevents local garbage collection. Locator: Pinning; garbage collection; remote pinning. Retrieved: 2026-10-02T18:55:25.704Z. - [ERC-721 NFT standard](https://eips.ethereum.org/EIPS/eip-721) — Ethereum Improvement Proposals. Ownership, receiver checks, token-level and operator approvals, mint/burn event semantics. Locator: safeTransferFrom; approve; setApprovalForAll; Transfer; metadata. Retrieved: 2026-10-02T18:55:25.399Z. ## Revision history - 2026-10-02: First publication after primary-source research and separate automated verification. ## Cite this entry Degrees of Satoshi editorial project. “NFTs and IPFS: a content address is not a storage guarantee.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/nft-ipfs-storage/