SPL Token Metadata: Validate JSON and Fix Missing Logos

A successful mint and a visible logo are separate checks. First verify the mint address and token balance on the correct network. Then inspect the metadata account and the files it points to. Recreating a token because its image is missing can leave you with two different mints carrying the same name.

Follow the metadata from chain to image

The mint identifies the asset. A Metaplex metadata account supplies its on-chain descriptive fields and a URI pointing to JSON. That JSON can contain the description, image URL and project links. The image lives at a separate URL. A wallet has to read each part before it can display the complete identity.

Open the URI recorded on chain in a browser. It should return the intended JSON without a login screen, expired download link or HTML error page. Next open the JSON's image URL. An image that works only while you are signed into its hosting account is unsuitable for a public token.

Check the fields with a concrete example

A simple fungible-token JSON can contain name, symbol, description and image. Keep the name and symbol consistent with the token you created. Use an absolute HTTPS image URL and a supported image format. Project links describe your project; they do not give it staking, governance or other executable behavior.

If the URI returns valid JSON but the image does not load, repair the image host first. If both URLs work, compare them with the URI in the metadata account rather than assuming a locally saved file is the live version. An explorer's display name is useful evidence, but the mint address remains the reliable identifier.

Understand what can still be changed

Mint authority, freeze authority and metadata update authority control different things. Revoking mint authority does not automatically lock a logo or description. Whether metadata can be updated depends on its update authority and mutability. Check those fields before promising a permanent identity or attempting an edit.

TokenAnvil's creator attaches Metaplex metadata during token creation. Its Developer API also accepts hosted metadata or your own HTTPS metadata URI. Uploaded hosting remains dependent on the hosting service operating; a public URI alone is not a permanence guarantee.

If a wallet still shows an unknown token

Confirm the wallet is on the mint's network and holds the correct token account. Wallets may cache metadata or apply their own display and spam rules. Give them time to refresh, then use the mint address and transaction record to establish delivery. A missing icon is not evidence that another payment is required.

Send support the network, mint address, transaction signature and the failing public URL. Keep seed phrases and private keys out of the report. For the creation checklist, use the metadata guide; for field definitions, consult the Metaplex documentation.