How to upscale pixel art without blur: use integer nearest-neighbor scaling

Pixel art depends on a deliberate grid

A sprite artist chooses the position and color of each pixel. A one-pixel highlight or outline can define a face, movement or silhouette. Treating that grid like a photograph can add intermediate colors, soften the outline or invent texture that changes the design.

At 4× nearest-neighbor scale, each original pixel becomes a 4 × 4 block of the same color. A 32 × 32 sprite becomes 128 × 128 pixels. Width and height multiply by four, while the pixel count multiplies by sixteen. The design gains display size rather than new drawn detail.

Choose the method for the artwork

Nearest-neighbor is suitable when you want to preserve the original blocks. Bilinear or similar smoothing methods interpolate between source pixels and may blur the edge. A general AI photo model can estimate structure and texture, which may be useful for some illustrations but is not faithful pixel-grid preservation.

Upscale a static sprite in the local tool

The pixel art page contains a built-in pixel-grid demonstration. Your selected image stays in your browser for this local transformation; this tool does not send it to the photo-processing service.

1. Open the pixel art upscaler and choose a static PNG, JPG or WebP. Use PNG when you need transparent edges.
2. Select 2×, 4× or 8× and read the proposed dimensions. The source limit is 4 megapixels; output is limited to 16 megapixels and an 8,192-pixel longest side.
3. Preview the source and enlarged version. Check one-pixel outlines, transparent edges and any tile seams.
4. Export the PNG. Keep the source sprite separately for animation or future edits.
5. Check the asset in its destination at an appropriate integer display scale. A later smooth resize can blur the exported grid again.

Preserve transparency and the palette

A JPG input has no transparency and may already contain compression artifacts around blocks of color. Nearest-neighbor enlarges those artifacts too; it does not recover the lost original palette. Prefer the artist's source export when available.

For transparent PNGs, review the alpha edge against both a light and dark background in your destination. The local scaler copies the existing pixel blocks; it is not a background remover or palette repair tool. If an edge is already wrong, correct it in the source editor before enlarging.

Static scaling is different from animation export

This tool exports a single static PNG and rejects animated input. It does not produce GIFs, assemble animation frames, rebuild a sprite atlas or rewrite game-engine metadata. Use a frame-aware workflow when those steps are needed.

For a sprite sheet, treat the result as a larger static image and update any cell dimensions or coordinates in your own tooling. Do not assume the scaler will adjust collision shapes or import settings. Keep grid spacing consistent so the enlarged sheet can still be sliced correctly.

Do not reintroduce blur at display time

An exported sprite can still look blurry if the website, editor or game engine applies smoothing when it is displayed at a different size. Check both the exported file dimensions and the destination's sampling settings. CSS image-rendering controls browser display behavior; it does not alter the stored image file.

If you want to redesign a low-resolution character into a detailed illustration, that is a different creative goal. Use an appropriate drawing or generative workflow and label the result as a reinterpretation. For a faithful larger sprite, preserve the grid and avoid treating extra pixels as new artistic detail.

Common questions