TIFF to SVG Converter

How to Convert TIFF to SVG Online

1. Upload Your TIFF File: Drag and drop, or click "+ Add Files" to pick one or more .tif / .tiff images. Batch uploads are supported, and each file is processed in a private session.
2. Set Number Precision: Open Advanced Options and drag the Number precision slider (1-10, default 6). Lower values (1-3) merge similar colours and smooth curves for the smallest SVG; the recommended 4-6 range balances size and fidelity; 7-8 keeps subtler edges at the cost of a larger file.
3. Keep the Slider At or Below 8: Positions 9 and 10 abort the conversion and produce no file at all. The single slider value is sent to the tracer as both the path precision and the colour precision, and colour precision is only defined for 1 to 8 significant bits per RGB channel — so the job stops with an out-of-range error rather than tracing more finely. Eight is the real maximum.
4. Convert and Download: Click "Convert", then download the .svg for each file. Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically after a few hours — no sign-up, no watermark, never shared.

Why Convert TIFF to SVG?

TIFF (Tagged Image File Format) was introduced by Aldus in 1986 and has been maintained by Adobe since it acquired Aldus in 1994. It is the de facto archival format for high-resolution scans, medical imaging, and prepress workflows because it supports lossless compression, multi-page documents, layers, and 16-bit-per-channel colour. SVG (Scalable Vector Graphics), a W3C Recommendation since SVG 1.0 was published on 4 September 2001 (SVG 1.1 followed on 14 January 2003), is an XML-based format that renders crisply at any zoom and is natively understood by every modern browser.

The two are not interchangeable, and this converter does not pretend otherwise: it traces. Your pixels are analysed, grouped into colour regions, and redrawn as real <path> elements. The output is genuine vector geometry — not the TIFF re-wrapped in an SVG container, and not a base64 payload inside an <image> tag. What that buys you, and what it costs you, is covered in the next section. Where it pays off:

• Editable artwork in vector tools — Inkscape, Illustrator, Figma, and Affinity Designer open the result as individual shapes you can recolour, reshape, or delete, rather than a flat picture you can only crop and mask.
• Publish scans through CMS uploaders — WordPress, Shopify, and Webflow reject .tif/.tiff by default but accept .svg, so a traced logo or letterhead publishes without a transcoding step.
• Fabrication workflows — Glowforge, Cricut Design Space, and LightBurn follow path geometry. A trace gives them the closed outlines they need; an embedded raster would give them nothing to cut.
• Resolution-free delivery — a traced mark renders identically on a phone, a Retina display, and a projected 8K screen, with no DPI decision to get wrong.
• Genuinely smaller files for line art — a two-colour logo that occupies megabytes as a 600 DPI scan is typically a few kilobytes once it is described as shapes.
• Future-proofing — every browser has shipped an SVG renderer for well over a decade; the same cannot be said for proprietary TIFF tag extensions such as GeoTIFF, JPEG-in-TIFF, or BigTIFF variants.

What Tracing Does Well — and Where It Falls Apart

A trace approximates your image with paths, so the quality of the result depends almost entirely on what the picture contains. Flat artwork with clear boundaries — logos, signatures, stencils, schematics, high-contrast stamps — traces beautifully, because those boundaries are exactly what the algorithm is looking for. Continuous tone does not: a photographic scan has no clean edges, so the tracer either collapses it into a handful of lumpy colour blobs or emits tens of thousands of micro-paths, producing an enormous SVG that is slow to open and looks worse than the TIFF you started from. If your source is a photograph, keep it raster with TIFF to PNG or TIFF to JPG.

TIFF is also not one of the tracer's native input formats — those are PNG, JPG/JPEG, JFIF, BMP, GIF and WebP — so a TIFF has to be rendered to a standard raster before any trace can begin. Doing that step yourself is worth considering as a quality decision rather than a chore: rendering the scan lets you set the crop, the levels, and the output size, and those choices influence trace quality far more than the precision slider does. Render with TIFF to PNG, push the contrast until your subject separates cleanly from the paper, then trace the result with PNG to SVG.

