Pixel Art Avatar Sizes: What to Export, From 16px to 512px
Which size to export for favicons, forums, game icons and profile pictures, why integer scaling keeps pixels crisp, and when to pick PNG, ICO or SVG.
Minecraft Pixel Art Team
Pixel avatars are one of the few art forms where the export size is part of the artwork. A 16×16 icon that looks perfect in a browser tab can turn mushy in a profile picture, and a big portrait can collapse into grey sludge when it is squeezed into a favicon. So the useful question is not "what is the best size?" — it is "which size does each job need?"
The short answer: match the size to the job, and scale in whole-number steps. A 16×16 avatar stays crisp at 32, 48, 64, 96, 128, 256 and 512 pixels, because every original pixel becomes an identical 2×2, 3×3, 4×4 … 32×32 block. In-between sizes force uneven pixels, and the drawing loses the grid look that makes it pixel art in the first place.
This guide walks through the whole export ladder: what each size is for, why whole-number scaling is the one rule that matters, which format (PNG, ICO or SVG) fits which destination, and how to handle platforms that resize your upload themselves. Every size mentioned below can be exported directly from our pixel art avatar icon generator, free and without signing up.
The quick answer: a size ladder, not one "best" size
Different slots need different sizes. This is the ladder we design our export options around:
| Export size | Best suited for | Why this rung exists | | ----------- | ------------------------------------------------------- | --------------------------------------------------------------------------------------------------- | | 16px | Favicons, tiny badges | MDN describes the favicon as "usually, 16 x 16 pixels in size", typically stored as GIF, PNG or ICO | | 32–48px | Small UI icons, list avatars, toolbar buttons | Double or triple the base grid — small, sharp, and readable | | 64–96px | Classic forum avatars, signatures, roster lists | The traditional forum-avatar range; face details still resolve | | 128–256px | Profile pictures in chat apps, game character portraits | Room for skin details like hair strands and eyes | | 512px | Master upload copy | One large file that every platform can downscale from |
Two honest caveats about this table:
- Except for the favicon row, these ranges are craft practice, not official specifications. Chat apps, forums and game engines pick their own display sizes, and they change them between versions.
- That is exactly why the top rung matters: one 512px master covers every display size a platform might choose today or next year.
Why whole-number scaling is the rule that matters
Pixel art is drawn on a fixed grid — in our generator, a 16×16 grid where every face, hair and outfit part is placed pixel by pixel. Each of those 256 cells is one unit of color. What happens when you scale it?
- 16 × 6 = 96px: every cell becomes an identical 6×6 block. Edges stay straight, eyes stay symmetrical, and the picture at 96px is a faithful enlargement of the picture at 16px.
- 16 × 6.25 = 100px: a cell cannot be 6.25 pixels wide, so the renderer alternates blocks of 6 and 7 pixels. Straight edges get jagged steps, the two halves of the face subtly stop matching, and at small sizes the picture looks "dirty" even though almost nobody can say why.
This is also why resizing pixel art in a general image editor usually disappoints: smooth interpolation blends neighboring pixels into intermediate colors, which is the opposite of what pixel art is. The grid is the style.
The practical rule: export at sizes that are whole multiples of the base grid (16 → 32, 48, 64, 96, 128, 256, 512), and let the destination display the size it wants. Because the artwork itself is crisp, every further downscale stays readable.
PNG, ICO or SVG: which format for which job?
Our generator exports all three, and each one has a distinct job:
| Format | Use it for | Strength | | ------ | ------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------- | | PNG | Profile picture uploads, forum avatars, game assets | Universal acceptance, lossless, supports transparency | | ICO | Website favicons | Bundles several sizes into one file so the browser picks the sharpest for the tab, bookmarks bar or taskbar shortcut | | SVG | Web projects, wikis, docs, anywhere vectors are welcome | Infinitely scalable from a tiny text file — one asset covers every display size |
One workflow note: some platforms only accept raster uploads (PNG/JPG) for profile images, so treat PNG as your default deliverable and reach for SVG when you control the rendering — your own site, a game engine UI, documentation.
What about specific platforms?
Chat apps display the same avatar at several sizes — a tiny circle in the member list, a larger popout, a full profile view — and they rescale your upload themselves. Rather than chasing each app's current pixel counts (they change between versions), follow rules that survive those changes:
- Upload a large master. Export 512px and let the platform downscale. Downscaling a crisp, integer-scaled PNG stays readable; upscaling a small one never recovers detail that isn't there.
- Export the exact size when you control the slot. Favicons, forum signatures with a stated size limit, and game UI icon slots take exact dimensions — pick the matching rung on the ladder (a whole multiple of 16) and it stays pixel-perfect.
- Center the face. Most modern apps crop avatars into circles. Keep eyes and mouth away from the corners so the crop doesn't decapitate your character.
- For game tokens and VTT portraits, go bigger. Map tokens get zoomed, so a 256px or 512px export holds up under zoom where a 64px one turns blurry.
Where we verified facts: the favicon convention is documented by MDN (page last modified July 2025). App display sizes are not something we re-measure here — they are design decisions that shift between app versions, and the master-size rule makes the difference academic.
Transparent background or filled?
Both options exist in the generator, and the choice depends on where the avatar lives:
- Transparent blends into any surface — the right default for forum avatars and game UI. One caution: if your outline is dark, it disappears on dark-themed apps; if it is light, it disappears on light themes.
- Filled gives the avatar a fixed frame. A solid retro-palette background reads as a deliberate "card", and it sidesteps the dark/light theme problem entirely.
At 16–32px, background detail is noise — a flat color reads better than a gradient or pattern. Save the detailed backdrops for 128px and above, where there are enough pixels to render them.
One avatar, every size
The nice property of a hand-drawn 16×16 avatar is that it is one artwork, not five. You generate the character once — our generator composes faces, hair, eyes, outfits and extras from hand-drawn parts across 8 retro palettes and 8 skin tones, with optional palette extraction from a photo that runs entirely in your browser — then exports the exact size each destination needs: PNG and SVG for general use, multi-size ICO for favicons, from 16px up to 512px, free, no watermark and no sign-up.
Every avatar also has a 13-digit share code, so the exact same character can be rebuilt by anyone, anywhere — handy when a whole team needs matching avatars at different sizes.
Next step: open the pixel art avatar icon generator, roll a character you like, and export the 512px master plus whatever exact sizes your destinations need. It takes under a minute.