SPL Token vs Token-2022: Which Should You Use in 2026

Solana has two token programs in active use. Unlike most "v1 vs v2" situations, the older one isn't deprecated, and it's still the right default for most tokens. This post explains how to choose.

Two programs, not two versions

Token-2022 isn't "SPL Token 2.0" replacing the original. They're two separate programs, each deployed on its own, and a token belongs to one or the other for its whole life. A standard SPL mint can't be moved to Token-2022 after it's created. The program you pick at creation is the one your token stays on.

Standard SPL Token is the default for a reason

The original SPL Token program has run unchanged since Solana's early days, and that stability is its main strength. Every wallet, exchange, DEX, indexer and analytics tool supports it, so compatibility is never in question. If your token doesn't need something only Token-2022 offers, standard SPL is the lower-risk choice.

What Token-2022 adds

Token-2022 keeps the same core instructions (transfer, mint, burn, freeze) and adds optional extensions. You choose them at creation and can't change them later. These are the ones that matter most for a typical launch:

Extension	What it does
Transfer fee	Withholds a percentage of every transfer for a fee authority to collect
Interest-bearing	The mint reports a continuously compounding display balance
Metadata on mint	Name/symbol/URI live on the mint account itself, no separate Metaplex account

The full Token-2022 spec has more, including non-transferable ("soulbound") tokens, transfer hooks that run custom program logic on every transfer, and confidential transfers. Tool support for those varies a lot, and many token creators, Solstack included, offer only some of them. Find out what an extension needs before you assume your creator supports it.

How to decide

Use standard SPL Token if you want the widest compatibility, if your token doesn't need an extension, or if you're unsure. It's the cautious default, and it's never a wrong choice.

Use Token-2022 if your token depends on an extension: a fee taken on every transfer, an interest-bearing display balance, or metadata stored on the mint instead of in a separate account. If the extension is the reason for the token, Token-2022 is the only way to have the protocol enforce it. The alternative is off-chain logic.

The compatibility cost

Wallet and exchange support for Token-2022 has caught up a lot in the last couple of years. Phantom, Solflare and Solana Explorer all handle it well. It can still cause trouble with some older third-party tools, a few smaller centralized exchanges, and any integration written on the assumption that every mint uses the original program's fixed account layout. If working everywhere matters more to your launch than any extension, that's reason enough to stay with standard SPL.

You only get to choose once

Since a mint can't move programs afterwards, make the choice on purpose and not by opening whichever creator you found first. If you don't need an extension, use standard SPL. If an extension is central to the token, use Token-2022, and check that your creator builds that particular extension before you commit.

Try either one: the SPL Token Creator for the standard program, or the Token-2022 Creator for transfer-fee and interest-bearing mints. The Token-2022 concepts doc covers the extensions in more depth.