deploya tokenTools / Logo & Metadata Check

Why Is My Solana Token Logo Not Showing?

Find out why a token's logo or name is missing: the URI, the JSON document and the image itself, checked in order.

Solana

How to fix a Solana token logo that is not showing

  1. Paste the token's mint address. No wallet is needed and nothing is signed, so this is free.
  2. Press Check. It reads the mint, then follows the metadata URI written into it.
  3. Read the verdict first: whether anything found will actually stop your logo appearing.
  4. Work through the findings in order. They follow the chain of things that has to be true: a URI exists, it returns JSON, the JSON has an image field, and that image loads.
  5. Fix whatever is flagged, then re-check. Wallets cache metadata for a while, so a fixed token can still look wrong in your wallet for several minutes after the check here comes back clean.

Common questions

Why is my token's logo not showing in Phantom?

Almost always one of four things, and this tool tells you which. Either the mint has no metadata URI at all, or the URI points somewhere that no longer serves the file, or it returns something that is not a JSON document (very often the image itself by mistake), or the JSON is fine but the image link inside it is broken. The mint being fine is not enough: wallets read a chain of things and any link in it can fail.

I fixed it and it still looks wrong. Is it broken?

Probably not. Wallets and explorers cache metadata on their own schedule, so a corrected token can keep showing the old logo, or none, for minutes after the fix confirms. If this tool says everything checks out, the chain is right and you are waiting on a cache. Different apps will update at different times.

It says it could not fetch the document. Does that mean my token is broken?

No, and this is worth understanding. A browser refuses to tell a page why a cross-origin request failed, so we genuinely cannot tell a missing file from a server that simply does not send a CORS header. Wallets often fetch through their own backends and are not affected by that at all. If the URI opens fine in a new tab, your token is almost certainly fine and we just could not read it from here.

How is the image check different?

It is reliable, where the document fetch is not. Loading an image is not a cross-origin read, so an image that fails to load really did fail. If this tool says the image loads, a wallet will be able to load it too.

The name on-chain and in the document are different. Does it matter?

Yes, more than people expect. Wallets differ over which one they display, so a token whose two names disagree shows up under one name in some apps and another elsewhere, and the owner usually has no idea. Pick one and make them match.

Where should I host the metadata document?

Somewhere that will still exist in two years. IPFS and Arweave are the right answers and this tool treats them as good rather than merely acceptable, because they cannot quietly vanish the way a personal web host can. A URL on a domain you might stop renewing is how a token ends up with no logo eighteen months later.

Can I fix the metadata from here?

No, this page only diagnoses. Changing the name, symbol or URI is done with Update Metadata, and it needs the update authority and a signed transaction. Splitting them keeps this one free, wallet-free and safe to run on any token, including ones you have nothing to do with.

The chain of things that has to be true

A logo showing up in a wallet is not one fact, it is four, and every one of them can fail on its own. This tool checks them in the order they depend on each other:

  1. The mint has a metadata URI. Without this there is nothing to follow and no logo anywhere.
  2. That URI returns a JSON document. The single most common mistake is pointing it straight at the logo image instead of at a JSON file that links to the image.
  3. The document has an image field. This is the field wallets actually read. A beautiful document without it shows nothing.
  4. That image loads. The link can be present and still point at something that has moved or was never there.

What lives on-chain, and what does not

Only the name, the symbol and the URI are on-chain. The description and the logo live in a JSON file at that URI, hosted by you, and nothing about it is guaranteed by Solana.

That is the whole reason this page exists. A token can be in perfect health, with revoked authorities and a healthy pool, and still show as a blank circle everywhere because a file moved. The chain has no idea, and neither does anything that only reads the chain.

The one thing a browser cannot tell you

When this tool says it could not fetch your document, it means exactly that and no more. A browser deliberately refuses to tell a page why a cross-origin request failed, so a missing file and a missing CORS header look identical from here. Wallets frequently fetch through their own servers and are not subject to that rule at all.

So that case is reported as a warning with an explanation rather than as a failure. Open the URI in a new tab: if it loads for you, your token is almost certainly fine. A checker that called that "broken" would be wrong often enough that people would learn to ignore it, and then it would be worse than not existing.

Host it somewhere permanent

The most common way a working token loses its logo months later is the host going away: a free tier that ended, a domain that lapsed, a bucket that was tidied up. IPFS and Arweave exist for this and this tool treats them as the right answer rather than an eccentric one.

Related tools

Sources