Token Logo Not Showing on Block Explorers? A Complete Guide to Fixing It (2026 Edition)

“I’ve successfully deployed my token contract, the on-chain data is all there, so why is it still showing a gray question mark icon on the block explorer?” This is a universal headache for almost every Web3 project founder or token deployer. When you check out your hard work on Etherscan, BscScan, Solscan, or BaseScan, a missing logo makes the project look extremely unprofessional and can even spark community doubts about the token’s legitimacy.

Here’s the short answer:
In 99% of cases, your token logo isn’t showing because you haven’t proactively submitted your token’s detailed information (including the icon) to the block explorer. These explorers don’t automatically grab images from the blockchain. The project team or a community member must submit them manually, and they only appear after an administrator approves them. The core workflow boils down to three steps: Prepare a compliant logo image → Find the submission portal for your specific explorer → Fill in the details and wait for approval.

Below, I’ll walk you through the complete logo update process for major explorers like Etherscan, BscScan, BaseScan, and Solscan from a beginner’s perspective, so you can fix this once and for all.

Why Is the Logo Blank? The Deep-Dive Reason and How to Fix It

Block explorers are fundamentally data aggregation and visualization platforms. They read on-chain transaction data from nodes, but a smart contract’s code doesn’t store a high-resolution JPG or PNG file (that would be insanely expensive in terms of gas fees). Therefore, explorers rely on an off-chain, centralized database to store a token’s metadata—including its name, symbol, decimal places, and most importantly, the logo.

When you deploy your contract, the explorer only automatically pulls basic on-chain fields like name and symbol. The logo field is blank. To fill it, you have to go through the “manual submission” channel.

Step 1: Prepare a “Perfect” Token Logo

No matter which explorer you’re submitting to, the image specifications are universal. The secret to getting approved on the first try lies in strictly following these requirements:

• File Format: Must be PNG (transparent background). Don’t use JPG, SVG, or WebP.

• Dimensions & Aspect Ratio: Strictly a 1:1 square. Recommended size is 200x200px or 256x256px. Keep the file size under 100KB.

• Background: Must have a transparent background. Do not use a white or solid colored background unless your design is inherently a square badge.

• Content: The icon should be clearly centered. Don’t put it right up against the edges; leave appropriate padding. Do not include promotional text, price tags, QR codes, or other irrelevant info.

• File Name: It’s recommended to name it simply logo.png to make the upload smooth.

Step 2: A Submission Guide for Each Explorer (The Practical Part)

While different ecosystems have different explorers, their core mechanisms are similar, yet their submission portals and approval criteria vary wildly. Let’s break them down one by one.

1. Etherscan (Ethereum) / BaseScan (Base Chain) / Other EVM-Compatible Explorers

Etherscan, BaseScan, PolygonScan, Arbiscan, and Optimistic Etherscan all belong to the Etherscan technology family. The interface and process are almost identical, making this the most common scenario for beginners.

Prerequisite: You need a free Etherscan account. That account must hold the contract ownership for the token (i.e., you’re the deployer), or you’ve added the contract address to your address watch list. However, the most common practice is to simply log in with the admin wallet that deployed the contract.

Detailed Steps:

1. Log In and Find Your Contract: Sign in to Etherscan using the deploying wallet (like MetaMask). Then, go to your token’s contract page.

2. Trigger the Update: At the top of the contract page, next to the “Token Tracker” line, find the “Update” link (often shown as “Update Name/Info” or a pencil icon). If you can’t find it, you can go directly to: https://etherscan.io/tokenupdate/[YourContractAddress].

3. Fill Out the Token Info:

• Token Symbol, Name, Decimals: These are usually auto-fetched and don't need changing.

• Project Description: This is mandatory! Concisely explain what your token does, ideally in 100-300 words. Include keywords for SEO, but don’t stuff them.

• Website and Social Links: Official URL, Twitter, Telegram, Discord, etc. The more you provide, the more legitimacy you build.

• Logo Upload: Click to upload the PNG icon you prepared.

