Jupiter recognition is incomplete
Valid metadata can still lack the upstream recognition Phantom uses as a trust signal.
Phantom readiness checker
Solana token logo not showing in Phantom?
Trace Phantom display problems back to token metadata, Jupiter recognition or CoinGecko instead of looking for a nonexistent direct submission.
Direct logo submissionNot generally available
Jupiter recognitionRelevant
CoinGecko recognitionRelevant
What the scan separates
The same symptom can need a completely different fix.
CheckMyMint prioritizes evidence and dependencies so you can avoid repeating a valid update or paying the wrong platform.
Metadata differs across sources
Name, symbol, logo and links should remain consistent across canonical and registry sources.
Phantom has not reclassified yet
After upstream changes, Phantom may need time to rerun its automatic classification.
Phantom troubleshooting guide
Diagnose the source before changing the token.
Phantom visibility depends on more than a valid image URL. Its support guidance tells creators to keep token information accurate and consistent and points to upstream recognition through sources such as Jupiter or CoinGecko; it also applies automated spam and classification controls.
Because there is no universal direct logo-submission shortcut, diagnose the dependency chain. Confirm the canonical metadata, compare Jupiter and CoinGecko, and inspect whether Phantom has hidden or flagged the asset. A technically correct logo can remain absent while upstream recognition is incomplete or while automatic classification has not rerun.
Evidence-first process
Work through the problem in this order
- 01
Verify the mint and metadata method
Confirm the exact mint address and whether its metadata comes from Metaplex or Token-2022. Read the live name, symbol, URI, and image rather than copying values from another wallet interface.
- 02
Normalize identity fields
Compare the project name, symbol, logo, website, and social links across canonical metadata, Jupiter, and CoinGecko. Resolve conflicting branding at the authoritative source before expecting Phantom to choose the new version.
- 03
Check hidden or spam classification
Follow Phantom's support guidance to determine whether the token is hidden or flagged. A classification problem is different from a wallet failing to download an otherwise accepted image.
- 04
Address the relevant upstream route
If Jupiter or CoinGecko lacks the project or contains stale details, use that provider's official metadata or verification workflow. Do not represent the upstream submission as a guaranteed Phantom change.
- 05
Allow automatic reevaluation
After correcting consistent source data, keep a timestamped baseline and wait for Phantom's automatic process to run. Avoid rapid successive metadata edits that make it difficult to know which source Phantom evaluated.
Avoid unnecessary work
Common mistakes
Looking for a universal Phantom logo form
Phantom's guidance emphasizes accurate metadata and upstream recognition rather than a general direct submission route for every token.
Ignoring spam classification
A hidden or flagged token requires classification-oriented troubleshooting, not merely a different image file.
Changing only one inconsistent source
Conflicting names, symbols, logos, or links across canonical and registry data can prolong an ambiguous downstream state.
Worked example
The new image appears on-chain only
Observed
The metadata URI contains the new logo, while Jupiter and CoinGecko still show the previous identity and Phantom shows no trusted image.
Diagnosis
The asset itself is reachable, but the recognized upstream records are stale and inconsistent with the mint's canonical metadata.
Smallest correct fix
Correct the appropriate Jupiter or CoinGecko record through its official workflow, keep all identity fields consistent, and monitor Phantom's automatic reclassification.
Start with the free scan
Know what needs fixing before you spend.
Phantom answers
Frequently asked questions
Can I submit my token logo directly to Phantom?+
Phantom’s creator guidance emphasizes accurate metadata and recognition through Jupiter or CoinGecko rather than a universal direct logo form.
Why is the token correct on Solscan but not Phantom?+
The two products apply different rules. Solscan visibility does not prove that Phantom’s upstream recognition and classification requirements are satisfied.
Does valid on-chain metadata guarantee a Phantom logo?+
No. Valid metadata is necessary, but Phantom can also rely on upstream recognition, safety classification and its own refresh process.
What should I fix before waiting for Phantom to refresh?+
Confirm the canonical image is public, identity fields match across sources, and the token has the relevant Jupiter or CoinGecko recognition. Then avoid repeated metadata edits during reclassification.
First-party references
Sources used for this guide
Third-party workflows change. CheckMyMint links to official documentation and displays when the platform rules were reviewed.