DEXScreener is showing a profile override
Platform-specific profile fields can remain independent of later on-chain changes.
DEXScreener update troubleshooting
DEXScreener token info not updating?
Find whether unchanged DEXScreener information comes from stale platform state, external token lists or an upstream metadata problem.
On-chain changeNot an instant refresh
External listsCan supply token info
Repeat paymentDiagnose first
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.
An external list is still old
If DEXScreener is consuming external token information, the outdated field may originate there.
The new asset is inaccessible
A changed URI does not help if the JSON or image cannot be fetched consistently by external services.
DEXScreener troubleshooting guide
Diagnose the source before changing the token.
When DEXScreener token information does not change, first identify which layer was updated. An on-chain metadata transaction, a new off-chain JSON document, and a DEXScreener Enhanced Token Info order are different events with separate caches and processing paths.
Build a timestamped chain of evidence: old and new canonical values, public HTTP responses, submitted DEXScreener fields, and current API or page output. This avoids duplicate changes while an accepted update is still processing and exposes cases where the platform keeps receiving the old value from a mutable URL or cached gateway.
Evidence-first process
Work through the problem in this order
- 01
Name the update that occurred
Record whether the team changed Metaplex metadata, Token-2022 metadata, the contents behind an unchanged URI, or DEXScreener profile information. Include the transaction signature or order reference where one exists.
- 02
Verify the new source is actually live
Fetch the canonical JSON and image from a clean client and confirm that they return the new bytes and expected content types. An editor preview is not evidence that the published endpoint changed.
- 03
Detect unchanged-URL caching
Compare response headers, gateway behavior, and the old and new asset URLs. Replacing content at one URL can leave downstream caches with no clear version boundary.
- 04
Check DEXScreener's current record
Compare documented API/profile data with the visible page and note the observation time. This helps distinguish an updated backend from a local browser cache or a still-pending platform record.
- 05
Escalate with a compact evidence package
If the official processing guidance has passed, provide the mint, pair, submitted values, order reference, working source URLs, and timestamps through the official support route. Do not create another paid order solely to restart the clock.
Avoid unnecessary work
Common mistakes
Making multiple simultaneous updates
Changing metadata, image hosting, and profile fields together removes the ability to identify which dependency remains stale.
Using an unchanged mutable asset URL
Overwriting a file at the same address can leave indexers serving an older cached object even though the project sees the new upload.
Inventing a universal refresh time
Use DEXScreener's current official processing guidance and the specifics of the submitted route rather than promising an unsupported deadline.
Worked example
New logo, same gateway URL
Observed
The team overwrote logo.png and sees the new image in its dashboard, but DEXScreener continues to show the prior graphic.
Diagnosis
The metadata and image URL never changed, and a public request through the storage gateway still returns cached old bytes.
Smallest correct fix
Publish a versioned public asset, update the authorized canonical reference if necessary, verify the new bytes externally, and then monitor or provide evidence to DEXScreener support.
Start with the free scan
Know what needs fixing before you spend.
DEXScreener answers
Frequently asked questions
How long does a DEXScreener update take?+
Processing and propagation vary by update route. DEXScreener says Enhanced Token Info usually processes within minutes but allows up to 12 hours; upstream changes can follow different schedules.
Should I submit the same information again?+
Not until you identify which source is stale and confirm that an earlier request is not still processing.
Why can an old DEXScreener logo remain after an on-chain update?+
DEXScreener may retain platform profile data or consume another external source. An on-chain transaction does not invalidate every downstream cache or override.
How can I prove which token field is stale?+
Record the exact canonical JSON, image URL and visible DEXScreener values, then compare them with other sources. Field-level evidence is more useful than another blind submission.
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.