Token-2022 Metadata Extensions: MetadataPointer and TokenMetadata Explained

Every SPL token needs somewhere to keep its name, symbol and logo, because the mint account itself only holds numbers: supply, decimals and authorities. Where that metadata lives is one of the more confusing differences between the original SPL Token program and Token-2022, and it's good to understand before you choose between them.

The original way: a separate Metaplex account

Standard SPL tokens have no built-in place for metadata. The standard everyone uses, and that nearly every wallet and explorer reads, is a Metaplex Token Metadata account. It's a separate on-chain account at an address derived from the mint, created and controlled by the mint's update authority. A wallet derives that address from the mint, reads the name, symbol and URI, and then fetches the JSON and image the URI points to, which usually live on Arweave.

This works well and is supported everywhere. It is an extra account, though, which means extra rent, an extra instruction to create it and an extra lookup for anything that wants to know what the token is called.

The Token-2022 way: metadata on the mint

Token-2022 has two related extensions that put the metadata inside the mint account:

• MetadataPointer, a small field on the mint that says where its metadata lives. It usually points to the mint itself.
• TokenMetadata, the name, symbol and URI, stored as extension data added to the end of the mint account.

So you get one account instead of two. A Token-2022 mint with on-chain metadata holds both its numbers and its identity in a single account, with no separate Metaplex account to derive, create and pay rent for.

The tradeoff is compatibility

On-mint metadata can do everything Metaplex metadata does. What it lacks is Metaplex's years of support. Every wallet, explorer and marketplace knows how to read a Metaplex account. Token-2022's on-mint metadata is newer. Major wallets (Phantom, Solflare) and Solana Explorer support it well, but some older tools, a few smaller exchanges and indexers built before the extension existed may still look in the wrong place.

If you want the token to show up correctly everywhere with no surprises, standard SPL with Metaplex metadata is still the safer default. If you're choosing Token-2022 anyway for another extension, such as a transfer fee or an interest-bearing balance, you get on-mint metadata as part of that choice, and support keeps getting better.

What happens when you create a mint

You don't pick MetadataPointer and TokenMetadata separately. A Token-2022 mint created with on-chain metadata gets both, in the same transaction that creates the mint. There's no separate "attach metadata later" step as there sometimes is with Metaplex. The name, symbol and image URI go in at creation along with any other extensions you chose.

Changing the metadata later needs the mint's metadata update authority. The authority model is the same as with Metaplex. Only the account layout differs.

Choosing between the two

If you haven't decided which program to use at all, metadata usually isn't what decides it. The question is whether you need one of Token-2022's other extensions. SPL Token vs Token-2022: which should you use in 2026 compares them in full. If you've settled on Token-2022, the Token-2022 Creator builds the mint, its extensions and its on-mint metadata in one signed transaction, and the Token-2022 Creator docs go through every field.