My Business Cards Came Back From the Printer Looking Like I'd Designed Them at 2am
The designer I'd hired had retired and taken his source files with him. All I had was a PNG of my logo — a clean, flat, two-color mark that looked fine on screen but fell apart the moment the printer tried to scale it. The print shop said they needed a vector file or they couldn't guarantee quality. I converted the PNG to SVG, opened it in Inkscape, tidied up three stray paths, and sent it over. The next batch of cards came back exactly right.
Upload files
Files are processed on our server and deleted automatically when the job finishes. Nothing is stored or shared.
Why I'd never heard of PNG-to-SVG before I needed it desperately
I'd always thought of format conversion as a simple swap — same image, different container. PNG to SVG isn't that. It's reconstruction. The tool looks at my logo's pixels and infers the geometric shapes behind them, then rebuilds the whole thing as mathematical paths. When it works, you end up with a file that scales to any size without a single blurry edge. When it doesn't work, you end up with a mess of tiny paths that look like the logo exploded. The difference between those two outcomes is almost entirely about what's in the PNG you start with.
What I learned preparing the PNG before converting
My first attempt at converting the logo produced a result that was... technically correct but noisy. There were extra paths around the edges, the background white had been traced as its own region, and some of the letterforms had small stray segments I had to clean up manually.
Before my second attempt I did three things: I used the background remover to strip the white background, leaving the mark isolated on transparency. I boosted the contrast slightly in an image editor — the edges between the two logo colors became sharper. And I upscaled the PNG from 400px to 1200px using a nearest-neighbor resize, which gave the tracer cleaner boundaries to work with. The second SVG was dramatically cleaner. Two paths, correct fills, no noise.
Those three steps — transparent background, increased contrast, larger source image — are what I'd tell anyone to do before they try this conversion.
What actually traces well versus what produces chaos
This conversion is honest about its limitations if you know what to look for. My logo worked well because it was a flat two-color design — exactly the kind of image that vectorization was built for. Here's the broader pattern I've come to understand:
- Works well: Logos and wordmarks with 2–5 flat colors, icons with clear silhouettes, black-and-white line art, hand-drawn illustrations with clean outlines and no gradients.
- Works poorly: Photographs of any kind — faces, products, landscapes. The tracer produces hundreds or thousands of micro-paths that don't clean up into anything useful. Also gradients, drop shadows, and anti-aliased edges — these create blended pixel regions that trace into noise.
If you're not sure whether your PNG is a good candidate, try it and look at the output file size. A clean conversion of a simple logo should produce a small SVG. If the output is several megabytes, the tracer created thousands of paths trying to approximate something it couldn't represent cleanly.
After the SVG comes out — what to do with it
Even a good SVG conversion usually needs a few minutes of cleanup in Illustrator, Inkscape, or Figma. What I look for:
- Stray paths: Small isolated path fragments around edges, usually from anti-aliasing in the source PNG. Select and delete them.
- Duplicate shapes: Sometimes the tracer produces overlapping paths for the same region. Merge or delete the redundant ones.
- Path simplification: Clean SVGs use fewer path points. Most vector editors have a "simplify paths" function that reduces point count without changing the visible shape.
Ten minutes of this and you typically have a clean, print-ready SVG. That's a reasonable trade for not having to recreate the logo from scratch.
Files processed privately — deleted after conversion
Your PNG uploads over HTTPS and is processed in temporary storage. Both the original PNG and the generated SVG are deleted automatically when the conversion finishes. No account needed.
Frequently Asked Questions
My SVG looks nothing like the original PNG. What went wrong?
Vectorization approximates images as geometric shapes. If the PNG had gradients, soft shadows, or photographic content, the tracer can't represent those cleanly. For logos and flat graphics on a transparent background, results are much more accurate. Remove the background before converting if you haven't.
Can I edit the SVG afterward in Figma or Illustrator?
Yes. Both tools open SVG files natively. For simple, clean conversions you'll have a handful of editable paths. For more complex conversions you may have many grouped paths — technically editable, but worth simplifying before doing detailed work.
Will the SVG be smaller than the PNG?
For a 2–3 color logo: yes, often significantly smaller. For anything complex that produced many traced paths: the SVG may be larger than the PNG. Check the output size — it tells you a lot about how cleanly the conversion went.
My PNG has a transparent background. Will the SVG keep it?
Yes. Transparent regions in the PNG are excluded from the traced paths. The SVG will have no background fill in those areas — it will be transparent when placed in Figma, on a webpage, or in print software.
Are my files stored after conversion?
No. Files are deleted automatically as soon as the conversion job completes.
Other tools in this workflow
Explore more free tools
Need a different format or workflow? These tools are part of the same Plomz toolkit and work the same way.