Solana Token Not Showing in Phantom? 9 Fixes (2026)

You minted an SPL token, the explorer shows it sitting in your wallet, but Phantom either hides it or labels it "Unknown Token". This is almost always one of six fixable issues.

1. "Hide unknown tokens" is on

Phantom hides any token that isn't on the Jupiter strict list by default. Open Phantom → Settings → Manage token list → toggle off "Hide unknown tokens". Your token appears immediately.

2. Metadata never pinned

If your token has no Metaplex metadata account, Phantom has nothing to render — no name, no symbol, no logo. Check Solscan for your mint. If the "Metadata" tab is empty, you skipped the Metaplex CreateMetadataAccountV3 instruction. Re-mint via SolanaForge which pins metadata to IPFS via Pinata in the same transaction.

3. Image URL is unreachable

Phantom fetches the image from the uri field in your metadata JSON. If you pinned to a private gateway, a dead webserver, or a CID that's no longer pinned, Phantom shows the token name but no logo. Test the URI in a browser — if it 404s, your image is gone.

4. You're on the wrong network

Mainnet tokens don't show up while Phantom is set to Devnet, and vice versa. Top-right of Phantom → check the network dropdown. Devnet airdrops and Mainnet tokens look identical onchain but are stored on different clusters.

5. ATA was never created for this wallet

Sending a token to a wallet that doesn't have an Associated Token Account for that mint requires creating the ATA first (~0.002 SOL rent). Some old senders forget this and the transfer silently fails. Re-send from a wallet that uses createAssociatedTokenAccountInstruction if missing — SolanaForge airdrops handle this automatically.

6. Cache lag

Sometimes Phantom just takes a minute. Force a refresh: pull-to-refresh on mobile, or click your account name → "Refresh" on desktop. Still nothing after 5 minutes? It's one of the five above, not cache.

7. Metadata exists but the JSON is malformed

Phantom reads the uri from your on-chain metadata account, fetches that JSON, and expects at minimum name, symbol and image. If the file is HTML (a gateway error page), has a trailing comma, or serves content-type: text/html, Phantom silently falls back to "Unknown Token" even though metadata technically exists. Open the URI in a browser and confirm you see raw JSON with those three keys.

8. IPFS CID is pinned on one gateway only

A CID that resolves on gateway.pinata.cloud but nowhere else will break the moment that gateway rate-limits you. Test the same CID on ipfs.io and cloudflare-ipfs.com. If only one responds, re-pin it. SolanaForge pins through Pinata and verifies the CID across two independent gateways before finishing your mint, so this failure mode never reaches your holders.

9. Token-2022 mint in an older wallet build

Tokens minted under the Token-2022 program (transfer fees, transfer hooks, metadata extensions) render fine in current Phantom, but old cached builds and some third-party portfolio trackers still only index the classic SPL Token program. Update the wallet app. If you need maximum compatibility across every wallet and bot, mint with the classic SPL Token program instead.

What about Solflare, Backpack and mobile?

The same nine causes apply, with two wallet-specific quirks:

• Solflare caches token metadata harder than Phantom. After fixing metadata, remove and re-add the account, or wait roughly an hour.
• Backpack shows unknown tokens by default but hides the logo until the image URI returns a valid image/* content type.
• Phantom mobile keeps a separate cache from the extension. Fixing it on desktop does not fix it on your phone — force-close the app and reopen.

60-second diagnostic order

1. Toggle off "Hide unknown tokens" in Phantom settings.
2. Confirm you are on Mainnet, not Devnet.
3. Open your mint on Solscan and check the Metadata tab is populated.
4. Open the metadata uri in a browser — you should see raw JSON.
5. Open the image field from that JSON — you should see your logo.
6. Force-refresh the wallet, then wait five minutes.

If steps 3–5 fail, the token itself is the problem and no wallet setting will fix it — the metadata has to be written correctly at mint time.

Bottom line

In order of likelihood: hidden-tokens toggle (60% of cases), missing or broken metadata (25%), wrong network (10%), everything else (5%). Start with the toggle, then check Solscan for metadata. If you want to skip all of this for your next launch, mint with metadata baked in — SolanaForge writes Metaplex v3 metadata, pins your logo to IPFS, and verifies both before it hands the mint back to you. See also: revoke mint authority explained and the Solana token launch checklist.