TIFF vs SVG — Format Comparison

Frequently Asked Questions

Does this tool trace my TIFF into editable vector paths?

Yes. The converter runs a raster-to-vector trace and writes real <path> elements — it does not wrap the scan in an SVG <image> element, and there is no base64 raster hiding inside the output. Every traced colour region arrives in Inkscape or Illustrator as an object you can select and edit. The trade-off is approximation: what you get is the tracer's geometric reading of your pixels, which is superb for flat artwork and unusable for photographs.

Why is my traced SVG bigger than the TIFF?

Because the source was continuous-tone. Every tonal step becomes its own filled path, and a photographic scan contains an enormous number of them, so the XML describing them all can outweigh the compressed raster it came from. Drop the precision toward 3-4 and re-run to see whether a simplified version is usable; if it isn't, that image genuinely wants a raster format rather than a different setting.

What does the "Number precision" slider actually change?

It drives two tracer parameters from a single value: how finely colours are separated when pixels are clustered into regions, and how many decimal places each path coordinate keeps. Lowering it therefore merges similar colours and smooths curves in the same move, which is why its effect is so visible. The default of 6 suits most work; 4-6 is the recommended band; 3-4 is worth trying when you want the simplest possible shapes.

Why do positions 9 and 10 fail?

The slider's range is wider than the tracer's. Because the same value is sent as the colour precision, and colour precision is defined only for 1 to 8 significant bits per RGB channel, asking for 9 or 10 is outside what an 8-bit channel can express. The tracer rejects it rather than clamping it, and the run ends with an out-of-range error and nothing to download. Keep the slider at 8 or lower; there is no detail hiding above 8 to miss out on.

Will my multi-page TIFF become a multi-page SVG?

No — SVG has no multi-page concept, so there is no format-level way to return every page in one .svg. If one particular page is what you need, split the TIFF first (ImageMagick's convert input.tif page-%d.tif does it in a single command) and upload that page on its own. For workflows that must keep the pages together, TIFF to PDF is the better target.

Does converting to SVG preserve TIFF's 16-bit colour and CMYK data?

No, and the trace reduces it much further than a format change would. The image is brought to 8-bit sRGB before tracing, and the trace itself replaces the tonal range with a small set of flat region fills. Neither wide-gamut data nor smooth gradients survive in any form. Keep the original TIFF for archival and press use, and treat the SVG as a shapes-only derivative.

Why won't my CMS accept the original .tif but it accepts the .svg?

WordPress, Shopify, Webflow, and most modern platforms ship with TIFF disabled in the upload allowlist because browsers other than Safari cannot render it without a plugin. SVG is on the default allowlist almost everywhere. For a logo or a letterhead mark, tracing to SVG is the cleanest way onto the site; for a photographic scan, TIFF to PNG is the honest answer rather than forcing a trace.

Are there security concerns with SVG that don't apply to TIFF?

Yes — because SVG is XML, it can in principle contain <script> tags and event handlers that a browser will execute when the file is loaded inline. This converter emits plain path geometry with no scripts, but if you accept SVG uploads on a public site, serve user-supplied SVGs with Content-Disposition: attachment or sanitize them with a library such as DOMPurify so nobody can inject scripts later.

Can I open the converted SVG in Illustrator, Inkscape, and Figma?

Yes. The output is standard SVG 1.1 path markup, which all three open without complaint and treat as normal editable objects — not as a single locked image. Cleaning up a traced scan in Inkscape usually means deleting a few speckle paths picked up from scanner noise and merging any regions the tracer split. For the reverse direction, SVG to TIFF rasterizes the vector back to pixels for print or archival use.

What if I just want the TIFF as a PNG or JPG for the web instead?

That is often the right call. PNG keeps lossless quality and is universally supported — try TIFF to PNG. JPG suits photographs where file size matters more than perfect fidelity: TIFF to JPG. Choose SVG only when you specifically need the artwork as shapes — editable paths, cutter-ready geometry, or markup you can inline and restyle with CSS.