Manage banners, token logos and explorer requests

Creating and managing tokens · How-to and reference · Owner-authorized branding capabilities for confirmed launches. Site banners, chain metadata and manual explorer requests are separate.

Know which artwork surface you are changing and track publication without promising external propagation.

Reviewed: 2026-10-18

Before you start

The recorded creator/owner account and confirmed launch.
Current branding capabilities and rights to publish the artwork.

Three surfaces, three different outcomes

Open Manage branding from My launches. The page distinguishes the on-chain token logo, the COMPUTER.EXE site banner and a saved helper for a manual Solscan request. Publishing one does not update the other two.

If the launch is not confirmed, open the attempt first. If capabilities fail to load, use Retry before editing. A cached logo preview is labeled by source and is not proof of current chain metadata or external acceptance.

Publish or restore a site-only banner

The banner editor supports automatic artwork and custom publication. Custom crop controls adjust horizontal position, vertical position and zoom; Reset crop returns the framing, not the currently published banner.

Publish publicly changes the site banner only. For a queued or uncertain operation, inspect the saved operation and use Cancel, Retry same attempt or Recover submitted attempt only when offered. A history Restore action prepares a replacement that must still be published.

Open the matching launch’s branding page and inspect automatic/custom status.
Upload a supported image, crop and zoom it, and review the preview. Discard if it is wrong.
Acknowledge public publication and select Publish banner once. Track the same operation until the result is known.
To return to automatic artwork, use Use automatic and its confirmation. To restore history, choose Restore, inspect the preview and publish the restored banner.

On-chain logo editing is not currently supported

The branding page currently reports no supported chain-logo edit adapter. A site banner update is not an on-chain metadata update, and the absence of an edit button is not a reason to submit a token-creation transaction again.

Verify the launch’s public metadata and exact mint when investigating a missing logo. Changes to immutable identity or unsupported metadata cannot be promised by a manual explorer request.

Prepare and submit a manual request

The saved request helper does not contact Solscan. It stores your draft and prepares a packet for Solscan’s own free manual review. Copying a packet or opening the external form is not submission.

The packet uses saved values, not unsaved edits. Published artwork has a permanent public URL; a development-preview URL is not suitable. Only record submitted, approval or rejection states when that event actually happened externally; those are reports, not independent verification.

Start a saved draft and enter the requester, official contact, website and neutral project description. Save edits.
If publishing artwork, read the public-URL acknowledgment and inspect the resulting image URL. Prepare the packet from the production site.
Select Prepare packet, copy it privately as appropriate, and open the official Solscan form from the helper.
Choose Social Links & Logo Update, complete the external verification and submit there. Avoid duplicate submissions and paid priority options.
Return and explicitly record that you submitted it. Later record the external decision only if received.

Verify display on each surface

A committed site operation proves only that site publication outcome. Solscan acceptance, wallet logos and other indexers have their own policies, data sources and caches. There is no guaranteed display time or cross-app propagation.

Check the exact mint, the publicly reachable image/metadata and the source of the displayed preview. If an external app is stale, use its documented refresh or review process; do not remint, resend a launch or claim an unsupported chain change.