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) yield the smallest SVG but lose fine detail; the recommended 4-6 range balances size and fidelity; 7-10 preserves subtle edges at the cost of a larger file.
3. Confirm SVG Output: SVG is preselected as the target. The converter embeds the rasterized TIFF inside an SVG container so the image remains pixel-accurate while gaining the scalable, web-friendly SVG wrapper.
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 acquiring 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 color. 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 level and is natively understood by every modern browser (Chrome, Firefox, Safari, Edge).

Wrapping a TIFF inside an SVG gives you a single file that drops cleanly into modern web, design, and CMS pipelines:

• Embed scans into websites and CMSs — many CMS uploaders (WordPress, Shopify, Webflow) reject .tif/.tiff by default but accept .svg. Converting lets you publish archival scans without a transcoding step.
• Edit in vector tools without losing the raster — Inkscape, Illustrator, Figma, and Affinity Designer open SVGs directly and let you add vector overlays (annotations, arrows, callouts) on top of the embedded TIFF layer.
• Share large scans without DPI guesswork — recipients zoom in their browser instead of needing a TIFF viewer like IrfanView, Preview, or Photoshop. The SVG renders identically on Retina, 4K, and 8K displays.
• Prepare assets for laser cutting, CNC, or plotters — many fabrication tools (Glowforge, Cricut Design Space, LightBurn) require SVG input but accept embedded raster layers for tracing or alignment.
• Reduce delivery friction for archival material — museums, libraries, and scientific journals that store master images as TIFF can hand out SVG copies that open in a browser tab, eliminating "what do I open this with?" support emails.
• Future-proof legacy scans — every browser since at least 2011 ships an SVG renderer; the same cannot be said for proprietary TIFF tag extensions (e.g., GeoTIFF, JPEG-in-TIFF, BigTIFF variants).

TIFF vs SVG — Format Comparison

Embedding vs Vectorizing — Which Approach Does This Tool Use?

There are two ways to turn a TIFF into an SVG. Pick the one that matches your goal.

If you need true vectorization with editable paths, run the output through Inkscape's Trace Bitmap (Shift+Alt+B) or Illustrator's Image Trace panel after this conversion, or upload a flattened version to a dedicated tracer like Vectorizer.AI.

Frequently Asked Questions

Does this tool actually trace my TIFF into editable vector paths?

No. This converter embeds the rasterized TIFF inside an SVG wrapper so the image stays bit-accurate. That works well for photographs and complex scans, where automatic tracing usually produces a worse result than the original. If you need editable paths (one shape per color region), use Inkscape's Trace Bitmap dialog or Adobe Illustrator's Image Trace — both are free or industry-standard tools designed specifically for that job.

Why is my SVG file roughly the same size as the TIFF?

Because the raster payload is preserved inside the SVG. An embedded TIFF still occupies the same number of bytes; the SVG wrapper only adds a small XML header and <image> element. If you need a smaller file, flatten the source TIFF to JPEG or WebP first, or run the SVG through svgo --multipass to compress the markup. True file-size reduction comes from vectorizing simple line art, not from embedding photos.

What does the "Number precision" slider actually change?

It controls how many digits of coordinate data are stored in the SVG markup — for example, 12.3 (precision 3) versus 12.345678 (precision 6+). Higher precision keeps fine alignment details but inflates the XML; lower precision shaves bytes at the cost of subtle pixel jitter. For most TIFF embeds the default of 6 is fine; drop to 3-4 if size matters and the image will only ever be viewed at 100%.

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

No — SVG has no native multi-page concept. The conversion takes the first page of a multi-page .tif (common in fax archives and scanned PDFs). If you need every page, split the TIFF into separate files first (ImageMagick convert input.tif page-%d.tif), then upload them together for batch conversion. For multi-page workflows, TIF to PDF is usually a better fit.

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

No. Browsers render SVG in 8-bit sRGB, and there is no widely-supported way to express 16-bit-per-channel or CMYK color inside SVG markup. If your TIFF is a 16-bit scientific scan or a CMYK print master, the embedded image is downsampled to 8-bit RGB on conversion. Keep the original TIFF for archival use and treat the SVG as a web-friendly derivative.

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

WordPress, Shopify, Webflow, and most modern CMS platforms ship with TIFF disabled in the upload allowlist because browsers (except Safari) cannot render TIFF without a plugin. SVG, by contrast, is on the default allowlist almost everywhere because every major browser has had inline SVG rendering since around 2011. Wrapping the TIFF in SVG is a common workaround for getting archival scans onto the web without changing the CMS configuration.

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

Yes — because SVG is XML, it can in theory contain <script> tags and event handlers (onclick, onload, etc.) that browsers will execute when the SVG is loaded inline. This converter produces a plain <svg><image.../></svg> with no scripts, but if you upload the SVG to a public site, configure your CMS to serve user-uploaded SVGs with Content-Disposition: attachment or sanitize them with a library like DOMPurify so a malicious user cannot inject scripts later.

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

Yes. The output uses standard SVG 1.1 markup with a base64-encoded raster payload, which all three open without complaint. In Inkscape and Illustrator you can layer vector annotations on top of the embedded image. Figma will treat the embedded raster as a single image element. For the reverse direction, SVG to TIF flattens the vector back to a raster for print or archival use.

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

PNG keeps lossless quality and is universally supported — try TIF to PNG. JPG is best for photographs where smaller file size matters more than perfect fidelity. SVG is the right answer only when you specifically need a file that scales (vector tools, CMS allowlists, or a single asset that needs to slot into a vector-only pipeline like Glowforge or Cricut).