Upload controls, route-specific examples, grid detection, greedy meshing, download, and copy actions hydrate in the browser. The SVG result appears only after a visitor uploads an image or tries the page example. The conversion runs locally with the canvas API.
Each case shows the source pixels, the SVG output structure, and the real use case so visitors can see why the result is different from a PNG preview.
Use case: Print-ready sticker sheets, craft decals, merch mockups
Turn a tiny badge or object sprite into artwork that can scale for print without fuzzy pixels.
16x16 source
SVG output structure: viewBox canvas with grouped <path> fills for each solid color
Use case: Asset catalog pages, manuals, wiki previews, UI kits
Document icons and inventory art as SVG while preserving hard square edges instead of trace curves.
UI export
SVG output structure: one scalable SVG that keeps the original pixel grid as vector blocks
Use case: Badges, overlays, embroidery references, laser-cut guides
Skip transparent cells so the exported vector stays clean on dark, light, or printed backgrounds.
alpha aware
SVG output structure: transparent cells omitted; only visible pixels become path geometry
Free · no signup · runs in your browser
Turn pixel art into pixel-perfect, infinitely scalable SVG. Every pixel stays a crisp square, not a blurry curve, and your image never leaves your device.
Most image-to-vector tools trace the picture: they fit smooth Bezier curves to shapes, which is useful for logos and photos but wrong for pixel art. Tracing rounds off hard edges and turns a crisp 8-bit look into soft blobs.
This converter reads the native pixel grid and turns every pixel into an exact SVG rectangle, so the result is a faithful, blocky vector you can scale to any size without blur.
It works well for stickers, decals, laser cutting, embroidery, print, crisp game UI, Minecraft skins, sprite sheets, icons, and retro game art.
The questions people ask most.
Drop a PNG or GIF onto the converter above. It detects the native pixel grid, turns every pixel block into an SVG rectangle, and merges same-colored blocks so the file stays small. Then download the SVG or copy the code. Everything runs in your browser.
No. The whole conversion runs locally in your browser using the canvas API. Your image never leaves your device, so it works offline and keeps private art private.
General vectorizers like tracing tools smooth and round hard edges into curves, which destroys the crisp square look of pixel art. This tool keeps every pixel as an exact rectangle, so the SVG is a faithful, blocky vector copy. For a full walkthrough with measured file-size comparisons, see the guide at /pixel-art-to-svg-guide.
Yes. Minecraft skins are pixel art, so drop the skin PNG in and you get a clean SVG of the exact pixels — handy for stickers, decals, laser cutting, and print.
Yes. A sprite sheet converts to one SVG that preserves every pixel. If you need individual sprites, crop the sheet first, then convert each frame.
Greedy meshing merges adjacent same-colored pixels into a single larger rectangle. Instead of thousands of 1x1 squares, you get far fewer rectangles, which makes the SVG dramatically smaller and faster to render — with identical visual output. For a full walkthrough with measured file-size comparisons, see the guide at /pixel-art-to-svg-guide.
A clean integer nearest-neighbor upscale can be reduced back to the native grid, but it adds no detail and is not better than the original source. A smoothed, non-integer, rotated, or recompressed upscale hurts because blended edge colors can be mistaken for real cells. Use the native-resolution image whenever available.
Crop the frame on exact grid boundaries, preserve its native cell dimensions and transparency, then convert that crop. If you also need the complete atlas or repeated frame handling, use the sprite sheet to SVG workflow and decide whether downstream code benefits from one sheet or separate SVG files.
Yes: the vector geometry is redrawn for the display, so it is not limited to a fixed raster density. Keep the native viewBox, integer-aligned shapes, and shape-rendering="crispEdges"; for the most uniform block sizes, also avoid fractional CSS transforms or layout dimensions that force grid boundaries between device pixels.