PNG to SVG Converter

Convert PNG to SVG: What This Tutorial Covers

This converter traces your PNG and rebuilds it as a true SVG — real vector paths and curves, not the original pixels base64-encoded inside an SVG wrapper. Because PNG is lossless, it is the ideal trace input: there are no JPEG-style compression artifacts to confuse the tracer, so flat-color graphics come out cleaner than the same image saved as JPG. This page walks through the conversion, the one setting that matters, and the cases where tracing is the wrong tool.

How to Convert PNG to SVG

1. Upload Your PNG File: Drag and drop your .png file onto the page, or click "+ Add Files" to browse. You can queue several images and trace them with the same setting.
2. Set Number Precision: Open Advanced Options and adjust the Number precision slider (1–10). This controls how many decimal places the traced path coordinates keep — lower values shrink the file, higher values retain fine detail. A value of 4–6 suits most images.
3. Start From a Clean Source (Optional): Tracing follows exactly what is in the image. A sharp, high-contrast PNG with a small palette — a logo, icon, or line drawing — traces far more cleanly than a busy or photographic one.
4. Convert and Download: Click "Convert" and download your SVG. No sign-up, no watermark.

Walk-through: What "Number Precision" Actually Does

An SVG stores shapes as coordinate paths in plain text, like M12.34,56.78 C.... The Number precision slider sets how many decimal places those coordinates keep:

• Want the smallest file? Lower the slider (toward 1–3). Coordinates round to fewer decimals, so the text is shorter. On most artwork the visual difference is invisible — two or three decimals is a common professional default.
• Want to preserve fine curves and tiny detail? Raise it (toward 7–10). The paths describe sub-pixel positions more exactly, at the cost of a larger file. Beyond about 6 the extra precision rarely changes what you see — it mostly adds bytes.
• Tracing a logo for the web? Stay around 4–5. That keeps edges crisp while producing a compact file that loads quickly.

Precision does not add detail that the trace did not find — it only decides how exactly the found paths are written down. If the output looks blobby, the fix is a simpler, higher-contrast source image, not a higher precision value.

Common Errors and How to Fix Them

• "The SVG looks blobby, posterized, or nothing like my photo" — You traced a photograph. Continuous-tone photos have millions of colors and soft gradients that vectorizing collapses into flat color blobs. Tracing is built for logos and line art; for a photo, keep it as a raster (compress the PNG or convert it to JPG) instead.
• "The SVG file is huge — bigger than the PNG" — Busy or photographic images force the tracer to create thousands of paths, one per color region, which can balloon the file far past the original. Simplify the source — fewer colors, higher contrast — or accept that this image is not a good vectorization candidate.
• "Edges came out fuzzy or fringed" — Anti-aliasing softens the boundary between a shape and its background with a ring of in-between pixels; the tracer reads those as extra thin shapes. Exporting the source PNG with crisp, aliased edges (or a larger version) gives the tracer a cleaner boundary to follow.
• "My transparent background turned into a solid shape" — Tracing works on color regions, so a flat backdrop can be traced as a filled rectangle rather than left empty. Crop tightly to the artwork, or remove the background before tracing so there is nothing behind the subject to vectorize.
• "I expected my logo back as editable layers" — Tracing rebuilds the picture as filled vector shapes grouped by color, not as your original named layers or fonts. Text becomes outlined paths, not live, re-editable type.

When This Doesn't Work

Vectorization is the wrong tool for photographs, screenshots full of text, and any image with smooth gradients or thousands of colors — the trace will be inaccurate and the file bloated. It shines on flat-color graphics: logos, icons, stencils, silhouettes, and line drawings, where a PNG's lossless edges trace especially well. If you only need a smaller raster rather than true scalable paths, compressing the PNG is the better move. And if you later need a flat image back from an SVG, the reverse SVG to PNG conversion rasterizes it cleanly.

Frequently Asked Questions

Does this embed the PNG inside an SVG or actually vectorize it?

It vectorizes. The converter runs the open-source vtracer engine, which traces shapes and edges and rebuilds the image as real SVG paths and Bézier curves — it does not base64-encode the original pixels into an <image> tag. That means the output is genuinely resolution-independent for suitable artwork, rather than the same raster picture in a new container.

Why does a PNG trace better than a JPG of the same image?

PNG is lossless, so it preserves clean, exact edges with no compression blur or block artifacts. JPEG is lossy and adds those artifacts, which the tracer faithfully follows — softening edges and creating stray shapes. Because the vtracer engine traces whatever is in the pixels, the lossless PNG gives it a sharper boundary to follow, so flat-color art generally traces cleaner from PNG than from the same image saved as JPG.

Will a photograph convert to a clean, scalable vector?

No. Photographs have continuous tones and millions of colors, so tracing approximates them as many flat color shapes — the result looks posterized and inaccurate, and the file is often far larger than the PNG. Tracing is designed for logos, icons, and line art with limited colors and clear edges. For a photo, keep a raster format.

What value should I use for Number precision?

For most artwork, 4–6 is the sweet spot — crisp paths at a reasonable file size. Drop toward 1–3 when you need the smallest possible file and can accept slightly rounded coordinates; only push toward 8–10 if you genuinely need sub-pixel accuracy, since beyond 6 the extra decimals usually add bytes without a visible change.

Does my PNG's transparency carry into the SVG?

Not as an alpha channel the way PNG stores it. Tracing rebuilds the picture from solid color regions, so a transparent area is best handled by leaving nothing behind the subject — crop to the artwork or remove the background first, and the traced shapes simply won't cover that space. A semi-transparent drop shadow, by contrast, gets flattened into a flat-color shape rather than a soft fade.

Can browsers and design apps open the resulting SVG?

Yes. SVG is a W3C XML-based standard supported by Chrome, Firefox, Safari, and Edge — caniuse reports roughly 97% global browser support — and it imports into Illustrator, Inkscape, Figma, and most vector editors. In our testing, a flat two-color PNG icon traced at precision 5 produced a compact SVG that opened identically in the browser and in Inkscape.

Is my file kept private?

Yes. Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically a few hours after conversion — no sign-up, no watermark, never shared or made public.