The metadata submission is incomplete
Jupiter can review fields such as name, symbol, logo, description, website and social profiles.
Jupiter metadata troubleshooting
Jupiter token logo not updating?
Separate Jupiter metadata updates from VRFD verification and check why an old or missing logo remains across Jupiter products.
Metadata reviewSeparate from verification
Standard routeFree
Express route1,000 JUP
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.
The new logo is not publicly reliable
A URL that redirects, blocks crawlers or returns an incorrect response can fail despite loading locally.
Verification expectations are misplaced
Paying for Express Review prioritizes the review and does not guarantee that the token becomes verified.
Jupiter troubleshooting guide
Diagnose the source before changing the token.
A stale Jupiter logo can result from canonical metadata, Jupiter-distributed metadata, or review state, and those should not be treated as one problem. Jupiter supports token information used across its products, while verification follows a separate workflow.
Compare the mint's live metadata with Jupiter's current name, symbol, logo, description, website, and socials. If the canonical image is inaccessible, repair it upstream; if canonical data is healthy but Jupiter alone is stale, prepare a Jupiter metadata update. Verification may improve recognition, but it should not be promised as a guaranteed logo refresh.
Evidence-first process
Work through the problem in this order
- 01
Confirm the exact stale field
Determine whether the old logo appears in Spot, Terminal, Mobile, API output, or several Jupiter surfaces. Record URLs and timestamps instead of assuming every Jupiter product has the same cache state.
- 02
Read the mint's current metadata
Inspect the applicable Metaplex or Token-2022 source and fetch its JSON and image. Confirm that the new asset is public and that the mint authority update actually changed the intended record.
- 03
Compare all Jupiter identity fields
Check the name, symbol, description, website, and socials alongside the logo. A partial or contradictory identity package can indicate that Jupiter is using a platform record rather than the latest canonical data.
- 04
Use the appropriate Jupiter request
Submit a metadata update for stale profile fields and use verification review only for verification status. Choose Standard or Express according to official terms, understanding that expedited review does not guarantee approval.
- 05
Monitor products and API separately
Save the submitted values and check the relevant Jupiter surfaces over time. Escalate with the mint, working source URL, request evidence, and timestamps rather than sending conflicting repeat submissions.
Avoid unnecessary work
Common mistakes
Using verification as a logo repair button
Verification and profile metadata are separate states, and approval should never be represented as guaranteed display propagation.
Checking only one Jupiter surface
Products and APIs may expose updates at different points, so one cached client does not establish the state of the entire Jupiter record.
Submitting an untested image
A URL copied from an upload dashboard may expire, redirect, or reject indexers even if it opens for the project team.
Worked example
Canonical logo is new, Jupiter is old
Observed
The Metaplex URI and public image return the new brand, while Jupiter's API and token page retain the prior logo and all other platforms have updated.
Diagnosis
The discrepancy is isolated to Jupiter's metadata record or propagation path rather than the mint or image host.
Smallest correct fix
Prepare one official Jupiter metadata update with the exact mint and public asset, keep verification expectations separate, and monitor the affected Jupiter products with timestamps.
Start with the free scan
Know what needs fixing before you spend.
Jupiter answers
Frequently asked questions
Can I update metadata without becoming verified?+
Jupiter’s Express API documentation treats verification and metadata updates as independently reviewed operations.
Does Express Review guarantee the new logo is accepted?+
No. It provides a faster review workflow, while eligibility and submitted information still determine the outcome.
Should I change on-chain metadata before requesting a Jupiter update?+
Only when the canonical metadata is actually wrong and the update authority is available. If the canonical logo is correct, investigate Jupiter's metadata review and propagation path instead.
What image format and hosting should a Jupiter logo use?+
Use a stable public image URL that returns an appropriate image content type without authentication, blocking or unstable redirects. Confirm current Jupiter submission requirements before sending it.
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.