SVG to TIFF, rasterized and private. Nothing ever uploads.

Drop SVG logos, icons and illustrations below — get a TIFF per file rasterized at the DPI you choose, in batches of up to 20. Converted entirely on your device.

Your file data never leaves the device
DPI 72–600 · LZW / PackBits / uncompressed
Batch up to 20 files + ZIP
Multi-page TIFF combine · scripts stripped

Add your SVG files

Drag & drop SVG files here

or browse your files · you can also paste from clipboard (Ctrl+V)

Your browser rasterizes SVG natively — no decoder download, no waiting. Scripts and external references are stripped or refused before anything renders.

No files yet. Everything stays on this device. Downloads start instantly.

TIFF settings

Output

One TIFF per file Each SVG becomes its own TIFF. Combine into one multi-page TIFF All SVGs become pages of a single TIFF, in list order.

Compression

LZW — lossless Best compression, the print standard. Default. PackBits — lossless Simple RLE for very old software that cannot read LZW. None — uncompressed Every pixel stored raw. Largest files.

Lossless: the rasterized pixels are preserved exactly, whatever you pick.

DPI — render size and tag

72 DPIScreen use, own size. 150 DPIDrafts, large prints. 300 DPIThe print standard. 600 DPIHigh-resolution print.

DPI does two jobs here: it sets the render size (DPI ÷ 72 × your SVG's own size — 300 DPI renders a 400×200 logo at 1667×833 px) and it is written as the TIFF X/YResolution tag. The tag tells print shops how large the image prints; DPI never invents detail.

Background colour

#ffffff

Transparency is flattened onto this colour — TIFF has no alpha channel. White is right for print; match the destination background to avoid a halo.

DPI sets the render size and the tag. 72 DPI renders at the SVG's own size; 300 DPI renders about 4× larger and writes 300 as the resolution tag.
Much larger than the SVG. A 400×200 logo at 300 DPI is 1667×833 px, about 4 MB uncompressed — LZW shrinks flat vector art to a fraction of that. Every file shows its size multiple honestly.
Transparency is flattened. Any see-through pixels are composited onto the background colour you pick, because TIFF here is 8-bit RGB with no alpha channel.
Scripts, animations and external references are stripped or refused. SVGs are checked before anything renders — nothing may be fetched while converting.
Fonts are not embedded. Text renders with your browser's system fonts, so a logo that relies on an unusual font may look different. The TIFF is rasterized, not vector — no text layer, no OCR.
Animated SVG renders as its first frame only. SMIL animation is stripped before rasterizing; a TIFF is a still image.
Settings apply when files convert. Choose before adding files, or press Convert again after changing them.
25 MB per file, 20 per batch. No daily limit and no account — most SVGs are well under 1 MB.

Need a vector PDF instead? Convert SVG to PDF — same privacy, keeps the vector.

Privacy you can verify, not just trust

Most online SVG converters upload your logos to their servers first — and some keep a download link live for hours afterwards. This one can't: your browser rasterizes the SVG and the TIFF encoder runs entirely in your browser. Your file data never leaves the device — the only third-party requests are the site's own analytics, which count page views — and it uploads nothing, ever. There is no decoder to download and no file fetched after load for the conversion itself. Don't take our word for it:

New cross-origin requests during use: 0

Press F12 to open developer tools, then the Network tab.
Convert any SVG above. Watch: apart from the site's analytics, nothing new is requested — no uploads, and no file data ever leaves your device.
Extra credit: disconnect your internet after this page loads — conversion still works.

How to convert SVG to TIFF without uploading it

Every "free" online SVG converter you've used uploads your logos to a company server, converts them there, and — in several documented cases — keeps a copy or a live download link for hours. For client work, brand assets and anything you wouldn't post publicly, that's an unnecessary risk. The safer approach is to convert the file where it already is: on your own device.

This tool does exactly that. When you drop an SVG here, your browser:

Sanitizes the SVG first — scripts, embedded HTML, SMIL animation elements and event-handler attributes are stripped, and any file that references an external resource is refused outright, so nothing is fetched while converting.
Rasterizes it at your DPI — the SVG is rendered at DPI ÷ 72 relative to its own size (300 DPI renders a 400×200 logo at 1667×833 px), with transparency flattened onto the background colour you chose. Animated SVGs render as their first frame only, and fonts are not embedded — text uses your browser's system fonts.
Re-encodes the pixels as a TIFF with a pure-JavaScript TIFF encoder — little-endian header, one IFD per image, LZW, PackBits or no compression, and the DPI you chose written as XResolution and YResolution tags. Your original file is never modified.

What makes this converter different

The converters that top the results for this search mostly upload your files to a server (Wondershare UniConverter and AnyConv convert server-side, and Zamzar caps free conversions at 2 MB), and the client-side ones we found are thin — mapree.dev is a dedicated client-side SVG-to-TIFF page with batch support, but offers no stated DPI choice, no compression choice and no multi-page combine, and picflow's client-side batch tool is thinner still. This page is the only dedicated SVG-to-TIFF page we found that combines a batch of 20 files with a ZIP download, a genuine DPI choice that sets both the render size and the TIFF tag, a compression choice (LZW by default, PackBits or uncompressed), a multi-page TIFF combine mode, SVG-specific safety (scripts stripped, external resources refused), and a live network-request counter so you can verify the privacy claim yourself. It runs entirely in your browser — there is no server to upload to, no daily limits, no account and no watermark.

When is TIFF the right choice for an SVG?

When the destination demands it: print shops and scanning bureaus that ask for TIFF, archives that store images losslessly, and layout software (InDesign, QuarkXPress and their peers) that places TIFFs at a stated DPI. TIFF is also the format for multi-page sets — one file, one page per image. For anything else — web, sharing, storage — keep the SVG, or use SVG to PNG instead and keep the smaller file.

Files are checked by their contents, not their name: an SVG saved as .txt still converts, because the <svg> root element is what matters, while a PNG renamed to .svg is refused with a pointer to the matching converter. A corrupt or truncated SVG is refused at rasterize time, with a per-file error explaining what happened.

Honest limitations

Rasterized, not vector

The TIFF holds pixels, not the vector drawing. There is no text layer and no OCR — text in the TIFF is not searchable or selectable, and the image cannot be scaled up cleanly the way the SVG could. Metadata is dropped on re-encode.

Fonts are not embedded

Text renders with your browser's system fonts, because the SVG is rasterized where it runs. A logo that relies on an unusual font may look different from the original — check the preview before downloading.

Animated SVG renders as its first frame

SMIL animation is stripped before rasterizing, so an animated SVG becomes a still image of its opening frame. If you need the animation, keep the SVG or convert it with our SVG to GIF converter.

Transparency is flattened

Output is 8-bit RGB — no 16-bit, no CMYK, no alpha channel. Any see-through pixels are composited onto the background colour you pick, so choose one that matches where the image will sit.

TIFFs are much larger than SVGs

An SVG is a few kilobytes of drawing instructions; a 1667×833 TIFF is about 4 MB uncompressed, less with LZW. Every file shows its size multiple honestly, and the batch bar shows the total before you download anything.

Multi-page TIFFs are not universal

Multi-page TIFFs open in most viewers, but some old software shows only the first page. If the destination is old or unknown, send one TIFF per file instead.

Frequently asked questions

Do my SVG files get uploaded anywhere?

No. Your browser rasterizes the SVG and the TIFF encoder runs entirely in your browser, so your file data never leaves the device. The only third-party requests are the site's own analytics, which count page views. You can verify it in your browser's Network tab, or disconnect from the internet after the page loads — conversion still works.

Which DPI should I choose — and what does DPI actually do here?

DPI does two jobs here: it sets the render size and it is written as the TIFF X/YResolution tag. The SVG is rendered at DPI divided by 72 relative to its own size, so a 400x200 logo at 300 DPI becomes a 1667x833 pixel TIFF, and the same 300 is stored as the resolution tag. 72 DPI is for screen use at the SVG's own size, 150 DPI is fine for drafts and large prints, 300 DPI is the print standard, and 600 DPI is for high-resolution print work. DPI never invents detail — it only decides how many pixels the vector is rasterized into.

Should I choose LZW, PackBits or no compression?

LZW is the default and the right choice for almost everything: it is lossless, it shrinks flat vector art dramatically, and it is the prepress standard every print shop and layout program reads. PackBits is a simpler lossless RLE format for very old software that does not understand LZW. Uncompressed stores every pixel as 3 bytes with no compression at all — the largest files, useful only when the destination cannot decode either compression.

What is a multi-page TIFF and when should I combine files?

A multi-page TIFF is one file holding several images, one per page — the format scanners and archives use for a document of many pages. Choose the combine mode when the SVGs belong together as one document, for example the pages of a set of illustrations, and keep one TIFF per file when each logo or icon is separate. Multi-page TIFFs open in most viewers, but some old software shows only the first page.

What happens to animated SVGs?

A TIFF is a still frame, so an animated SVG renders as its first frame only. The SMIL animation elements are stripped before rasterizing — they change nothing visually in a still image, and an animated attribute could otherwise rewrite references at runtime. If you need the animation itself, keep the SVG or convert it with our SVG to GIF converter instead.

What happens to transparency in my SVG?

TIFF as written here has no alpha channel, so any transparency is flattened onto the background colour you choose — white by default. Pick the colour the image will sit on: white for print, or match the destination background so edges do not show a halo. The file card tells you when a file had transparency flattened.

Why is the TIFF so much bigger than the SVG?

An SVG is a set of drawing instructions, often only a few kilobytes, while a TIFF stores every rasterized pixel losslessly — even LZW only compresses them, it never throws detail away. A 400x200 logo rendered at 300 DPI is 1667x833 pixels, about 4 MB as an uncompressed TIFF. LZW shrinks flat vector art to a small fraction of that, so the gap is much smaller than for a photo. This tool shows the original and TIFF size for every file, with the size multiple, so the trade-off is never hidden.