The trace is only as good as its edges.

Wobbly outlines almost always mean the source had wobbly edges you could not see.

A tracer follows edges exactly — including the ones compression invented

JPEG discards detail in 8×8 blocks, and around any hard boundary it leaves faint rings and speckles. At 100% zoom you will never notice them. An edge detector notices nothing else: it follows those artefacts as faithfully as it follows your artwork, which is why a JPEG logo comes back with rippled outlines and stray fragments floating near the edges that a PNG of the same design would not produce. Low resolution compounds it — at 200px a curve is a staircase of pixels, and the tracer returns the staircase, correctly. The tracer is not guessing badly; it is reading precisely what is there.

How to confirm it

Zoom the source to 400%
Look at any hard edge. Rings, halos or speckles mean JPEG artefacts.
Check the pixel dimensions
Under ~512px on the short edge, the trace inherits visible stair-stepping.
Look for stray fragments
Tiny disconnected shapes near edges are compression noise, not artwork.
Try a different source
If a PNG of the same artwork traces cleanly, compression was the cause.
Rule out the wrong fix
Upscaling AFTER tracing does nothing — the paths are already wrong.

The fix

1
Find a better source

Any other copy — a PNG, the original design file, a larger export — beats re-tracing the JPEG.

2
If JPEG is all you have, upscale first

Scale the raster up before tracing. Artefacts stay the same physical size while the shapes grow past them.

3
Re-trace and check the path count

Clean flat art returns tens to a couple of hundred paths. Thousands means it is still tracing noise.

Image → SVG · free, no signup

Fix it here.

Upload the original image. The preview shows the real path count before you pay.

3 free previews left · no signup to try

FAQ

Would a different tracer fix it?

Not meaningfully. Every tracer follows boundaries, and the boundaries in a compressed low-resolution image are genuinely ragged. Some smooth more aggressively, which trades wobble for softness and loses real detail along with the noise. Improving the source beats changing the tool every time.

Why does upscaling before tracing help but not after?

Before tracing, the artefacts stay the same absolute size while the shapes get larger, so they matter proportionally less to the edge detector. After tracing, the paths already encode the wobble — scaling just makes the wobble bigger.

Is a screenshot ever good enough?

Occasionally, for flat high-contrast artwork captured at high zoom on a high-DPI screen. Usually not: a screenshot is a re-render of something that already existed, often scaled, often compressed, and usually with a background baked in.

What if the original is a photograph?

Then tracing is the wrong tool rather than a poorly-performing one. Photographs have gradients rather than edges, so any trace returns a poster-like reduction. That can be a great result deliberately and is never a faithful reproduction.

Related problems