The Best Image Formats for SVG Conversion, Ranked

Vectorization quality depends on the source as much as the tracer. The same logo saved six ways will produce six different SVGs – some flawless, some speckled with artifacts. Here’s every common format ranked as a tracing source, and how to get the best result from whichever one you’re stuck with.

The ranking, short version

1. PNG – the gold standard
2. BMP – surprisingly excellent
3. GIF – great for what it holds
4. Lossless WebP – PNG-equivalent
5. Lossy WebP / AVIF – good, mild artifacts
6. JPG/JPEG – workable with the right settings
7. TIFF / HEIC – fine content, needs a conversion step first
8. PDF – special case: may already contain vectors

Why PNG wins

Tracing infers shapes from regions of flat color and the edges between them. PNG is lossless – every edge is exactly as sharp as the original export – and supports transparency, which acts as a free, perfect mask telling the tracer where the artwork ends. A transparent-background PNG of a flat-color logo is the single best input vectorization can receive. (Try one.)

BMP and GIF: the legacy surprises

BMP stores raw uncompressed pixels – zero compression artifacts, ever. Old bitmap files trace beautifully; their only sin is file size, which stops mattering the moment they become 20 KB SVGs.

GIF is limited to 256 colors with no lossy smearing – meaning hard edges and flat regions, which is precisely what tracers love. Old GIF-era logos and clipart convert nearly 1:1. Animated GIFs trace from their first frame.

JPG: the format that fights back

JPG compresses by discarding detail in 8×8 pixel blocks – invisible in photos, but around a logo’s sharp edges it leaves “mosquito noise”: faint ringing the tracer happily converts into hundreds of tiny phantom shapes.

The countermeasures, in order of power:

• B&W mode – thresholding to two colors annihilates low-level noise completely. Best for scans, signatures, single-color marks.
• Lower detail settings – loosens curve-fitting tolerance so noise gets smoothed over rather than traced.
• Higher-quality sources – a JPG saved at quality 90+ has far less ringing than a meme-grade quality 60 file.

Full workflow: JPG to SVG.

WebP and AVIF: the modern middle

Lossless WebP behaves exactly like PNG. Lossy WebP and AVIF behave like high-quality JPG – much cleaner artifacts, same countermeasures when needed. The real reason these formats appear in tracing workflows: they’re what you get when you save images from modern websites. Browsers decode both natively, so WebP and AVIF trace in one step.

TIFF and HEIC: a detour, not a dead end

Browsers can’t decode TIFF (and only Safari decodes HEIC), so browser-based tracers can’t read them directly. The detour is lossless: export to PNG first – Windows Photos, macOS Preview, or any editor does it – then trace. The pixels that reach the tracer are identical to the originals. Step-by-step: TIFF to SVG · HEIC to SVG.

PDF: check before you trace

A PDF made by a designer may already contain true vector graphics – in which case tracing is the wrong move entirely. Extract the vectors losslessly with Inkscape instead, and only fall back to tracing for scanned PDFs. The decision guide: PDF to SVG.

Beyond format: the three source qualities that matter more

Format is half the story. Whatever you’re feeding the tracer:

1. Resolution – 800–1400px on the long edge is the sweet spot. Below 300px, shapes get ambiguous.
2. Edge sharpness – original exports beat screenshots beat photos-of-screens.
3. Flat color – gradients posterize in any format; flat-color versions of artwork always convert better.

The universal converter at image to SVG accepts all the browser-decodable formats above – pick your best available source, apply the right mode, and the format ranking takes care of the rest.