The Register Every strike, burn, and pool — ranked on-chain. Reputation you can check, not claim. See the ledger →
Solana
SolForger

Token creation

Solana Token Shows Unknown or No Logo in Phantom: How to Fix

Phantom shows a token as Unknown when it finds no metadata, and with no logo when the URI or image link is broken. How to diagnose and fix each case on-chain.


Key takeaways

  • A Solana token shows as Unknown in Phantom when Phantom cannot find metadata for it: no Metaplex Token Metadata account, no Token-2022 metadata on the mint, and no entry in the deprecated Solana Labs token list.
  • A Solana token that shows a name but no logo in Phantom has on-chain metadata whose URI is empty, unreachable, or does not lead to a JSON file with a working image link.
  • The update authority of a Solana token's metadata, Metaplex or Token-2022, can fix a missing logo by pointing the metadata URI at a valid JSON file, which costs 0.1 SOL on SolForger's metadata tool, as long as the metadata has not been made immutable.
  • Creating a Metaplex metadata account for an existing Solana token requires the mint authority's signature, so a token that never had metadata cannot be given it by its creator after mint authority is revoked.
  • For a Token-2022 token, Phantom reads the name and symbol stored on the mint and takes the logo from the image field of the JSON file at the metadata URI.

Phantom shows a token as “Unknown” when it can’t find any metadata for it. That means no Metaplex metadata account and no Token-2022 metadata on the mint, so Phantom can show the balance but has no name, symbol, or logo to display. A token that shows its name but no logo has a different fault. The metadata exists, but the URI it holds doesn’t lead to a JSON file with a working image link. Both are fixed on-chain by whoever holds the token’s update authority, for example with an update through the metadata tool (0.1 SOL). The exceptions are locked metadata, and a token that never had metadata and whose mint authority is already revoked.

This guide walks through how Phantom decides what to show, how to diagnose your token in a few minutes, and how to fix each cause.

How Phantom decides what to display

Phantom’s token display docs describe a fixed lookup order:

  1. Metaplex Token Metadata account. Phantom looks first for the metadata account that the Metaplex Token Metadata program derives from your mint. It holds the name, the symbol, and a metadata URI pointing to a JSON file. Phantom uses the on-chain name and symbol even if the JSON says something different.
  2. The JSON file. Phantom follows the uri to an off-chain JSON file and takes the logo from its image field.
  3. Token-2022 metadata. For a Token-2022 token that stores metadata on the mint itself, Phantom reads the name and symbol from the mint and still follows the uri for the image. It assumes the JSON follows the Metaplex standard.
  4. Fallback. If there is no metadata account, Phantom checks the Solana Labs token list, which is deprecated and closed to new tokens. If the token isn’t there either, it shows as “Unknown”.

So there’s a chain: mint → metadata (name, symbol, URI) → JSON file → image. If it breaks at the first link, you get “Unknown”. If it breaks at any later link, you get a name with no logo.

One other check runs on top of all this. Phantom’s trust and safety systems can hide a token or show it with a warning even when its metadata is perfect. That is covered separately below.

Diagnose it in a few minutes

  1. Copy the mint address, not the ticker.
  2. Paste it into the certificate. It reads the chain live and tells you which token program the mint uses (SPL Token or Token-2022). It also says whether the token has Metaplex metadata at all, and if so whether that metadata is editable or locked. “No Metaplex metadata” on a classic SPL token is your “Unknown” right there.
  3. Read the metadata URI. Connect the wallet that holds update authority and select the token on the metadata tool. It loads the current name, symbol, and URI. Any explorer that shows a token’s metadata also works.
  4. Open the URI in a browser. It should return JSON text, not an image, an HTML page, or an error.
  5. Open the image link from that JSON. It should load your logo.
What you seeWhere the chain breaksFix
”Unknown”, no nameNo metadata at allCreate metadata (needs mint authority)
Name, no logo, URI emptyNo URISet a URI pointing to a valid JSON file
Name, no logo, URI loads an imageURI points at the image, not JSONHost a JSON file and point the URI at it
Name, no logo, URI errorsHost down, link expired, or privateRe-host on durable storage, update the URI
Name, no logo, JSON loadsMissing or broken image fieldFix the JSON, then point the URI at it
Token missing or flaggedSpam classificationSee the spam section below

