Token Metadata Checklist: Get It Right Before You Launch

A token's name, ticker, image and links are written once, at creation, and on launchpad tokens they can't be changed afterwards. A typo in the ticker or a broken image follows the token forever, on every screener and wallet. This checklist covers what to prepare before pressing Launch - on pump.fun, LetsBonk or Bags.

Where metadata lives

On-chain, a token stores only its name, its symbol and a URI. The URI points to a small JSON file - usually on IPFS - with the description, the image link and the socials. Wallets and screeners read the name and symbol from the chain, then fetch the JSON for the rest. On pump.fun the on-chain part sits in the mint itself (Token-2022); on LetsBonk in a Metaplex metadata account; on Bags the Bags API stores the token info and returns the URI.

On a live pump.fun mint the metadata update authority is empty, and launchpads give the creator no way to edit metadata after launch, so the on-chain part is final. The JSON on IPFS is content-addressed - its address is a hash of its content - so it can't be edited either.

The checklist

Name

• Up to 32 characters. Longer names are cut or rejected.
• Check spelling and capitalization - it shows exactly as typed.
• Avoid names that impersonate an existing brand or project; screeners flag them and buyers don't trust them.

Ticker (symbol)

• Up to 10 characters. Short tickers (3-6) read best on screeners.
• Most screeners show it in capitals; decide whether you want it typed that way.
• Search it first - a ticker already used by a large token makes yours hard to find.

Image

• Square, readable at 32 px - most places show it as a small circle.
• PNG, JPG, GIF or WebP; keep it small (well under a few MB) so it loads fast everywhere.
• Check the corners: circular crops cut off anything near the edge.

Description

• One or two clear sentences on what the token is. Bags allows up to 1000 characters.
• No promises of returns - it looks like a scam and can be one legally.

Socials

• Website, X and Telegram links must be live before launch; buyers click them in the first minutes.
• Use full URLs (https://...). A broken link can't be fixed later.

Beyond metadata: the launch itself

• Wallets funded with buffers, not exact amounts (cost breakdown).
• Platform chosen with its extras in mind (launchpad comparison).
• Buy plan decided (snipe, bundle or both).
• Avoid the usual errors (common launch mistakes).

In SolBundle's Launch wizard the token details step enforces the 32/10 limits and shows the image preview; the review step lets you read everything once more before anything is signed. The metadata is uploaded to IPFS only when you launch.

Frequently asked questions