PNG to SVG: why it needs tracing, and what to do instead

People searching for "PNG to SVG" usually want one of two very different things: a vector drawing that scales to any size without going blurry, or simply an SVG file that shows your PNG. The first needs a real tracing algorithm; the second is three lines of text. This page explains both, and says plainly why the tools on this site don't do the tracing part.

Why a PNG can't become a real SVG on its own

A PNG is a grid of coloured pixels. An SVG is a list of instructions — "draw a circle here", "fill this shape" — that a renderer turns into pixels at whatever size you ask for. Nothing inside a PNG says "this cluster of pixels is one smooth curve", so there is no single correct answer to convert: the shapes have to be guessed. That guessing is called tracing (also vectorising or auto-trace), and it is real image analysis, not a file rename.

Every tool on this site works the other way round: it decodes an image with your browser's built-in decoder, then re-encodes the result on your device. Browsers have no tracer built in, and because nothing is ever uploaded here, there is no server-side tracer either. So there is no button on this site that says "PNG to SVG" — it would quietly hand you an SVG that still contains your bitmap, and call it converted.

Option 1: trace it with free software on your own computer

Inkscape is free, works offline on Windows, Mac and Linux, and is the usual answer. Open the PNG, choose Path → Trace Bitmap, pick a preset (a bright, smooth logo and a detailed photo want different ones), press OK, and it creates a path you can edit. File → Save As then writes the SVG. Because it runs locally, your image never leaves the computer — the same privacy property as the tools here.

For a simple mark — a letter, a badge, an icon — redrawing beats tracing. Ten minutes with a pen tool gives you a file a fraction of the size that stays sharp at any resolution. Photographic images are the wrong input for a vector format in the first place: the traced file often ends up larger than the PNG it came from.

Option 2: wrap the PNG in an SVG (no tracing at all)

If what you actually need is "get this logo into a design tool, a slide deck or a print job that only accepts SVG", you don't need tracing. You need an SVG that points at the PNG. Save the next block as logo.svg in the same folder as logo.png, using your image's real pixel size:

<svg xmlns="http://www.w3.org/2000/svg" width="512" height="512">
  <image href="logo.png" width="512" height="512"/>
</svg>

That is a genuine SVG file, and any program can open it. It is not a vector version of your picture: it still shows the original pixels, it still has one fixed size, it will look soft when scaled up, and the PNG has to travel with it.

Option 3: find the vector original first

Before converting anything, check whether a real SVG already exists. If the logo came off a website, that site's own /favicon.svg, or an inline <svg> block in the page source, may be the original. If a designer or an agency made the logo, ask them for the vector file — that is the version they actually drew, and it beats any trace. If you drew it yourself, export SVG straight from the drawing app.

What this site can do with the PNG

The tracing itself doesn't run here, but the preparation usually does. Crop and rotate squares the image and trims the empty margin around a logo; Remove EXIF deletes location and camera data before you hand the file to any other program; Resize to exact pixels makes it the size a tool expects; Compress image makes it smaller to upload; and Favicon generator turns a PNG or SVG logo into every icon size a website needs, as real PNG files rather than a trace.

Questions