Fix 1: the token has no metadata at all

This is common with tokens minted from the command line without metadata. The fix is to create a Metaplex metadata account. The program only accepts that from the current mint authority: if the mint authority has been revoked, creation fails with an invalid-mint-authority error. The only exception in the program’s code is a Metaplex-controlled seeding key, which is not a route a token creator can use.

So the order matters. If you still hold mint authority, create the metadata first, then revoke. If you’ve already revoked it on a token with no metadata, that token can’t be given Metaplex metadata by you.

Tokens made with the forge’s token creator don’t hit this: the mint and its Metaplex metadata are written in the same transaction.

Fix 2: the metadata exists but the logo doesn’t load

This is the most common case. The usual faults are an empty URI (a token created without a logo), a URI that points straight at a PNG, JSON with the logo under the wrong key such as logo instead of image, or a host that has gone offline.

  1. Prepare the image. A square PNG is the safe choice. Host it somewhere permanent. Metaplex itself suggests permanent storage such as Arweave for metadata files.

  2. Write the JSON. The Metaplex fungible token standard uses four fields:

    {
      "name": "Forge Ore",
      "symbol": "ORE",
      "description": "One sentence about the token.",
      "image": "https://your-permanent-host/ore.png"
    }
  3. Host the JSON at a public https:// address and open it in a private browser window to confirm it loads without a login.

  4. Update the URI. On the metadata tool, connect the update-authority wallet, select the token, paste the new URI, and sign — or attach the image there and the tool hosts a new JSON file for you. It costs 0.1 SOL and settles in one transaction. The program caps the on-chain fields at 32 bytes for the name, 10 for the symbol, and 200 for the URI.

Publish new JSON at a new URL rather than overwriting the file at the old one. A new URI is an unambiguous change for every app that cached the old file. The files the forge hosts at creation are served as immutable, so a new logo means a new file anyway.

Fix 3: Token-2022 tokens

A Token-2022 token can keep its metadata on the mint itself instead of in a Metaplex account. Phantom reads the name and symbol from there and takes the logo from the uri, so the same JSON rules apply.

This matters for older tax tokens made on the forge’s Token-2022 bench: they stored the name and symbol on the mint with an empty URI, so they launched without a logo. (The bench now hosts the logo and writes its link at the strike.) To fix one, open the metadata tool with the creating wallet, which holds the update authority, and select the token. The tool reads metadata on the mint as well as Metaplex accounts. Attach the logo and sign: the logo and description are hosted as a new JSON file, its link is written to the mint, and the small rent increase the longer field needs is added to the same transaction. It costs 0.1 SOL.

Outside the forge, the Solana token CLI does the same job:

spl-token update-metadata <MINT_ADDRESS> uri https://your-permanent-host/metadata.json

The CLI also adds the extra rent, and spl-token authorize <MINT_ADDRESS> metadata --disable locks the metadata afterwards. It signs with a keypair file, so the update-authority key has to be available to it. Weigh that carefully, and never type a seed phrase into a website to do this.

When it isn’t “Unknown”: hidden or flagged as spam

Phantom’s help article on hidden and flagged tokens says a flagged token may show with a warning, move to the hidden list, or be removed from view entirely. Phantom doesn’t publish the criteria. For creators, it advises:

  • Keep the name, symbol, logo, and metadata accurate and consistent across platforms.
  • Get verified through Jupiter or CoinGecko. The listing guide covers both.
  • If the token is marked as spam, appeal to Blockaid through its portal at report.blockaid.io, as Phantom’s docs direct.

Phantom says spam detection re-runs automatically and regularly, so status can change once the metadata is fixed.

One more display quirk: if the token has no token standard set, Phantom guesses from supply and decimals. It treats a supply of 1 as an NFT, and a larger supply with 0 decimals as a semi-fungible asset. Either way the token shows under Collectibles instead of on the Home tab. Check there before assuming it’s missing.

