Getting a token logo into wallets: Trust Wallet and Jupiter requests, step by step

What wallet token list inclusion covers

Quick test: Open your token in 2 wallets. Is the logo shown or a blank circle? Note which ones need work.

Wallet token list inclusion means preparing a project's asset information for a wallet's supported token surfaces and helping the team follow the relevant submission route. It is distinct from an exchange listing: the work focuses on accurate identification, usable logo assets and consistent public information.

The service is useful when a token is difficult to identify in a wallet, its logo is missing or inconsistent, or the project wants to pursue a wallet's review or verification process. We start by clarifying which outcome you mean, because a logo display, appearance in a token list and a verification status are not interchangeable.

Before work begins, we collect:

• The token's network and contract address, checked against the project's own public references.
• Current logo files and any stated brand or file requirements you already have.
• Official website, social profiles and project description for cross-checking.
• The wallet and specific user-facing surface you want to address.

This gives us a concrete plan rather than a vague request to “get listed.” If you are also preparing broader tracker submissions, see listings and verification for the adjacent work.

How should a project prepare its wallet token information?

Prepare one consistent source of truth before submitting anything: the network, contract address, token name, symbol, logo and official project links should agree wherever a user can check them. Our wallet-readiness review compares those items and returns a concise gap list, so the team can resolve discrepancies before a request is sent.

Use this checklist to make the review productive:

• Confirm the contract address from the project's official channels and relevant explorer page.
• Provide the logo in its original files, not only in a screenshot or compressed social image.
• Keep token naming and symbols consistent across the website, wallet request and public profiles.
• Make sure official links are accessible and point to the project rather than an unrelated page.
• Flag any recent contract migration, rebrand or change to token details.

For projects that have changed contracts or names, coordinate the wallet request with the public update. Our contract migration and rebranding updates service covers that related profile work. A clean, consistent submission packet helps reviewers and users identify the intended asset; it does not replace the platform's own review.

Your 6-point wallet logo checklist

Check these 6 points before you submit. They give every wallet the same logo and the same facts, which is the quickest way through a review and the only way to avoid mismatched requests.

• Open your token in 2 wallets.
• Prepare the logo in the required format.
• Copy the contract address from the explorer.
• Match name and ticker everywhere.
• Keep proof of ownership.
• Log each request and its date.

Terms in one line

Token list: a list of verified tokens that a wallet or app shows with names and logos.

Jupiter verification (in plain words: a mark Jupiter gives to tokens whose details it has checked).

Trust Wallet and Jupiter: what does each request ask for?

Trust Wallet asset visibility and Jupiter verification are separate requests with different destinations, so one submission should not be treated as proof of the other. We confirm the target surface with you first, then prepare the information for the relevant platform route using the project's verified details.

For Trust Wallet, we organize the asset identity and logo information for the requested wallet-facing inclusion path. For Jupiter, we clarify what verification or asset information the project is seeking and help prepare a consistent submission. We do not present a generic token-list request as an equivalent to Jupiter verification; the status and purpose need to be stated accurately.

A practical distinction:

If your goal is specifically Jupiter-facing coverage, review our Jupiter listing support as a related route. For logos and token details displayed on explorer pages, see explorer token info and logo updates.

What the wallet inclusion work delivers

Rule of thumb: Use the same logo file and token details in every request. Mismatches cause rejections.

You receive a prepared submission package, not just a message saying that a request was sent. The exact contents follow the wallet and plan you choose, but the work is organized so your team can see what was checked, what was provided and what action remains.

Typical what you receive include:

• A readiness checklist covering token identity, network, contract, logo and official references.
• A list of inconsistencies or missing items to resolve before submission.
• Submission-ready project details and the logo files available from your team.
• A record of the request route, submitted materials and any response or follow-up received.
• A short handover explaining what to monitor in the wallet and where to report a display issue.

The workflow is straightforward. First, we collect the asset details and confirm the intended wallet surface. Next, we review the materials and send any corrections for your approval. Once the approved packet is ready, we support the submission and keep a status record. If a platform asks for clarification, we explain what it is requesting and help assemble a relevant response. The project retains control of its official claims and final approvals throughout.

What can affect wallet display or verification

A prepared submission improves clarity, but wallet display and verification are decisions made by the destination platform. The useful distinction for a project team is between items it can correct—such as inconsistent public details—and the platform's handling of its own asset data and review.

Trust Wallet controls whether and where an asset appears in its wallet experience, while Jupiter controls its verification decisions and the status it displays. A submitted logo or complete project packet cannot determine their review outcome, timing, asset coverage or later presentation changes.

To keep the work actionable, we record the exact details submitted and check the user-facing surface after any reported update. If the asset is still not visible, share the wallet version, network, token address and the steps you took to locate it; those specifics help distinguish a data issue from a search or display question. Avoid describing a submission as approval until the relevant wallet surface or verification status actually confirms it. This gives your community accurate guidance and gives the platform a useful report if follow-up is needed.

How wallet inclusion fits other visibility work

Wallet inclusion is one part of a coherent asset-information plan. Projects often pair it with tracker profile maintenance or a listing request, but each destination has its own record and workflow; a wallet submission does not automatically update other platforms.

Keep the work coordinated by using the same approved contract, token name, symbol, logo and official links across relevant profiles. If you are preparing a broader tracker application, our CoinGecko listing support and CoinMarketCap listing support address those separate destinations. For updates to market-facing DEX profiles, see DEXTools and DEXScreener profile updates.

Send 3 things: your contract address, your logo files and your official links. With those, we prepare the requests and confirm the cost in writing before anything is submitted.

How it works

1. Share the asset detailsSend the network, contract address, official project links, logo files and the wallet surface you want to address.
2. Confirm the request planWe distinguish a Trust Wallet asset request from Jupiter verification and agree what the submission is meant to address.
3. Review and resolve gapsWe compare the supplied details for consistency and send a written checklist of missing or conflicting items.
4. Prepare and submitAfter your approval, we organize the submission materials and support the agreed platform route.
5. Record status and follow upWe share what was submitted and any response received, with practical next steps for the project team.