Skip to blog content

    Quality Crypto Reporting · Primary Sources Researched

    CryptoWorkPro

    Market context

    Powered by CoinStats APIUpdated 8:22 PM

    BTC-0.51%
    $84,385
    ETH-1.25%
    $2,669
    XRP-1.91%
    $1.47
    SOL-0.31%
    $118.01
    BNB-0.38%
    $766.15
    HBAR-3.45%
    $0.0997
    QNT-10.93%
    $229.3
    TRX-0.35%
    $0.3346
    LINK-5.82%
    $13.63
    XLM-3.38%
    $0.2115
    Back to Blog
    NFTs

    The NFT Is in Your Wallet. The Picture Often Lives Somewhere Else.

    Published September 29, 2026

    The token records ownership. The picture is often a linked file. OpenSea metadata labels and IPFS pinning explain why the image can disappear.

    The NFT Is in Your Wallet. The Picture Often Lives Somewhere Else.

    The token in your wallet records that you own a specific item on a blockchain. The picture you see on a marketplace is often a separate file, stored at a link the contract points to. If that link breaks, or the file is taken down, the token can still sit in the wallet while the image is gone.

    This article covers storage, not prices. Ethereum.org describes an NFT as a unique token whose contract tracks ownership and gives each item an ID, with metadata usually attached to describe what the NFT represents. The ERC-721 metadata extension is optional. It uses a function called tokenURI that may point to a JSON file. That file can name the item, describe it, and give another URI for the image.

    What the token records

    On Ethereum, ethereum.org says the pair of contract address and token ID identifies an ERC-721 NFT. The contract can assign ownership and keep that record on the chain. That record is what wallets and marketplaces check when they say you own the item.

    The picture, name, and traits are a different layer. OpenSea's developer docs say the marketplace reads metadata from the URI returned by ERC-721 tokenURI or ERC-1155 uri. That metadata controls the name, media, description, and traits shown for the NFT. The URI can serve JSON from a hosted web address, IPFS, Arweave, or from the contract itself.

    Where the picture usually lives

    OpenSea's metadata storage page lists several methods. A hosted JSON file sits on a server or cloud account the project controls. An IPFS URI starts with ipfs:// and points to content identified by a hash. An Arweave URI starts with ar://. A contract can also return Base64-encoded JSON directly, which OpenSea calls onchain metadata. That last option raises gas costs, so OpenSea says to use it when the metadata is compact.

    IPFS docs for NFT data say a CID identifies a particular piece of content, and that changing the content produces a different CID. They also say copies on IPFS nodes are temporary unless someone pins the data. Pinning tells a node not to delete the files during garbage collection. IPFS's persistence page is direct: the network does not guarantee that any content stays available. If nobody pins the files, they can disappear even though the token still exists.

    What OpenSea's metadata labels mean

    OpenSea's help article dated February 2, 2026, shows a Metadata field on NFT pages. It lists five labels:

    • Fully onchain: all metadata and media are stored on a blockchain. OpenSea calls this the most permanent method and names CryptoPunks, Nouns, Loot, and Autoglyphs as examples.
    • Onchain metadata: the metadata references or is generated from onchain data, but media may be served elsewhere. OpenSea cites Art Blocks generative art and ENS names.
    • Decentralized: metadata stored on IPFS or Arweave.
    • Centralized: metadata on traditional web servers. OpenSea says availability depends on the server owner maintaining access.
    • Unknown: the storage method could not be determined.

    OpenSea says these classifications are determined programmatically and may not be entirely accurate for all projects. A Decentralized label means IPFS or Arweave. It does not mean a pin is guaranteed forever.

    What can go missing

    If the contract points to a web address and that server goes offline, marketplaces may show a broken image even though the ownership record still names your wallet. If the contract points to IPFS and no node pins the CID, the same thing can happen. The token record remains. The linked files are what failed.

    This article does not claim that every NFT image will vanish, or that IPFS and Arweave behave the same way. It reports what the cited docs say about where files live and what persistence requires.

    What remains unknown

    OpenSea does not publish a live accuracy rate for its metadata labels. CryptoWorkPro has not audited any collection's storage, pins, or whether a given contract can later change its tokenURI. Those facts sit in each contract and hosting setup, not in a marketplace badge.

    What to check

    On OpenSea, open the item page and read the Metadata field in Blockchain details. Treat Fully onchain, Decentralized, and Centralized as OpenSea's labels, not as a warranty. If you need the files themselves, look at the tokenURI or uri target, and whether the image URI still loads. None of those checks is a reason to buy or sell.

    Sources

    Disclosure: This article explains how cited NFT standards and marketplace docs describe token records versus linked files. It is not a review of any collection, storage provider, or marketplace, and it does not say any specific image will remain available. This article is not financial, legal, or investment advice. AI-assisted research and writing. Cited sources, not AI alone, support the claims.