What is Metaplex Token Metadata? (Plain English)

When you see a token on Solscan with a name like "BONK", a logo, and links to Twitter/Telegram, that information doesn't come from the SPL Token Program — it comes from Metaplex. This guide explains how the two programs work together and why metadata matters.

The two-program architecture

Solana's token system is split across two on-chain programs:

| Program | What it stores | |---|---| | SPL Token Program | Supply, decimals, mint authority, freeze authority | | Metaplex Token Metadata Program | Name, symbol, image URI, description, social links, update authority |

Each token has both:

• A mint account (in the SPL Token Program) — the technical identity
• A metadata account (in Metaplex) — the human identity

These two accounts are linked: the metadata account stores the mint address it describes, and tools like Solscan look up both when displaying a token.

Why two programs instead of one? Solana's design encourages composability through separate, focused programs. The SPL Token Program is minimal and battle-tested; Metaplex evolved separately to handle the richer requirements of NFTs and metadata, and the same standard naturally applied to fungible tokens.

What's actually in a metadata account

The Metaplex metadata account stores a structured set of fields:

• name — display name (e.g., "Bonk")
• symbol — ticker (e.g., "BONK")
• uri — link to off-chain JSON with full metadata (image, description, attributes, social links)
• sellerFeeBasisPoints — for NFTs, the royalty rate (irrelevant for fungible tokens)
• creators — list of wallet addresses with optional verified flag (used in NFT royalty splits)
• isMutable — boolean: can the metadata still be updated?
• updateAuthority — wallet address allowed to modify the metadata

The on-chain part is small — name, symbol, URI, plus pointers. The full metadata (image, description, links) lives off-chain at the URI, typically on IPFS or Arweave.

The off-chain JSON

When you click a Solana token on Solscan and see its image and description, here's what's happening:

1. Solscan reads the metadata account from Metaplex
2. It pulls the uri field, which points to a JSON file (e.g., https://cf-ipfs.com/ipfs/bafy...)
3. It fetches that JSON, which looks like:

{
  "name": "Bonk",
  "symbol": "BONK",
  "description": "The first Solana dog coin for the people, by the people",
  "image": "https://arweave.net/hash-to-image",
  "extensions": {
    "twitter": "https://twitter.com/bonk_inu",
    "telegram": "https://t.me/bonkonsolana",
    "website": "https://bonkcoin.com"
  }
}

4. Solscan renders the image and links

Implication: if the IPFS gateway is slow or the image host goes down, your token displays without an image. This is why projects pin metadata to robust storage (Arweave is permanent, IPFS via Pinata or Cloudflare gateways is reliable).

Update authority — the third token authority

When you launch a Solana token via Alchemii or any creator tool, you'll see three "revoke" toggles:

• Mint authority (guide) — controlled by SPL Token Program
• Freeze authority (guide) — controlled by SPL Token Program
• Update authority — controlled by Metaplex Token Metadata Program

Update authority is the wallet that can:

• Change the token's name, symbol, or image URI
• Mark the metadata as mutable or immutable
• Transfer update authority to another wallet
• Revoke update authority (set it to null)

If update authority is active, the holder can rename your token — for example, changing "BONK" to "STOLEN_BONK_v2" or repointing the image URI to a malicious image. This is why some projects revoke update authority after their branding is final.

But unlike mint/freeze authority, update authority has legitimate ongoing uses:

• Fixing a typo in the description
• Updating the image to a higher-resolution version
• Adding a Twitter handle that didn't exist at launch
• Migrating image hosting from cheap IPFS to permanent Arweave

So the right strategy depends on your token type:

| Token type | Update authority | |---|---| | Memecoin (final branding at launch) | Revoke after launch + final QA | | Project token (may need updates) | Keep active, on a multisig | | Stablecoin / regulated asset | Keep active for compliance updates | | NFT collection | Required for some collection-level operations |

How isMutable interacts with update authority

The isMutable flag is a separate gate. Even if update authority is active, the metadata can't be changed if isMutable: false.

| isMutable | Update auth active | Can metadata change? | |---|---|---| | true | yes | yes | | true | revoked (null) | no (no one to authorize) | | false | yes | no (locked even with active auth) | | false | revoked (null) | no (double-locked) |

For maximum trust signal: set isMutable: false AND revoke update authority. This means "no one, including the original creator, can ever change this token's metadata."

Why Metaplex matters for memecoin launches

Some less-known token creator tools mint the SPL token but skip Metaplex metadata creation. The result: your token has supply and decimals on-chain, but no name, symbol, or image. Solscan shows it as Unknown Token with the raw mint address.

This is bad for adoption because:

• Buyers don't see a recognizable token in their wallet
• Aggregators like Jupiter need metadata to display the token in swap UIs
• DexScreener can't render a logo on the pair page
• Centralized exchanges won't list a token without metadata

Reputable creators (including Alchemii) bundle Metaplex metadata creation into the token mint transaction, so your token has all three account types — mint account + metadata account + token account — created in one click.

How to update Metaplex metadata after launch

If your update authority is still active, you can update metadata via:

1. The official Metaplex CLI: npx @metaplex-foundation/sugar (originally for NFTs, also works for fungible tokens)
2. Programmatically with @metaplex-foundation/mpl-token-metadata
3. Via wallet UIs — Phantom and Solflare expose a basic update flow for tokens you own

The transaction calls Metaplex's UpdateMetadataAccountV2 instruction. Costs are minimal (~0.001 SOL).

Common questions

Does Metaplex add to the cost of creating a token? Yes — the metadata account requires ~0.0144 SOL of rent (one-time, returned if you ever close the account). It's already factored into our cost breakdown.

Where should I host my image? Best to worst:

• Arweave — permanent, paid once, reliable
• IPFS via Pinata or Cloudflare — reliable but you pay for pinning
• IPFS via free public gateways — works but slow and unreliable
• Direct HTTPS hosting — works but if your domain expires, the image breaks

For memecoin launches, Pinata IPFS is a good cost/quality balance.

Can a token have multiple metadata accounts? No — there's exactly one metadata account per mint, derived deterministically from the mint address.

What happens if my image URI breaks? The token still works on-chain (transfers, swaps, etc.), but Solscan/wallets show a broken image placeholder. You can fix it by updating the URI if your update authority is still active.

Are NFTs and fungible tokens both Metaplex? Yes. Both use the Token Metadata Program. The difference is the tokenStandard field: NFTs are NonFungible or ProgrammableNonFungible, memecoins are Fungible.

Why doesn't the SPL Token Program just include metadata? Solana's design philosophy keeps programs minimal and composable. SPL Token handles fungibility/balances; Metaplex handles metadata. Same reason Linux has separate utilities for "list files" vs "edit files" instead of one mega-tool.

---

Launching a Solana token? Alchemii's Token Creator handles SPL Token + Metaplex metadata in a single transaction — no need to call them separately. If it's a memecoin, our pre-configured meme coin tool bundles the same flow with memecoin-friendly defaults. For the full launch playbook, see our Solana memecoin launch checklist.