WebP to TIFF, lossless and private. Nothing ever uploads.

Drop WebP images below — get a TIFF per file with LZW compression and print-ready DPI tags, in batches of up to 20. Converted entirely on your device.

Your file data never leaves the device
LZW / Deflate / PackBits / uncompressed
Batch up to 20 files + ZIP
Multi-page TIFF combine + DPI tags to 600

Privacy you can verify, not just trust

Most online WebP converters upload your images to their servers first — and some keep a download link live for hours afterwards. This one can't: your browser decodes WebP natively 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 WebP 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 WebP to TIFF without uploading it

Every "free" online WebP converter you've used uploads your images to a company server, converts them there, and — in several documented cases — keeps a copy or a live download link for hours. For personal photos, client work 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 a WebP here, your browser:

Decodes the WebP natively — every modern browser includes a WebP decoder, so there is no decoder file to download and no waiting for a library to load. Lossy and lossless WebP both decode the same way; only the first frame of an animated WebP is decoded.
Flattens any transparency onto a white background, because the TIFF written here stores 8-bit RGB with no alpha channel. The file card warns you when this happens.
Re-encodes the pixels as a TIFF with a pure-JavaScript TIFF encoder — little-endian header, one IFD per image, LZW, Deflate, 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 (Convertio, CloudConvert and XConvert all convert server-side — XConvert does offer a compression choice, but only after your files upload), and the client-side ones we found are thin — tools.mapree.dev and filevolve convert locally in a batch but offer no compression choice, no DPI tags and no multi-page mode, convert.browzy.dev is client-side but offers none of those either, toolsforanyone.com converts in a batch with a ZIP download but no compression choice, no DPI tags and no multi-page mode, quickimagetool.in batches with a ZIP but its TIFF output is always uncompressed with no compression choice, no DPI and no multi-page mode, imageconvertit caps its free tier at 3 trial files and charges for batches of 50, PureConverter runs ImageMagick in WebAssembly with no stated compression choice, DPI tags or multi-page mode, and imagexpo.com states none of those either. This page is the only fully client-side dedicated WebP-to-TIFF page we found that combines a batch of 20 files with a ZIP download, a genuine compression choice (LZW by default, Deflate, PackBits or uncompressed), DPI tags from 72 to 600, a multi-page TIFF combine mode, and no daily limits, no account, no watermark and no paywall. 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 a WebP?

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 scans — one file, one page per image. For anything else — sharing, web, storage — keep the WebP or use WebP to JPG instead and keep the smaller file.

Files are checked by their contents, not their name: a WebP saved as .txt still converts, because the RIFF....WEBP header is what matters, while a JPG renamed to .webp is refused with a pointer to the matching converter. A corrupt or truncated WebP is refused at decode time, with a per-file error explaining what happened.

Honest limitations

No quality recovery

WebP throws away detail when it compresses. A TIFF holds the same decoded pixels, losslessly — it cannot put back what WebP discarded. Blocky artefacts in the WebP stay blocky in the TIFF. Lossless WebP is supported too, but converting it still cannot add detail — it only stops further loss.

TIFFs are much larger than WebPs

Expect roughly 20× the size for an uncompressed TIFF of a photo, less with LZW or Deflate. A 300-DPI A4 scan is about 26 MB uncompressed. Every file shows its size multiple honestly, and the batch bar shows the total before you download anything.

8-bit RGB only, alpha flattened

Output is 8-bit RGB — no 16-bit, no CMYK, no alpha channel. WebP transparency is flattened onto a white background. WebP itself is 8-bit only, so nothing is lost in bit depth — the TIFF keeps the same 8-bit pixels.

Animated WebP: first frame only

TIFF has no animation, so an animated WebP becomes a still TIFF of its first frame. The file card warns you instead of silently dropping the animation.

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.

DPI is only a tag

The DPI you pick never changes the pixels — it only records how large the image prints. A 72-DPI tag on a 4000-pixel photo still prints large; the pixels are what they are.

Metadata is stripped

Camera metadata (EXIF, including location) is dropped on re-encode. Orientation is applied where the browser exposes it, so the output is stored upright. There is no text layer, no OCR, and nothing searchable is added.

Frequently asked questions

Do my WebP files get uploaded anywhere?

No. Your browser decodes the WebP natively 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.

Will converting WebP to TIFF improve the quality?

No. WebP throws away detail when it compresses a photo, and no converter can put it back. The TIFF holds exactly the pixels your browser decoded from the WebP — the same picture, losslessly stored. Converting to TIFF only stops further loss: unlike saving as WebP again, re-saving a TIFF never degrades the pixels.

Should I choose LZW, Deflate, PackBits or no compression?

LZW is the default and the right choice for almost everything: it is lossless, it shrinks photos and line art well, and it is the prepress standard every print shop and layout program reads. Deflate is also lossless and often produces the smallest files on photos — pick it when size matters most. PackBits is a simpler lossless RLE format for very old software that does not understand LZW or Deflate. Uncompressed stores every pixel as 3 bytes with no compression at all — the largest files, useful only when the destination cannot decode any compression.

Which DPI should I choose?

DPI is only a tag — it never changes the pixels, it tells print shops and layout software how large the image prints. 72 DPI is for screen use, 150 DPI is fine for drafts and large prints, 300 DPI is the print standard, and 600 DPI is for high-resolution print work. A 300-DPI A4 scan is 2480 x 3508 pixels, about 26 MB uncompressed, so LZW matters at high DPI.

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 WebPs belong together as one document, for example the pages of a scan, and keep one TIFF per file when each photo is separate. Multi-page TIFFs open in most viewers, but some old software shows only the first page.

What happens to an animated WebP?

Only the first frame is converted. TIFF has no animation, so an animated WebP becomes a still TIFF of its first frame — the tool warns you on the file card instead of silently dropping the animation. For the full animation, keep the WebP or convert to a video or GIF format.

Does converting keep WebP transparency?

No. TIFF as written here stores 8-bit RGB with no alpha channel, so transparent areas are flattened onto a white background — the tool warns you on the file card when it finds transparency. If you need the transparency kept, keep the WebP or convert to PNG with another tool — there is no WebP to PNG converter on this site yet.

Why is the TIFF so much bigger than the WebP?

WebP compresses photos lossily to a fraction of their raw size, while TIFF stores the decoded pixels losslessly — even LZW only compresses them, it never throws detail away. A 1920x1080 photo is about 6 MB as an uncompressed TIFF and often under 300 KB as a WebP — roughly 20 times larger, less with LZW or Deflate. This tool shows the original and TIFF size for every file, with the size multiple, so the trade-off is never hidden.