The JSON file referenced by an NFT's metadata URI that contains the full description, image URL, attributes, and properties. Typically stored on Arweave (permanent, ~$0.01), IPFS/Filecoin, or Shadow Drive. The JSON schema follows the Metaplex standard: name, description, image, animation_url, attributes[], properties{files[], category}.
Start with the shortest useful explanation before going deeper.
The JSON file referenced by an NFT's metadata URI that contains the full description, image URL, attributes, and properties. Typically stored on Arweave (permanent, ~$0.01), IPFS/Filecoin, or Shadow Drive. The JSON schema follows the Metaplex standard: name, description, image, animation_url, attributes[], properties{files[], category}.
Use the quick analogy first so the term is easier to reason about when you meet it in code, docs, or prompts.
Think of it as a building block that connects one definition to the larger Solana system around it.
Place the term inside its Solana layer so the definition is easier to reason about.
SPL assets, token standards, metadata, and NFT primitives.
Turn the term from vocabulary into something operational for product and engineering work.
This term unlocks adjacent concepts quickly, so it works best when you treat it as a junction instead of an isolated definition.
Use this compact block when you want to give an agent or assistant grounded context without dumping the entire page.
Off-Chain Metadata (JSON) (off-chain-metadata)
Category: Token Ecosystem
Definition: The JSON file referenced by an NFT's metadata URI that contains the full description, image URL, attributes, and properties. Typically stored on Arweave (permanent, ~$0.01), IPFS/Filecoin, or Shadow Drive. The JSON schema follows the Metaplex standard: name, description, image, animation_url, attributes[], properties{files[], category}.
Related: Token Metadata Standard, Arweave, IPFSUse glossary context, relationships, mental models, and builder paths to get structured answers instead of generic chat output.
Optional: paste Anchor, Solana, or Rust code so the Copilot can map primitives back to glossary terms.
The Copilot will answer using the current term, related concepts, mental models, and the surrounding glossary graph.
These branches show which concepts this term touches directly and what sits one layer beyond them.
The convention for structuring NFT metadata established by Metaplex. On-chain: name (32 chars), symbol (10 chars), URI, creators, seller_fee_basis_points, collection. Off-chain JSON (at the URI): name, description, image, animation_url, external_url, attributes array [{trait_type, value}], and properties (files, category).
A decentralized permanent storage protocol that uses a blockchain-like structure called the blockweave and a one-time upfront payment model (no recurring fees) to store data indefinitely, backed by an endowment mechanism. In the Solana ecosystem, Arweave is the dominant off-chain storage layer for NFT metadata JSON and media files, and is used by Metaplex's Bundlr/Irys integration to upload assets cheaply in bulk before minting, with URIs of the form ar://<txid> or https://arweave.net/<txid> stored in on-chain metadata accounts.
A peer-to-peer hypermedia protocol that addresses content by cryptographic hash (CID) rather than location, so the same content always resolves to the same CID regardless of which node serves it. In Solana NFT contexts, IPFS is used as an alternative to Arweave for storing off-chain metadata and media, commonly accessed via pinning services like Pinata or NFT.Storage; however, content availability depends on active pinning, making it less permanent than Arweave's endowment model without a dedicated pinning arrangement.
These are the next concepts worth opening if you want this term to make more sense inside a real Solana workflow.
These entries are easy to mix up when you are reading quickly, prompting an LLM, or onboarding into a new layer of Solana.
The Metaplex Token Metadata program (metaqbxxUerdq28cj1RbAWkYQm3ybzjb6a8bt518x1s) that attaches rich metadata to any SPL token or NFT. It creates a PDA-derived metadata account storing: name, symbol, URI (pointing to off-chain JSON), creators array, seller fee basis points, and collection info. The de facto standard for NFT metadata on Solana.
The account authorized to modify an NFT's or token's on-chain metadata, including name, symbol, URI, and attributes. In Metaplex's token metadata standard, this authority can update mutable metadata fields. Revoking or transferring update authority is a trust signal — immutable metadata means the creator cannot alter the NFT's properties post-mint.
A Token-2022 extension that stores token metadata (name, symbol, URI, and custom key-value pairs) directly on the mint account instead of requiring a separate Metaplex metadata account. Reduces account creation costs and simplifies token setup. The update authority can modify metadata fields after creation.
Glossary entries become useful when they are connected. These links are the shortest path to adjacent ideas.
The convention for structuring NFT metadata established by Metaplex. On-chain: name (32 chars), symbol (10 chars), URI, creators, seller_fee_basis_points, collection. Off-chain JSON (at the URI): name, description, image, animation_url, external_url, attributes array [{trait_type, value}], and properties (files, category).
A decentralized permanent storage protocol that uses a blockchain-like structure called the blockweave and a one-time upfront payment model (no recurring fees) to store data indefinitely, backed by an endowment mechanism. In the Solana ecosystem, Arweave is the dominant off-chain storage layer for NFT metadata JSON and media files, and is used by Metaplex's Bundlr/Irys integration to upload assets cheaply in bulk before minting, with URIs of the form ar://<txid> or https://arweave.net/<txid> stored in on-chain metadata accounts.
A peer-to-peer hypermedia protocol that addresses content by cryptographic hash (CID) rather than location, so the same content always resolves to the same CID regardless of which node serves it. In Solana NFT contexts, IPFS is used as an alternative to Arweave for storing off-chain metadata and media, commonly accessed via pinning services like Pinata or NFT.Storage; however, content availability depends on active pinning, making it less permanent than Arweave's endowment model without a dedicated pinning arrangement.
These entries live beside the current term and help the page feel like part of a larger knowledge graph instead of a dead end.
The original Solana Program Library token program (TokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5DA) that implements fungible and non-fungible token operations. It manages mints (token definitions) and token accounts (balances). Core instructions include InitializeMint, MintTo, Transfer, Burn, Approve (delegation), and Revoke. All SPL tokens on mainnet before Token-2022 use this program.
Solana Program Library—a collection of on-chain programs and client libraries maintained by Solana Labs. Key SPL programs include Token, Token-2022, Associated Token Account, Memo, Name Service, Stake Pool, and Account Compression. SPL programs are deployed to well-known addresses and serve as the standard building blocks for Solana applications.
The next-generation token program (TokenzQdBNbLqP5VEhdkAS6EPFLC1PHnBqCXEpPxuEb) that extends SPL Token with configurable extensions. Extensions include transfer fees, confidential transfers, transfer hooks, permanent delegate, non-transferable tokens, interest-bearing tokens, metadata, and more. Token-2022 is backwards-compatible with SPL Token for basic operations.
An on-chain account defining a token type. A mint specifies: supply (total minted), decimals (0 for NFTs, 6 for USDC, 9 for most tokens), mint authority (who can mint), and optional freeze authority. Each unique token (USDC, JitoSOL, etc.) has exactly one mint account. Mint address serves as the token's unique identifier.