Tracing Gives You a Vector. It Does Not Give You the Vector

How it works

Three deterministic steps and no model of any kind.

The image is enlarged by two with lanczos resampling, which interpolates between the pixels that exist and invents nothing. More pixels give a tracer a smoother boundary to follow, so its curves fit better.

Contrast is raised, which firms up the transition between colors that scaling and compression have softened.

Then the colors are flattened to four with dithering off. Autotracers work by finding boundaries between regions of uniform color, so the fewer and cleaner those regions are, the fewer stray shapes the trace produces.

The output is a PNG. The trace happens in your vector editor, deliberately.

What tracing can and cannot recover

The gap between a traced vector and an original vector is not about quality of output. It is about what kind of object each one is.

Shape is recoverable. A trace can follow a boundary very accurately, and at normal viewing it will be indistinguishable from the original outline.

Construction is not. The designer's circle is an ellipse object with a center and a radius; the trace's circle is a path of hundreds of points that happens to look round. Both render the same. Only one can be scaled, edited, or aligned reliably.

Type is not. Live text carries a typeface, a size, and spacing. Outlines carry none of that, so a traced wordmark is permanently frozen — you cannot fix a kerning problem or change a company name.

Intent is not. Was that corner meant to be a two millimeter radius or a three? The trace records what the pixels showed after the JPEG got hold of them, which is neither.

So the honest description of any trace, however clean: a vector that resembles the image, not the vector the image came from.

Clean input decides everything

The reason this page is a cleanup rather than a tracer is that autotracers are mostly limited by what they are given.

A soft edge produces a boundary the tracer has to guess at, and it guesses differently along the length of the same edge, which is where wobble comes from. Compression artifacts create small color regions that become their own tiny shapes. Anti-aliasing creates a one-pixel intermediate color that, if it is not merged into a neighbor, becomes a hairline path shadowing every outline in the file.

Flattening to a few colors with no dithering deals with all three at once, and it is why the same tracer produces a clean file from one input and a mess from another that looked similar.

The exception is gradients, which flattening actively harms. A mark with a smooth blend becomes a set of bands, and tracing bands gives you stacked shapes rather than one object with a fill. For those, tracing is the wrong approach entirely and a redraw is the only sensible route.

After the trace

Two steps that people skip, both of which take minutes and determine whether the file is usable for years.

Reduce the nodes. Vector editors have a simplify function, and using it until the shape starts to distort, then stepping back once, typically removes most of the points without visible change. Curves made of few points are also curves that can be adjusted.

Rebuild the primitives. If a shape is meant to be a circle, delete the traced approximation and draw an actual circle over it. If two strokes are meant to be the same weight, set them to be. That is the difference between a file that looks right today and one that behaves correctly the next time somebody opens it.

Publication gate

This page ships once the workflow has been run against a flat two-color mark, a mark with anti-aliased edges from a screenshot, a mark containing a gradient, and a mark containing small text, with each output traced in a vector editor and the resulting node counts and curve fidelity recorded.