When you create a token on Solana, the basic SPL Token Program only stores raw token balances and decimals. It does not natively store your token’s human-readable name, ticker symbol, description, website, or logo image.
To display rich token branding across wallets (like Phantom and Solflare) and DEX interfaces (like Raydium and DexScreener), Solana uses the Metaplex Token Metadata Standard.
Understanding how on-chain metadata accounts connect to off-chain JSON files ensures your token displays its logo and details reliably without broken images or rendering glitches.
The Metaplex Metadata Standard splits token information into two distinct layers:
A dedicated account stored directly in Solana validator memory, derived deterministically from your token mint address (a Program Derived Address or PDA). It stores fixed, queryable string fields:
- Name: Token name (up to 32 characters).
- Symbol: Ticker symbol (up to 10 characters).
- URI: A URL string (up to 200 characters) pointing to the off-chain JSON file.
- Update Authority: The public key allowed to update the metadata (until revoked).
A structured JSON file hosted on permanent decentralized storage (such as Arweave, Shadow Drive, or IPFS). This file holds extended project details:
image: Direct URL to the PNG, JPEG, or SVG logo asset.
description: Detailed project summary.
external_url: Official website link.
properties.files: Array of media assets and content types.
Official schema specifications are maintained in the Metaplex Developer Documentation.
Common Causes of Broken Token Logos
Token creators often notice that their token logo appears in Phantom wallet but fails to load on Solscan, or vice versa. This occurs due to metadata specification mismatches:
- Non-Direct Image URLs: Linking to a web page containing an image rather than a direct image asset URL ending in
.png or .svg.
- CORS Restrictions: Hosting the image on a centralized web server that blocks cross-origin resource sharing (CORS) requests from wallets and DEX frontends.
- Invalid Image Aspect Ratios: Uploading non-square images. Wallet interfaces expect square aspect ratios (e.g., 512x512 pixels).
- Temporary Hosting Providers: Hosting image assets on temporary image uploading sites that delete files after 30 days.
To guarantee universal rendering across all Solana wallets and DEX aggregators, follow these image and JSON guidelines:
- Image Format: PNG or SVG (transparent background recommended).
- Dimensions: Square 512x512 pixels (under 1 MB file size).
- JSON Hosting: Permanent, decentralized storage (Arweave or IPFS gateway).
- HTTPS Enforcement: All image URIs must use secure
https:// or ar:// protocol headers.
Creating, pinning, and linking Metaplex JSON files manually requires setting up Arweave wallets and CLI developer tools.
The PumpBolt Solana Token Creator automates the entire metadata pipeline in a single step:
- You upload your square PNG or SVG logo image directly in the web form.
- PumpBolt optimizes the image asset and uploads it to permanent decentralized storage.
- PumpBolt generates a compliant Metaplex JSON metadata file and pins it to Arweave.
- When you mint your token, PumpBolt attaches the Arweave URI to your on-chain Metaplex metadata account in the same transaction.
Following the Metaplex standard and using permanent storage ensures your token branding remains visible and immutable across the entire Solana ecosystem.