The email was one line: “Can you get us a web version of the logo that scales without going blurry?” Attached was a 400 by 130 PNG pulled off a business card. They had already paid someone to convert it to SVG once, and that file came in at 1.9MB looking like the mark had been drawn with a burnt crayon.
That second file is the problem in one object. Something converted it in four seconds, and the result was technically vector, technically scalable, useless above 60 pixels wide. What follows is what “convert” hides, which files survive it, and the slower route a print shop will accept.
What “converting a PNG to SVG” actually means
Two jobs hide behind that phrase, and nearly every converter on page one does the first one.
Tracing means software reads pixel edges and lays bezier curves over them, one closed path per colour region. The machine guesses where a curve ends, how many anchors it needs, whether a dark patch is a counter or dust.
Rebuilding means drawing the thing again. Circles get a real centre and radius, a 3mm corner is 3mm instead of forty anchors pretending, and stroke widths stay editable.
The gap shows up in code. One fragment of what a tracer produced for a two-colour wordmark, and the same shape rebuilt by hand:
traced <path d="M118.4218 63.9017 L119.7733 62.4102 C120.8779 61.2102 121.6791 59.6481 121.9952 57.9505 L123.1037 52.9188 C123.2998 51.5924 123.1402 50.2317 122.6421 48.9971 L121.8893 47.2144 Z" fill="#1c1c1c"/>
rebuilt <path d="M118 64 L124 52 H132 L126 64 Z" fill="#1c1c1c"/>
Three hundred and eleven paths in that file looked like the first line. The second is the same silhouette with twelve coordinates instead of roughly 2,400, and either anchor can be nudged without the next curve jumping sideways.
Before you convert, three checks
- Ask for the original. Plenty of “we only have the PNG” cases have an AI, EPS, or PDF in an old folder, and a PDF opened in Illustrator keeps real paths.
- Measure the file, not the preview. Under 600px wide, the edge detail you need is already gone, so the tracer smooths guesses.
- Count the colours. Two to six solid tones and tracing has a chance. Hundreds of values and it does not, at any panel setting.
We ask all three before quoting, and half the time the estimate drops to a five-minute export.
When tracing works, and when it wrecks the file
Flat art and photographs are different problems, and one has no vector answer at any price.
| Source file | Verdict | What you get |
|---|---|---|
| Flat logo, 2 to 4 solid colours, clean edges | Trace is fine | Regions follow the original closely, node count in the low hundreds |
| Single-colour icon or pictogram | Trace is fine | One fill region, easy to over-simplify; watch small counters |
| Photograph, product shot, any texture | Do not | Every tonal step becomes an edge; a 1200px photo at 8 colours hit 41,000 anchors and 3.4MB |
| Gradient, glow, or soft shadow | Do not | No gradient model, so you get banded solids and visible steps at 100% |
| Thin script type, hairline serifs | Do not | Sub-pixel stems arrive as wobbling blobs, or swell until counters close |
| Screenshot containing body text | Do not | Wrong skeleton and spacing; set the words as text instead |
The photo row is the one people argue with. A traced portrait that looks like a woodcut will not improve with more colours; the node count climbs with them.
Thin type fails for a duller reason. A one-pixel stem has three or four partly transparent pixels of edge, so the tracer cannot locate the stroke and the edge wobbles by half a pixel, which reads as a printing error at 16px.
The manual rebuild route, step by step
This is the route for that logo, and it is not glamorous. A two-colour wordmark takes 15 to 40 minutes once you know the mark. A mascot takes a day, which is what you quote.
- Lock the PNG as a template at 30% opacity and set the artboard to the largest size the artwork will ever print at.
- Decide primitives or pen before you pick up the tool. About half of commercial marks are circles, rectangles, and straight bars, so draw circles and bars.
- Hand-trace only lettering, silhouettes, and drawn edges: one anchor per real corner, one curve segment per arc, handles pulled to the tangent. Curve handles on a straight line are why hand-traced logos wobble.
- Type the numbers where you can. Real ellipse, real corner radius, Pathfinder Unite on overlaps, then check at 16px, 240px, and 1200px and mirror it. Symmetry errors hide until the mark faces the other way.
You end up with about 40 anchors instead of 2,400, and often a file lighter than the source PNG.
Cleaning a traced file before it goes anywhere
A trace worth keeping is still only step one. Uncleaned files share a family of defects that show at small sizes.
- Delete the background rectangle. White paper became a path, so your logo is a white box covering the header behind it.
- Reduce nodes. Simplify in Illustrator or Inkscape, corner angle above 70 degrees. A 40% cut looks identical; 80% does not.
- Kill the slivers. Delete shapes under a few pixels, merge shapes sharing a fill, or the seam shows on a dark background.
- Round coordinates on purpose. Two decimals for screen, three for 400mm print. Four costs 15 to 30% of file size for accuracy nobody sees.
- Optimise last. SVGO at precision 2 once the geometry is right, then confirm the viewBox survived. Our SVG optimization guide lists the settings that are safe.
Do the pass at 400% with outlines on, then look at 16px, where clean shapes turn grey.
Tools that claim to do it, and what they cost
None of the automatic options write geometry. They all trace, some better.
- Potrace, free, command line or inside Inkscape. Single colour only, still the best automatic output for scans and stamps.
- Illustrator Image Trace, about $23 a month. Black and White Logo preset, Threshold 128, Paths 90%, Corners 75%, Noise 25px.
- Vector Magic, browser upload, roughly $10 a month. Cleanest automatic result on flat two-colour marks in our tests, and wasted on soft edges, since no subscription makes a tracer invent a gradient.
- Adobe Express, Convertio, and the lookalikes, free tiers. Wrappers over the same engines, no node control, useful for finding out in ten seconds whether a file is traceable.
Prices move, so check first. Once a job needs a second cleanup pass, the tool stops mattering and the rebuild wins.
Where our own editor fits, and where it does not
Straight answer first. The SVG editor on this site will not convert a PNG. You cannot drop a raster in and get paths out, and there is no tracer inside it.
It handles the part after. Paste SVG code or open an .svg file and each shape becomes a layer you can select, move, scale, rotate, and recolour. Hide or delete the stray paths a tracer left, set a stroke width to zero instead of deleting it, and export minified SVG.
It cannot move a single anchor and has no boolean union, so a rebuild belongs in Illustrator or Affinity. Our other tools sit on design tools.
Three questions people ask about PNG to SVG
Can you convert a PNG to SVG without losing quality?
Not for anything photographic. A conversion cannot create information the file does not hold, so the choice is a trace approximation or a rebuilt shape. Flat art with a few solid colours comes out identical; a photo becomes a banded imitation of itself.
Is the SVG smaller than the PNG?
Usually not, which surprises people who converted for file size. A flat 400px logo PNG can be 40KB and the same mark traced properly lands near 180KB, because solid areas compress to nothing as pixels and cost real bytes as paths. If bytes are the problem, WebP wins.
Which converter gives the cleanest result?
For a flat two-colour mark, Vector Magic at its highest detail setting beat Illustrator’s presets and everything else we tried. For a single-colour scan, potrace with a generous turd size wins, because it discards noise instead of tracing it. For anything with type, none of them.


Leave a Reply