4. Submit and Wait: After clicking “Submit,” the status will change to “Pending Review.” Etherscan’s review is very strict and typically takes 1-3 business days. If you haven't heard back in over a week, it was likely rejected without an email notification, so you’ll need to re-submit and double-check your image or information.

2. BscScan (BNB Smart Chain)

BscScan is also part of the Etherscan family, and the process is nearly identical, but with one crucial difference: the entry point is more hidden, and the background check on project owners is much stricter, especially within the Binance ecosystem.

Quick Step-by-Step: Log in to BscScan → Go to your token contract page → Click “Update” → Fill in info and upload logo.

What Newbies Must Pay Attention To: BscScan requires that the provided Website be genuinely accessible and that the site explicitly shows your token’s contract address or a clear association with the project. Otherwise, it will reject you with a “Cannot verify project ownership” note. If you don’t have a website, you can create a simple project info page on GitHub or publish an introductory article on Medium and use that URL in the website field.

3. Solscan (Solana Ecosystem)

Solana is not an EVM chain; its token standard is SPL Token. Solscan’s logo update logic is entirely different from Etherscan’s. It relies on on-chain metadata or a verified Token List repository, and this is where most people get it wrong.

The Core Mechanism: Solscan fetches SPL Token logos from two places:

• On-chain Metadata: If you used the Metaplex Token Metadata program and correctly set the uri field in your token’s metadata account to point to a JSON file (usually stored on Arweave/IPFS) containing an image field, some front-ends can parse it. However, Solscan’s retrieval of this format is notoriously unreliable.

• The Solana Token List (The Key): This is the most reliable and universal method. Solscan pulls logos from the famous Solana Token List public repository, which is jointly maintained by Jupiter, Solscan, and many other ecosystem projects.

Therefore, the standard way to update a logo on Solscan is to submit a Pull Request to the Solana Token List.

Detailed Steps (Beginner-Friendly Version):

1. Preparation: A GitHub account. Upload your logo PNG to the internet and get a direct link URL (for instance, upload it to your own GitHub repository or use an IPFS gateway, ensuring the link stays alive long-term).

2. Fork the Repository: Visit the github.com/solana-labs/token-list repository, click the “Fork” button in the top-right corner, and copy it to your own GitHub space.

3. Add Files and Information:

• In your forked repo, navigate to the assets/mainnet/[YourTokenMintAddress]/ directory. If the folder for your address doesn’t exist, create it.

• Upload your logo.png into this folder.

• Crucial Step: Modify the src/tokens/solana.tokenlist.json file. Find or add a new entry for your token, making sure the address is your Token Mint Address and the logoURI field points to the image link you just uploaded. The link format looks something like: https://raw.githubusercontent.com/solana-labs/token-list/main/assets/mainnet/[MintAddress]/logo.png.

4. Submit the PR: Create a Pull Request on GitHub to the original repo. In the PR description, seriously fill out the project name, official website, and a one-sentence introduction. A respectful attitude goes a long way.

5. Wait for the Merge: Wait for the Token List maintainers to review and merge your PR. This process can take anywhere from a few days to two weeks. Once the PR is merged, Solscan will display your logo after a data refresh cycle (usually within 24-48 hours).

Special Note: Never try to get them to add a logo by emailing Solscan’s customer support or DMing them on Twitter. You will almost certainly be ignored. Submitting a PR to the Token List is the only recognized way.

Step 3: What to Do After Submission—Tracking the Status

The hardest part after submitting is the waiting game. Here’s what you need to know:

• For Etherscan Family (including BaseScan): You can check the status on the https://etherscan.io/tokenupdate/[ContractAddress] page. If it previously said “Pending” but now shows an editable, blank form again, your submission was likely rejected. Check your image and info and submit again.

• For Solscan: Track the status of your submitted GitHub PR. If it shows “Merged,” all you have to do is wait for Solscan to sync. If the PR is closed, the maintainers will usually leave a comment explaining why (e.g., logo not sharp enough, no project website, suspected copycat). Fix the issues based on their feedback and re-submit.

Data Comparison: A Quick Cheat Sheet for Logo Updates on Major Explorers

To give you a clear overview, here’s a table comparing the key differences among the four main explorers:

