Pixel Art for Game Development
Pixel art and indie games go hand in hand, so let me be straight about where a photo converter fits: it won't replace a real sprite artist. What it's great at is speed. It gets a placeholder on screen so you can build and test your game before the proper art exists, and it's a surprisingly good way to test whether a palette and resolution will work before anyone draws a thing.
By Richard Wallace · Published 5 August 2026 · Updated 5 September 2026
Where it fits in a project
The honest version is this: converting a photo gives you a pixelated image, not a game-ready animated sprite. What it does brilliantly is get you moving. In early development you constantly need something on screen to test movement, collisions and layout, and you need it now. That's exactly the gap a converter fills, as a source of fast, throwaway placeholders that look roughly right while the real art is still being made.
Pick a target resolution first
The single most useful decision in a pixel-art game is the size of the virtual screen, because it decides how big every sprite and tile can be. Most retro-styled games pick a small internal resolution and scale it up by a whole number to fit the player's display.
| Internal resolution | Feels like | Scales cleanly to |
|---|---|---|
| 128 × 128 | PICO-8 | 1024 × 1024 at 8x |
| 160 × 144 | Game Boy | 1440 × 1296 at 9x |
| 256 × 224 or 256 × 240 | NES / SNES | 1024 × 960 at 4x |
| 320 × 180 | Modern "16:9 retro" | 1920 × 1080 at 6x |
| 384 × 216 | Modern, more detail | 1920 × 1080 at 5x |
| 480 × 270 | Modern, high detail | 1920 × 1080 at 4x |
Once you know the internal resolution, you know how big a placeholder needs to be. A character that's meant to stand 32 pixels tall on a 256 × 224 screen needs a converted image that's 32 blocks tall, no more. The pixel size guide has the one-line formula for getting there from any photo.
Quick placeholder sprites
Grab a photo or reference of the thing you need, whether it's a character, an item or a prop, crop it tight, and convert it at a pixel size that gives you the right number of blocks for your target resolution. Drop it into your engine as a stand-in. It'll sit far more happily in a pixel-art project than a grey box or a full-res photo, and it cost you about a minute. Swap it out when the real sprite lands.
One thing to know: the converter exports at the same dimensions as the source, with each block drawn as a square of pixels. For a placeholder you usually want the small version, one pixel per block, so resize the export down by the pixel size you used, with nearest-neighbour resampling. A 640-pixel export at pixel size 20 becomes a 32-pixel sprite.
Prototype mock-ups
Before you commit to a look, it helps to mock up a scene. Convert a few references with one consistent palette and stitch them into a rough screenshot of how a level might feel. Keeping the whole mock-up in a single palette, say NES or PICO-8, gives you a quick read on the game's mood and colour without drawing anything from scratch. The palette guide is handy for picking one that fits, and the palette reference pages give you the exact hex codes to carry into your engine and your art tools.


Prototype faster. Turn a reference photo into a placeholder in seconds.
MAKE A PLACEHOLDERReference and moodboards
Even if you never ship a converted image, pixelating references is a useful way to think. Seeing a real object reduced to a limited palette and low resolution shows you which colours and shapes actually survive, which is genuinely helpful when you or your artist go to draw the proper sprite. It's a fast way to answer "what will this even read as at 32 pixels?"
Engine settings that keep pixels crisp
Whatever you use, the same three settings matter. Get them wrong and your beautifully blocky placeholder turns into a blurry smear the moment it's drawn.
- Texture filtering off. In Unity set the sprite's Filter Mode to Point. In Godot set the texture filter to Nearest. In GameMaker turn off interpolation between pixels. Pixel-art templates in most engines do this for you.
- Whole-number scaling. Scale the internal resolution by 2x, 3x, 4x and so on. Fractional scaling makes some pixels wider than others and looks wobbly.
- Pixels per unit consistent. If one sprite is imported at 16 pixels per unit and another at 32, they'll be different sizes in the world for no good reason. Pick one value and stick to it.
The converter preserves transparency from your source image in the PNG export. If your photo has a background, remove it in an image editor before or after conversion. Converting a subject shot against a plain, contrasting background makes that a one-click job with a magic-wand tool.
Keeping assets consistent
- Pick one pixel size that matches your target resolution and use it for every placeholder, so nothing looks out of scale.
- Stick to a single palette across the prototype for a cohesive look.
- Export as PNG to keep hard edges and a transparency-friendly workflow in your engine.
- Treat them as temporary and label them clearly, so a placeholder never sneaks into your final build.
When to draw or hire instead
For shipping something polished, hand-crafted sprites and animation are worth every penny. A converter can't produce clean, frame-by-frame animation the way an artist can, and it can't make the deliberate simplifications that make a 16-pixel character readable. So think of it as part of your prototyping kit: brilliant for getting moving quickly, and honest about where the craft of a real pixel artist takes over. Used like that, it genuinely speeds up the messy early days of a project.
◀ ALL GUIDES