Different image sources
The launch page may render uploaded launch data while DEXScreener relies on its own profile or an external token list.
Pump.fun → DEXScreener diagnostic
Pump.fun image showing there—but not on DEXScreener?
Diagnose why a Pump.fun token image appears at launch but remains missing or different on DEXScreener.
Pump.fun image visibleDoes not prove propagation
DEXScreener listingAutomatic when eligible
Best first actionCompare sources
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 retrieval failure
The metadata URI can exist even when its image returns a blocked response, redirect loop or incorrect content type.
A stale DEXScreener profile
A previous logo can remain visible after canonical metadata changes because profile state is platform-specific.
DEXScreener troubleshooting guide
Diagnose the source before changing the token.
A Pump.fun image appearing at launch does not prove that DEXScreener has the same profile data or can retrieve the same asset. The two services maintain separate indexing and presentation layers, and DEXScreener distinguishes automatic market listing from enhanced token profile information.
Trace the mint from its canonical metadata rather than copying the image rendered by Pump.fun. The metadata may reference a working asset while DEXScreener has no profile, or the Pump.fun interface may be serving a cached/proxied image that masks an origin URL problem. Cross-platform comparison reveals which branch is more likely.
Evidence-first process
Work through the problem in this order
- 01
Confirm the exact Pump.fun mint
Copy the mint address from a trusted transaction or token page and use it on every platform. Similar names and symbols make visual search an unsafe way to diagnose a newly launched token.
- 02
Find the canonical image source
Read the token metadata and follow its URI to the image field. Compare that raw URL with the image Pump.fun renders so you can detect a proxy, transformed asset, or stale cached version.
- 03
Test external fetchability
Request the metadata and image without Pump.fun cookies or application context. Confirm successful responses, proper content types, and no anti-bot page, expiring URL, or authorization requirement.
- 04
Check DEXScreener pair and profile state
Verify whether the liquidity pair and transaction are visible. If market data exists but profile fields do not, isolate the issue to profile enrichment or propagation rather than basic listing eligibility.
- 05
Fix the responsible layer
Repair the canonical asset only if raw metadata is wrong or inaccessible. If the asset is healthy and the discrepancy is DEXScreener-only, follow DEXScreener's official profile route and monitor the submitted version.
Avoid unnecessary work
Common mistakes
Using the Pump.fun render as the source of truth
An application can proxy or cache an image, so its successful display does not demonstrate that independent indexers can reach the origin.
Assuming the pair needs to be relisted
If DEXScreener already shows liquidity and transactions, relisting does not address absent profile fields.
Replacing metadata before testing the URL
Changing a valid mint record adds propagation work and may leave the actual DEXScreener-specific profile issue untouched.
Worked example
Pump.fun proxies a fragile asset
Observed
The launch page shows the logo, DEXScreener shows the pair without an image, and the canonical image URL contains an expiring query signature.
Diagnosis
Pump.fun can display its cached copy, but an independent fetch after the signature expires fails. The origin is not a durable public asset.
Smallest correct fix
Publish the image at a stable public URL, update metadata only with the proper authority, test it independently, and then allow DEXScreener to ingest the corrected source or profile.
Start with the free scan
Know what needs fixing before you spend.
DEXScreener answers
Frequently asked questions
Why does the image work on Pump.fun only?+
The two services can read different sources and refresh on different schedules. Compare the exact image URL and profile source before changing metadata.
Should I create another token or update metadata again?+
No. First verify the current on-chain URI, public image response and DEXScreener profile. Repeating a valid update can add cost without changing the platform-specific cause.
Does Pump.fun send every token image directly to DEXScreener?+
Do not assume both products use the same stored image or refresh path. Compare the exact image URLs and public token profile evidence on each service.
Can a Pump.fun image URL fail for external indexers?+
Yes. A URL may work in one application while redirects, content types, access controls or rate limits prevent another platform from retrieving it reliably.
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.