Q&A Session: Answers to All Your Burning Questions

Q1: I’m just a regular holder, not the project owner. Can I submit a logo for a token I like?
A: You can try, but the success rate is low. Etherscan-family explorers usually require proof that you're the project owner (e.g., logging in with the deployer wallet). If you aren’t, and the info you submit (especially the website) can’t be verified, it will be rejected. Solscan is completely open; anyone can submit a PR for any token. However, reviewers will strictly judge if you're maliciously submitting a fake logo. If a token has been abandoned, the community is welcome to supplement its logo.

Q2: I submitted my logo over a week ago and it’s still not showing. Has it fallen into a black hole?
A: Don't panic. Proactively investigate. For Etherscan/BscScan, go back to the tokenupdate page. If the form is editable again, your last submission was rejected silently. Double-check: Is the image a transparent PNG? Is the link valid? Is the website accessible and clearly mentions this contract address? For Solscan, check your GitHub PR for any comments from a reviewer asking for changes, or if a CI check failed (e.g., a wrong file path).

Q3: After the token logo is successfully updated, can I change it later?
A: Absolutely. The process is exactly the same as the first time. If you want to swap out the logo, just run through the update workflow again. The new logo will overwrite the old one once approved. Keep in mind browsers have caches, so you might need to force-refresh (Ctrl+F5) or wait a few hours to see the change.

Q4: I uploaded my logo to IPFS. Can I just give the IPFS link to the explorer?
A: A hard no! For form-based explorers like Etherscan, you must upload the image directly through their webpage. They store it on their own CDN; you cannot paste an external link. For Solscan’s Token List, while you do fill in an external logoURI in the JSON, the recommended and most stable method is to use a relative path to the file inside the GitHub repository, not a direct IPFS gateway link, as IPFS gateways can go down.

Q5: Why isn't the logo showing in Phantom/Trust Wallet? It’s already on Solscan!
A: This is the biggest misconception. Showing on Solscan ≠ Showing in Wallets. Wallet logo updates are a separate, independent process:

• Phantom: It also heavily relies on the Solana Token List. After your PR is merged, Phantom will sync, but it’s often slower than Solscan, potentially taking a week.

• MetaMask / Trust Wallet: For EVM chains, MetaMask partially pulls data from Etherscan, but it sometimes has its own token detection list. Trust Wallet requires you to submit a PR to its assets repository to add a logo. This means you might need to update the logo for the same token separately on Etherscan, Trust Wallet, and CoinGecko.

Q6: My token on Etherscan is showing the logo of an impersonator with the same name. What do I do?
A: This happens when your contract isn’t verified or has missing info, causing the explorer to incorrectly match it with another token’s logo. You need to immediately submit your real logo and project info correctly. As long as your contract is open-source verified and the info is accurate, your new logo will overwrite the wrong one.

Q7:Does my project website have to be HTTPS?

A: Yes, that’s the absolute bare minimum. Explorers like Etherscan have high security requirements for projects. If your site is still on http://, it will be rejected on sight. Make sure you have an SSL certificate installed and use an https:// URL.

Summary

A missing token logo is never an on-chain technical failure. It’s an entry-level test of your patience, adherence to standards, and compliance awareness. It’s like your project’s "on-chain business card"—a blank or unprofessional icon will massively erode user trust.

To fix this once and for all, burn this golden workflow into your memory:

1. Create a clean, transparent-background PNG icon, sized at 200x200.

2. Give your project a decent HTTPS website or a landing page.

3. If you’re on ETH/BSC/Base or other EVM chains, log in to the explorer with your deployer wallet, find the “Update” button, and submit.

4. If you’re on Solana, calmly learn how to submit a GitHub PR to the Solana Token List. Don’t DM customer support.

5. Set a mental expectation of at least one week for the review. Don’t panic an hour after submitting.

In the world of Web3, the devil is in the details. The moment you see that meticulously designed icon finally appear on a top-tier block explorer, paired with your contract address, your token truly earns its “legal identity” to circulate in the crypto world. So go ahead, open up your explorer, and get that missing ID card submitted right now!