When to Vectorize an Image (and When Not To)

🖼️ Images⏱️ 6 min readFree tool included

"Convert image to SVG" is one of the most searched image tasks, and most of those searches end in disappointment — because vectorizing is powerful for exactly one category of image and a bad idea for the other one. The dividing line isn't file format or size; it's how many colors your artwork really has. Here's the pipeline, the trade-offs, and the decision rule.

Advertisement

What does image-to-SVG tracing actually do?

A tracer runs three stages. First, color quantization: the image is reduced to a fixed palette (you choose the size — 2, 8, 16, 64 colors) using a k-means-style clustering pass, the same family of algorithm behind GIF and PNG-8. Second, edge following: for each palette color, the algorithm walks the boundary between regions of that color and everything else, recording the boundary as a chain of sample points. Third, curve fitting: splines are fitted through those points — with corner detection so hard angles stay hard — and each region is written out as an SVG <path> with a fill. The result is genuine vector geometry you can open and edit in Illustrator, Inkscape, or Figma.

The Image to SVG Converter on this site exposes exactly those stages: the color count, a speckle filter (pathomit) that drops tiny regions below a size threshold, and presets that bundle curve-fitting behavior. Everything runs locally in your browser.

Why do logos trace beautifully and photos don't?

File size and fidelity both scale with the number of color transitions, not with pixel dimensions. A flat logo has maybe six colors and large uniform regions: quantization is nearly lossless, boundaries are clean, and the whole thing collapses to a handful of paths — kilobytes that scale to a billboard. A photograph has effectively unlimited colors: quantization snaps every subtle gradient to bands, every boundary is noisy, and the tracer emits thousands of paths trying to follow them. You get poster art and a file bigger than the JPEG you started with.

ArtworkTrace resultVerdict
Flat-color logo (4–8 colors)Few paths, tiny file, perfect scaling✅ Ideal
Icon / pictogramOften cleaner traced at 8 colors than the original✅ Ideal
Diagram / chart screenshotUniform regions collapse nicely✅ Good
Line art, stencil2-color posterize gives clean cut paths✅ Good
PhotographThousands of paths, banded colors, huge file⚠️ Don't
Noisy JPEG of a logoCompression artifacts traced as speckles⚠️ Clean up or raise pathomit

How do the settings change the output?

Color count is the big lever. Measured on a 64×64 test logo (a red disc over a gradient), the default 16-color trace produced 18 paths and 2.7 KB of SVG; a 4-color posterized pass produced 4 paths and 1.0 KB — 62% smaller, with the gradient flattened to bands; a 64-color detailed pass produced 38 paths and 5.8 KB. More colors, more truth, more bytes. pathomit is the speckle filter: any traced boundary with fewer nodes than the threshold is discarded. It's the single best fix for noisy sources — JPEG artifacts, dust on scans, moiré on screenshots. Start at 8; go to 0 only for deliberate detail work.

What's the honest alternative to vectorizing?

How do you clean up a traced SVG?

Open it in Inkscape (free) and expect three chores: delete stray paths (the speckles pathomit didn't catch), merge paths that share a fill, and simplify jumpy curves (Path → Simplify). Recolor by selecting paths and changing fill — useful for rebuilding a brand mark's exact palette. The payoff is a master file: from one traced SVG you can export PNG at any size, print at any resolution, and restyle with CSS on the web. That last property — inline SVG recolorable from your stylesheet — is the quiet reason vectorizing interface icons is so popular.

Vectorize your logo now — privately

Drop a PNG or JPG, pick colors, trace to a real SVG. Runs entirely in your browser.

Trace an Image →

The bottom line

Vectorizing is a lossy re-interpretation that pays off only when the artwork is flat and the goal is infinite scaling or editability. Logos, icons, stencils: trace away, at the lowest color count that still looks right. Photos: don't — upscale or compress instead. And when you do trace, remember the two knobs that matter are colors (fidelity vs. size) and pathomit (noise immunity), in that order.

Advertisement

Frequently Asked Questions

Can you convert any image to SVG?

Technically yes, usefully no. Tracing works by reducing the image to a small palette and fitting curves to the color boundaries, so it shines on flat-color art: logos, icons, stencils, diagrams. Photographs are continuous-tone — tracing one produces thousands of paths, a posterized look, and a file larger than the original. For photos that need to be bigger, upscaling is the right tool, not vectorizing.

How many colors should I use when tracing?

Match the artwork: 2 colors for stencils and pure black-and-white, 4–8 for flat logos, 16 (the common default) for shaded icons, and 32+ only when you want deliberate gradient banding. Every extra color band adds path data — on one 64×64 test, the default 16-color trace produced 18 paths (2.7 KB) while a 64-color detailed trace produced 38 paths (5.8 KB).

Why does my traced SVG look posterized?

Because tracing quantizes: it must choose a finite palette, and every pixel is snapped to the nearest palette color. Smooth gradients become visible bands. That's inherent to the technique, not a bug in the tracer — the fix is either more colors (bigger file) or embracing the poster look. True gradient meshes exist in vector formats but no automatic tracer generates them well from photos.

Is a traced SVG smaller than the original PNG?

Often, for the right artwork. A flat logo traced to 8 colors can shrink dramatically and then scale to any size. But size scales with the number of color transitions, not pixel dimensions — a noisy JPEG or a photo traces to more path data than the pixels were worth. Raise the speckle-filter setting (pathomit) and lower the color count to shrink noisy output.

Related Tools