Export pixel art without blurry edges.

Know which dimensions you are exporting

The working grid is the real pixel artwork. If a wide source is converted at a Pixel Detail of 48, the grid is 48 cells wide; zooming the canvas does not change that. Pixel Art Tool offers raster, vector, and editable-project exports.

Native-size PNG · 1×

The exact editable grid with one output pixel per cell. Best for engines and further pixel editing.

Export Scale PNG

The grid enlarged by a whole-number factor with nearest-neighbor edges. The menu shows both native and final dimensions.

Original-size PNG

The pixel result mapped back to the source image dimensions.

Before / after PNG

A flattened source-size comparison with pixel artwork on the left and the original image on the right.

SVG

The native grid expressed as crisp vector geometry with transparent cells omitted.

Project file

An editable backup containing the source, settings, generated grid, and manual edits.

Share the conversion in one comparison image

Source-backed projects can export a flattened before-and-after PNG. Drag the divider, use the 25%, 50%, or 75% presets, then download one source-size image containing the current visible artwork on the left and the original source on the right.

The downloaded image has a clean split by default. Enable Include divider when you want a visible separator baked into the PNG. The preview always shows its divider and draggable handle so the split remains easy to position; neither is exported unless you enable that option.

The comparison uses the same visible-layer composite as normal exports. Hidden layers stay excluded, layer opacity is preserved, and the editor’s Source Reference opacity is not baked into the result.

Use SVG when the destination supports vector artwork

SVG keeps each pixel boundary on the document grid while allowing the artwork to scale without raster interpolation. Pixel Art Tool groups same-color runs to avoid emitting a separate element for every visible cell.

SVG is useful for scalable icons, interface artwork, and vector-capable pipelines. Many game engines and sprite pipelines still work best with a native-size PNG, so confirm format support before choosing SVG for game assets.

Scale by 2×, 3×, 4×, or another whole number

Each source cell should become an equal block of output pixels. A 32 × 24 grid exported at 4× becomes 128 × 96, with every original cell represented by a 4 × 4 square. The grid remains regular.

Fractional scaling asks a renderer to distribute cells unevenly. A 32-pixel image stretched to 100 pixels cannot give every cell the same width, so the browser or image editor blends or alternates boundaries.

Prevent web and social platforms from smoothing the image

Upload a whole-number scaled version large enough for its display slot. If you control the website, keep the rendered width and height proportional to the native grid and use CSS image-rendering: pixelated.

Social platforms often resize uploaded images. A larger 4× or 8× export gives their pipeline more pixels to work with and usually preserves edges better than uploading the tiny native grid.

Use the native grid in game engines

Import the native-size PNG, disable texture filtering or select nearest-neighbor filtering, and keep the pixels-per-unit setting consistent across assets. Disable lossy compression where it introduces color noise or softened edges.

Check the running game at multiple window sizes. Integer camera scaling and a pixel-perfect camera prevent the engine from placing texels between screen pixels.

Run a final crispness check

• Keep the native-size PNG and project file as masters.
• Use SVG only when the destination supports real vector artwork.
• Use whole-number dimensions for enlarged copies.
• Inspect the actual file dimensions, not only the preview zoom.
• Disable smoothing or filtering in the destination.
• Avoid repeatedly resizing and re-exporting an already scaled image.