How to Choose Your Pixel Art Sprite Size

Guide · Back to guides

PixelCraft Studio editors · Last updated: August 2026 · About a 6-minute read

The first thing that trips up new pixel artists usually isn't brush technique or color choice - it's "how many pixels should this character actually be?" Skip that decision and you'll often end up with a sprite that doesn't line up with your tilemap, turns blurry when scaled, or needs more animation frames than you can realistically draw. This guide lays out how to pick a sprite size using the same rules real games are built on.

Why sprite size matters this much

Sprite size isn't just "how big it looks on screen." Once you commit to a size, it decides how much detail a character can carry, how much work each animation frame takes, how the sprite aligns to your tilemap, and even how large a touch target feels on mobile. Changing size mid-project usually means redrawing everything you've already made, so locking it in before you draw is the single biggest time-saver in pixel art production.

Common sprite sizes and what they're for

16 / 32 / 48px 64px
Canvas area by size at the same on-screen scale. Double the size and you have four times as many pixels to fill.
Use case and workload by size (indie 2D games)
SizeMain useDetail it can carryWork per frame
16x16UI icons, minimap markers, ultra-simple charactersSilhouette, 2-4 colorsVery low
32x32Standard indie character, objectsExpression, clothing, weaponLow
48x48Player character, mini-bossLimb motion, readable gearMedium
64x64+Bosses, cutscene portraits, card artIllustration-level shadingHigh

Resolution, canvas size, and display size are three different things

One of the most common mistakes is drawing a 32x32 sprite and then rendering it on screen at literal 32-pixel size. On modern displays that makes the character look tiny in a corner of the screen. Instead, scale it up by an integer factor (2x, 3x, 4x, and so on) - a 32x32 sprite rendered at 4x becomes 128x128 on screen. Scaling by a non-integer factor (like 1.5x) smears the pixel edges and destroys the crisp, blocky look that makes pixel art read as pixel art in the first place, so it's worth avoiding entirely.

When you need to resize an original sprite or check how it looks at different scales, the image resize tool runs entirely in your browser and lets you try scale buttons instantly.

If you use a tilemap, align to the grid first

For platformers or top-down RPGs where characters move across a tilemap, it helps to size your character as a multiple (or divisor) of your tile size. If your tiles are 16x16, characters are often drawn at 16x32 (one tile wide, two tiles tall) so they line up cleanly with the grid. That makes collision detection, camera scrolling, and level design far more predictable.

Practical checklist

Once you've settled on a size, browse the pixel image picks page for icons at a similar density, or resize your own artwork instantly with the image resize tool.

Frequently asked questions

Does a sprite have to be square?

No. Keep the canvas square (like 32x32), but the character inside can be tall or wide. If you use a tilemap, it helps to make the character's actual footprint a multiple of the tile size so placement stays predictable.

Can I change the sprite size mid-project?

You can, but you'll have to redraw most of what you already made. Scaling up by an integer factor (2x, 3x) keeps pixels crisp, but shrinking or non-integer scaling smears detail. Locking the size before you draw is the safe move.

Do mobile games need larger sprites?

Not in pixel count. Draw at 32x32 and render at 3x-4x on screen. Just make sure anything the player taps ends up at least about 44px in its final displayed size.