After the fix: confirm, then lock

The chain changes as soon as the update confirms. Phantom doesn’t publish how often it refreshes token metadata. If the certificate shows the new state and Phantom still shows the old one, the delay is in the wallet, so wait rather than paying for a second update.

Once the logo shows correctly and the image is on hosting you trust to last, lock the metadata on the same metadata tool for 0.1 SOL. Locking is permanent, and it is one of the guarantees buyers check. The trade-offs are covered in how to update Solana token metadata and make it immutable.

Honest limits

  • Locked metadata can’t be repaired. A broken image link on an immutable token stays broken.
  • No metadata plus no mint authority is final. The Metaplex program won’t let the creator add a metadata account after that.
  • A hosted logo replaces the whole JSON file. When the metadata tool hosts a new logo, the new file carries the name, symbol, description, and logo only. If your current JSON lists social links or other fields, host an updated JSON yourself and paste its URL instead. The tool lists only the tokens the connected wallet holds an account for.
  • Phantom’s spam filter and refresh timing are outside anyone’s control except Phantom’s and its security providers’.

Frequently asked questions

Why does my Solana token say Unknown in Phantom?

Phantom labels a token Unknown when it cannot find metadata for it. It looks for a Metaplex Token Metadata account, or for a Token-2022 token, the metadata stored on the mint. If neither exists, Phantom falls back to the deprecated Solana Labs token list, and if the token is not there either, it can show the balance but not a name, symbol, or logo. The fix is to give the token metadata, which needs the mint authority if no metadata account exists yet.

Why does my token show a name but no logo in Phantom?

The token has on-chain metadata, so Phantom can read the name and symbol, but it cannot get an image. Phantom takes the logo from the image field of the JSON file that the metadata URI points to. If the URI is empty, points straight at an image instead of a JSON file, returns an error, or the JSON has no working image link, there is no logo. Pointing the URI at a valid JSON file fixes it while the metadata is still editable.

Can I add a logo to my Solana token after revoking mint authority?

Usually yes. Changing metadata needs the update authority, not the mint authority, so a token with an existing, editable metadata account can still get a new logo after its mint authority is revoked. The exception is a token that never had a Metaplex metadata account: creating one requires the current mint authority to sign, so once mint authority is revoked, the creator can no longer add one.

How long does Phantom take to show a new token logo?

Phantom does not publish a refresh interval. The on-chain change takes effect as soon as the transaction confirms, and a live reader such as the SolForger certificate shows the new state immediately. If the chain is right and Phantom still shows the old version, the delay is on the wallet side, so wait rather than paying for a second update.

Can I fix the logo if my token metadata is locked?

No. Locked (immutable) metadata cannot be changed by anyone, including the creator, so a broken URI on a locked token stays broken. This is why the metadata, and the hosting behind the image link, should be checked before it is locked.

My token is hidden or marked as spam in Phantom. How do I fix that?

That is a different problem from Unknown. Phantom's trust and safety systems can show a token with a warning, move it to the hidden list, or remove it from view, and Phantom does not publish its criteria. Phantom tells creators to keep the name, symbol, logo, and metadata accurate and consistent across platforms, and to get verified on Jupiter or CoinGecko. Detection re-runs automatically. For a spam mark, Phantom points creators to Blockaid's appeal portal at report.blockaid.io.

Written by

Marcus Feld

Solana engineer, SolForger

Marcus builds the transaction-signing tooling behind SolForger's benches, from the SPL create flow to the Token-2022 tax extension. He has been writing Solana programs and web3 clients since the 2021 token boom, and spends most of his time in the weeds of the Token program, Metaplex metadata, and the quirks of getting a versioned transaction through a wallet on mobile. He writes the step-by-step guides so the people who use the tools understand exactly what they are signing.

  • SPL Token program
  • Token-2022 extensions
  • Metaplex metadata
  • Transaction lifecycle
  • TypeScript & Rust