Unclassified reputation
A reputation state can suppress display even when the underlying token image is valid.
Check whether Solscan reputation—not broken metadata—is preventing your Solana token logo from appearing.
CheckMyMint prioritizes evidence and dependencies so you can avoid repeating a valid update or paying the wrong platform.
A reputation state can suppress display even when the underlying token image is valid.
A functioning site, public logo, neutral description, socials and project-domain email may be required.
The token may use a metadata extension that differs from a traditional Metaplex metadata account.
A missing Solscan logo is not automatically a metadata defect. Solscan documents a reputation system in which tokens commonly begin as Unclassified, and that state can suppress the logo even when the image and metadata are technically valid.
A useful check therefore has two branches: validate the token's actual metadata path and inspect the Solscan-specific display state. If the image is publicly reachable and appears through other consumers, another metadata edit is unlikely to address a reputation restriction. The appropriate next step may be an official token information or reputation update.
Check whether the token uses classic SPL with Metaplex metadata or Token-2022 with a metadata pointer and token metadata extension. Looking only for a Metaplex account can produce a false missing-metadata result.
Open the canonical JSON and request the image directly. Confirm that the URL is public, durable, returns an image content type, and matches the project logo rather than a temporary upload or HTML gateway page.
Review the token page for an Unclassified or other reputation label. Treat reputation as a platform policy state, not as evidence that the on-chain image pointer is broken.
For an official update, assemble a functioning website, a publicly accessible logo, a neutral project description, complete social links, and a project-domain email address where required by Solscan's guideline.
Use Solscan's documented update route and save screenshots or field values from before submission. Monitor the reputation and visible logo without making unrelated on-chain changes while the platform review is pending.
Solscan can intentionally hide a logo for this reputation state, so replacing an already valid image does not address the policy reason.
An incomplete site, missing socials, or a generic contact address can weaken an update request even when the logo file itself is valid.
Token-2022 metadata may live through extensions associated with the mint and requires different detection logic.
The image returns a public PNG, and Jupiter displays it, but Solscan shows an Unclassified label and no logo.
The cross-platform evidence indicates that the asset works. Solscan's reputation display rule, rather than the image URI, is the likely blocker.
Keep the working metadata unchanged and prepare a Solscan reputation or token-information update with complete, neutral project evidence.
Solscan applies its own reputation and display rules. An Unclassified token may not display a logo even when another platform does.
Not if the current metadata and image are valid. Check the token reputation and official Solscan update requirements first.
Prepare a functioning official website, a stable public logo, a neutral project description, working social links and a project-domain contact address where requested by Solscan.
Yes. Token-2022 can expose metadata through extensions rather than a traditional Metaplex metadata account, so the correct metadata architecture must be checked first.
Third-party workflows change. CheckMyMint links to official documentation and displays when the platform rules were reviewed.