Metadata URI is unreachable
The on-chain pointer can exist while its JSON target returns an error or times out.
Solana metadata checker
Check your Solana token metadata
Inspect whether a token uses classic SPL or Token-2022 metadata and diagnose broken JSON, images and inconsistent fields.
Classic SPL + MetaplexSupported
Token-2022 metadataSupported
Image/JSON preflightIncluded
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.
Image response is invalid
Wrong content type, access restrictions or redirects can prevent external platforms from loading the asset.
The wrong metadata path was checked
Token-2022 extensions and Metaplex metadata accounts require different detection logic.
Solana troubleshooting guide
Diagnose the source before changing the token.
Solana tokens do not all expose metadata through one mechanism. Traditional SPL tokens commonly use a Metaplex metadata account linked to the mint, while Token-2022 can use metadata pointer and token metadata extensions. A checker that probes only one architecture may incorrectly report that valid metadata is missing.
Finding a URI is only the first stage. The off-chain JSON, image response, field consistency, update authority, and mutability all affect whether platforms can consume a change. The goal is to identify the earliest broken dependency before recommending another transaction.
Evidence-first process
Work through the problem in this order
- 01
Identify the token program
Read the mint owner and extensions to distinguish classic SPL from Token-2022. Use that result to decide whether to inspect a Metaplex PDA, extension-based metadata, or both where applicable.
- 02
Extract authoritative fields
Record the live name, symbol, metadata URI, update authority, and mutability state. Preserve raw values so trailing spaces, stale URIs, and authority assumptions are visible.
- 03
Validate off-chain JSON
Fetch the metadata URI and check its HTTP status, content type, JSON syntax, image field, description, website, and social properties. Confirm that the response is public and stable outside the project's own session.
- 04
Inspect the image response
Request the image URL independently and verify that it returns actual image bytes with an appropriate content type. Note redirects, access controls, gateway errors, and case-sensitive paths.
- 05
Compare downstream representations
Diff the canonical fields against DEXScreener, Jupiter, Solscan, Birdeye, and wallet views. Widespread stale values suggest an upstream issue; one differing platform suggests a platform-specific cache, profile, or policy.
Avoid unnecessary work
Common mistakes
Assuming every token uses Metaplex
Token-2022 can associate metadata with the mint through extensions, so a missing PDA does not prove missing metadata.
Stopping after a URI exists
A pointer can be valid on-chain while its JSON target is malformed, unavailable, or linked to an inaccessible image.
Ignoring authority and mutability
A technically correct repair plan is not actionable if the required authority is absent or the relevant metadata cannot be changed.
Worked example
Token-2022 metadata with a blocked image
Observed
A Token-2022 mint has a metadata pointer and valid JSON, but several platforms display no logo.
Diagnosis
The image request returns a 403 response to non-browser clients. The extension is present; the public asset is the broken dependency.
Smallest correct fix
Re-host the image on a stable public endpoint, update the authorized metadata URI or image field as appropriate, and verify raw responses before monitoring downstream consumers.
Start with the free scan
Know what needs fixing before you spend.
Solana answers
Frequently asked questions
Does every Solana token use Metaplex metadata?+
No. Token-2022 can use a Metadata Pointer and Token Metadata extension associated with the mint.
Why does my image work locally but not on platforms?+
Platforms may reject a host because of HTTP status, content type, redirects, rate limits or access controls even when your own browser can load it.
What should a Solana token metadata JSON file contain?+
At minimum, check the intended name, symbol and image reference. Project descriptions and links should be consistent, public and represented through the metadata architecture the token actually uses.
Can immutable Solana token metadata be corrected?+
Not through a normal metadata update when mutability has been disabled or the required authority is unavailable. Platform-specific profile changes may still be possible, but they do not alter canonical metadata.
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.