TIFF to SVG Converter

How to Convert TIFF to SVG Online

1. Upload Your TIFF File: Drag and drop the .tiff or .tif file, or click "+ Add Files" to browse. Multi-page TIFFs and batch uploads are supported — each frame is processed independently.
2. Set Number Precision: Open Advanced Options and adjust the precision slider (1-10). The default is 6, which fits most logos and line art. Lower values (3-4) shrink file size aggressively but round off curve control points; higher values (7-10) preserve detail at the cost of larger output.
3. Review the Conversion Approach: xconvert embeds the TIFF raster inside the SVG container rather than vectorizing it. The output is a true SVG file that any browser, Illustrator, Inkscape, or Figma can open, and the precision setting controls how coordinates are written when the wrapper is generated.
4. Convert and Download: Click "Convert". Files process server-side with no watermark, no account, and no email required.

Why Convert TIFF to SVG?

TIFF (Tag Image File Format) was published by Aldus in autumn 1986 for desktop scanners and prepress; Adobe took over the spec when it acquired Aldus in 1994 and the current revision is 6.0. SVG (Scalable Vector Graphics) became a W3C Recommendation on 4 September 2001 and is now the only vector format that renders natively in every major browser. Wrapping a TIFF in SVG gives you a file you can drop into any HTML page, scale by CSS without resampling, and version-control as plain text.

• Embed scans in HTML or React — SVG is XML, so it inlines directly into JSX, Vue templates, or <svg> tags in plain HTML. No <img> round-trip, no CORS surprises.
• Replace TIFF on the web — most browsers (Chrome, Firefox, Edge, Safari) do not render TIFF inline. Converting to SVG makes the image immediately viewable without a plugin or server-side transcode.
• Preserve multi-page archive scans — bank statements, blueprints, and medical scans archived as multi-page TIFF can be split into per-page SVGs that load lazily in a viewer.
• CSS-styled wrappers — once the raster is inside an SVG, you can layer text, masks, filters (drop-shadow, blur), and CSS animations on top without re-exporting from Photoshop.
• Print-ready handoff — SVG embeds cleanly in Illustrator and InDesign; designers can crop, mask, or trace the embedded TIFF without losing the original pixel data.
• Smaller for line art — for logos, signatures, and high-contrast diagrams, a vectorized SVG (run through Illustrator's Image Trace or Inkscape's Trace Bitmap on the output) can be 60-90% smaller than the source TIFF.

TIFF vs SVG — Format Comparison

Embed vs Vectorize — Which Path Fits Your TIFF?

Number Precision Quick Guide

Frequently Asked Questions

Does this tool actually trace my TIFF into vector paths?

No. xconvert wraps the TIFF inside an SVG container (using SVG's <image> element), so the output is a valid .svg file but the picture data remains raster. True vectorization — running a tracer like Potrace or VTracer — is a separate step. If you want vector paths, open the converted SVG in Inkscape and use Path > Trace Bitmap, or in Illustrator use Image Trace. Wrapping is fast and lossless; tracing is slow and lossy but produces infinitely scalable output.

Will my SVG be smaller than the TIFF?

Usually yes, because TIFFs are typically stored uncompressed or with LZW, while the embedded raster inside the SVG is base64-encoded PNG which is deflate-compressed. Expect a 40-70% reduction for color photos. For files already saved as TIFF with JPEG compression, the SVG may be slightly larger because of base64 overhead (roughly 33%).

Why doesn't my SVG look any sharper when I zoom in?

Because the underlying pixels are still raster. Wrapping a 1000-pixel-wide TIFF in SVG and rendering it at 4000 px will look just as blurry as scaling the original TIFF. Sharpness at arbitrary zoom only comes from real vector paths, which means running a trace step after this conversion.

Can I edit the result in Illustrator or Inkscape?

Yes. Both Illustrator and Inkscape open SVG natively and will show the embedded TIFF as a single linked-or-embedded image object. You can mask it, clip it, place it under text, or — in Inkscape — run Trace Bitmap on it to generate editable paths.

What's the maximum precision and what does it mean?

The slider goes 1-10. It controls the number of decimal places written for any coordinates in the SVG (transformations, viewBox, embedded-image positioning). Higher precision means longer numbers in the XML and a slightly larger file. The default of 6 matches the SVG spec recommendation for general-purpose rendering and is well below the threshold where the difference would ever be visible.

Does this handle multi-page TIFFs?

Multi-page TIFFs are processed page by page; SVG itself has no multi-page concept, so you receive one SVG per frame. If your goal is to keep a multi-page document together, convert to PDF instead — PDF preserves page order and can embed multiple TIFF frames in a single output.

What about CMYK or 16-bit TIFFs from print workflows?

The encoder converts non-RGB color spaces to sRGB during the embed step (browsers render SVG in sRGB by default), and 16-bit-per-channel TIFFs are reduced to 8-bit. If you need to preserve full color fidelity for press, keep the TIFF and use TIFF to PDF with a print-ready profile instead.

Why not just use PNG or JPG for the web?

For pure web display, TIFF to PNG or TIFF to JPG is usually the simpler path. Pick SVG when you specifically need: (a) the ability to inline the image in HTML/JSX as XML, (b) CSS-controlled masks or filters layered on top, (c) a single container you can later vectorize, or (d) a path to embed the image inside a larger composed SVG (charts, infographics, icon sheets).

Can I reverse this and go back to TIFF?

Yes — SVG to TIFF rasterizes the SVG (paths and any embedded images) at a chosen resolution and writes a TIFF. The round trip is lossy if you've added vector elements on top of the embedded raster, since those get flattened back into pixels.