Image to SVG: the three tracing algorithms, and what a cut-ready file actually needs

Generating an SVG from a reference image is sold as one button. What you get back varies more than the marketing suggests, because "tracing an image" covers at least three different algorithms, and each produces a file that behaves differently in a cutting machine.

If you cut vinyl, HTV or laser stock, the differences are not cosmetic — they decide whether the file weeds in ten minutes or becomes a fight with tweezers.

The three families of image-to-SVG

1. Threshold tracing (black and white). The software picks a luminance cut-off and turns everything above it into a filled path. This is what most free converters do, and it is the right choice for silhouettes, stencils and single-colour decals. It is also the only family that reliably produces a true single-path cut line.

2. Multi-colour posterization. The image is quantised down to N colours, then each colour region becomes its own path on its own layer. This is what you want for layered vinyl — one sheet per colour. The quality lives or dies on two numbers: how many colours the tool commits to, and how it handles the anti-aliased boundary between them. A tool that dumps 40 colours because the source photo had 40 shades has not done the work; 3-6 well-chosen layers are what a craft cutter actually wants.

3. Centerline tracing. Instead of outlining shapes, it follows the middle of each stroke — essential for line art, text and anything you want to draw or score rather than fill. Most free tools skip this entirely, which is why a hand-lettered logo converts into solid blobs instead of strokes.

Check which one your tool runs before you judge the output. A bad result from family 1 is often the right algorithm with the wrong threshold, not a reason to switch tools.

What a cut-ready file actually needs

The SVG spec is generous; cutting software is not. A file that previews fine in a browser can still be unusable in Design Space or Silhouette Studio. The things to check:

• Closed paths. Every shape must be a closed contour. Open paths become unpredictable cuts — some software closes them for you, some cuts down the open edge and back.
• Actual fill, not stroked outlines. A path that is "a 2px black stroke with no fill" looks identical to a filled shape on screen. On a cutter, the stroke usually disappears and the machine has nothing to cut. This is the single most common failure in converted files.
• Groups per colour layer. For layered vinyl, each colour's paths should be grouped, so "send this layer to this mat" is one click rather than a manual sorting session.
• Sane node counts. A trace of a 4000-pixel photo can emit tens of thousands of nodes. Design Space slows to a crawl above a few thousand. Simplification is not cosmetic; it is the difference between a file that loads and one that freezes the app.
• Physical scale. SVGs are unitless until someone assigns a size. Check the file imports at a real-world dimension (width in mm) rather than arriving at 40 kilometres wide or 4 pixels tall.

The honest test before you cut

Load the file into your cutter's software and zoom to 100% at the size you will actually cut. Two failure modes show up only there:

The thin-feature problem. Strokes finer than roughly 1.5-2 mm on 651 vinyl (and a bit more on HTV) become unusable: the weeding tool lifts the whole island, or the material tears. A good preview shows the thinnest stroke in millimetres so you can make this call before cutting, not while weeding.

The island problem. Inside a letter "o" is an island that must be held by a bridge to the surrounding vinyl. Traces that forget bridges produce letters whose counters fall out on the transfer tape. Text-heavy designs need either manual bridges or a font-based rebuild — a trace alone will not save you.

Where AI generation fits, honestly

Text-to-SVG is a different product from image tracing. A generation model produces clean, closed, layer-grouped paths by construction — no threshold artefacts, no anti-aliasing residue — because it is drawing shapes rather than interpreting pixels. The trade is fidelity: it draws what it understands your prompt to mean, not your exact reference. For an original design, that is fine. For reproducing a specific logo, tracing is the right tool and generation is the wrong one.

The combination is more useful than either alone: trace the reference for shape fidelity, then use generation to produce a cleaned variant when the trace is too noisy to weed.

I build AISVG Pro, which does both under one rule: show the honest numbers before you pay. The free preview reports path count, colour layers and the thinnest stroke in millimetres, so you can compare against your material before spending a credit. The trace runs in your browser — free, no account, nothing uploaded — and a credit unlocks the full pack: layered SVG, transparent PNG, DXF for Silhouette and a real-size PDF.

Honest limits: browser tracing is 2D and threshold-based; it will not reconstruct occluded parts of an image or vectorise a 3D render reliably. And generation costs real GPU time per image, which is why it is the paid half while local tracing stays free.