The Pump.fun coin image guide, from size to what actually reads
What size and format to use for a Pump.fun coin image, why it gets judged at 64 pixels, and the design choices that survive that test.
Your image is the only thing most people will ever see of your coin. Not the description, not the socials, not the chart. A square, roughly 64 pixels wide, moving past in a feed.
So it's worth an hour, and most creators give it four minutes.
The specification
Square. At least 512 by 512 pixels. PNG or JPG.
Why 512 when it displays at 64? Because a handful of surfaces render it larger, and a 128-pixel upload blown up to 400 looks like a mistake. Uploading big and letting things downscale costs nothing.
Keep the file reasonable, under a few hundred kilobytes. An enormous file loads slowly on mobile, and a placeholder square where your logo should be is worse than a plain logo.
The test that decides everything
Take whatever you designed. Shrink it to 64 pixels. Look at it on your phone, outdoors if you can.
Can you tell what it is? That's the whole test. Almost every image failure comes from designing at 1000 pixels on a large monitor and never checking the size people actually see.
At 64 pixels you have room for one idea. One shape, one face, one strong colour relationship. Not a scene, not a paragraph of text, not a detailed illustration with three focal points.
What survives shrinking
Some patterns hold up and some collapse, reliably.
High contrast survives. Subtle tonal work becomes grey mush. Your image needs to separate from a dark feed background, so mid-greys and low-contrast palettes disappear.
Single subjects survive. One recognisable thing, centred, with breathing room. Compositions with several elements turn into visual noise.
Bold silhouettes survive. If the shape reads with the detail removed, it reads at 64 pixels. If it depends on internal detail, it doesn't.
Thin lines and small text die. A 2-pixel line at full size vanishes entirely. Text under maybe 30% of the frame height becomes an unreadable smudge that still costs you space.
The mistakes that repeat
Text-heavy images are the most common failure by a wide margin. Creators put the ticker, a tagline and a slogan into the square, none of which is legible, all of which crowds out the one thing that might have read.
Borrowed art is the second. Grabbing an existing character, logo or meme image implies an association you don't have, and experienced buyers read that as a warning sign rather than a joke.
Then there's the busy background. A detailed scene behind your subject destroys the silhouette. Flat colour or a simple gradient behind one clear shape beats a beautiful illustration every single time at this size.
And finally, the near-duplicate. If your image looks like 40 other coins in the feed, it does the opposite of its job.
How it works with the name
Image and ticker get judged together, in one glance.
Which order? Usually the image first, because it's larger and the eye lands there. So the image needs to work alone, and the ticker needs to confirm rather than explain. How to name a Pump.fun coin covers the naming half of the same problem.
Test them the way a stranger meets them: image at 64 pixels first, ticker second, nothing else. Whatever survives that is what you actually shipped.
Where else it appears
Worth knowing the surfaces, because they crop differently.
Pump.fun shows it small in feeds and larger on the coin page. Terminals like Photon and Axiom show it in dense lists. Screeners show it beside the pair name. Some places round the corners, some show a circle, and a design with critical content in the corners loses it.
Keep the important part inside a centred circle covering about 80% of the square. Then no crop can damage it.
What the image can't do
Now the part that keeps things in proportion.
A perfect image doesn't get your coin discovered. Discovery surfaces read volume, trade count, unique wallets and recency, and none of them look at your art. A beautifully designed coin with 5 trades stays invisible in every feed that exists, which means the image you spent an afternoon on never actually reaches a single pair of eyes.
So the image belongs to the "make the page worth arriving at" half of a launch. It decides whether arrivals stay. Something else has to decide whether arrivals happen at all, and that part is covered in the launch checklist.
Quick checklist
- Square, 512 by 512 or larger
- Under a few hundred KB
- One subject, high contrast, bold silhouette
- No small text, no thin lines
- Important content inside a centred circle
- Checked at 64 pixels on a phone, not on your monitor
If the image breaks after minting rather than before, coin image not loading covers the metadata chain behind it. If you've done all six and the coin still isn't moving, the image was never the constraint. The console prices sustained activity against a specific window and wallet count if distribution is the gap.
Frequently asked
Square, and at least 512 by 512 so it stays sharp when a terminal renders it larger. It gets displayed far smaller than that in most places, but a low-resolution upload looks broken on the few surfaces that show it big.
No. Image, name and ticker are written at mint. Test it before, because there's no revision afterwards.
Rarely worth it. Many surfaces show a static frame anyway, and a design that only works in motion fails everywhere the motion is stripped.
Everything in this guide describes mechanics that settle on Solana mainnet, so you can check any of it yourself. Mint addresses, swap signatures, curve progress and wallet counts are all public, and an explorer will disagree with us if we are wrong.
Curvegrad sells a volume service, and guides that touch on what a campaign does say so in the text rather than in a footnote.
- Solana mainnet transaction history, read through the standard RPC methods
- Pump.fun bonding curve and PumpSwap pool accounts as they appear on-chain
- Public block explorers, where every claim here can be verified against a real mint
- Campaigns run through our own engine, which is where the operational detail comes from