TIFF to WebP Converter
Drop TIFF files, get web-ready WebPs back — 100% in your browser. No uploads, no accounts, no limits. Batch convert, multi-page TIFFs, every page as its own WebP.
100% in-browserNo uploadsFree · no accountBatch up to 20 filesMulti-page TIFFsLossless or lossy WebP
Scans and print files saved as TIFF are pixel-perfect but huge — and many apps, forms and the web only accept WebP. WebP is the modern web format: typically 25–35% smaller than PNG or JPG at quality 85, and it keeps transparency — but it is lossy unless the Lossless toggle is on.
Drop TIFF files here
or — multiple files welcome
Up to 25 MB per file · up to 20 files per batch · nothing ever uploads
Loading the WebP encoder…
Privacy proof — verify it yourself
This page processes your images entirely on your device. Your file data never leaves the device — the only third-party requests are the site’s own analytics, which load at page open and never see your files.
External requests while you use this page: 0 (zero — as it should be)
- Press F12 to open developer tools, then open the Network tab.
- Drop a TIFF file above and let it convert.
- Watch the Network tab: no file uploads while it works — the only requests are the site’s analytics, which load at page open. The counter above shows the same number live.
How to convert TIFF to WebP without uploading it
- Drop your TIFF files above — or paste one straight from your clipboard. You can add up to 20 at once.
- Pick a quality and width (quality 85 and 800 px are good defaults for the web; Original keeps every pixel). Turn Lossless on when every pixel must survive exactly. Multi-page TIFFs become one WebP per page, numbered in order.
- Download each page, or grab everything as one ZIP. Your originals are untouched and your file data never leaves your device.
Why convert TIFF to WebP at all?
TIFF is the format scanners, cameras and print shops use because it keeps every pixel — but that makes files huge, and many upload forms, email clients, messaging apps, websites and older programs only accept web formats. WebP is the modern web format: the same image is typically 25–35% smaller than PNG or JPG at quality 85 with no visible difference, it keeps transparency, and every modern browser displays it. That weight is time your visitor waits — especially on a phone — which is why switching a site's TIFFs to WebP is one of the cheapest PageSpeed wins there is. Keep the TIFF as your master copy for editing, and publish the WebP.
Lossy or lossless — which should you pick?
Pick lossy (the default, quality 85) when the image is going on a website, into a blog post, or onto Discord or a forum: it is the small file that loads fast, and at quality 85 it looks identical to the original for almost every photo — typically 25–35% smaller than the same image as PNG or JPG. Pick lossless when every pixel has to survive exactly — a master you will edit further, or an image with razor-sharp edges. Lossless files are bigger, sometimes bigger than the TIFF for scans with large flat areas, because lossless cannot throw detail away. Either way, keep the TIFF as your master copy and publish the WebP.
Honest limitations
- WebP is lossy unless Lossless is on — the output discards some detail. Quality 85 is visually identical to the original for most photos, but quality 100 is near-lossless, not pixel-perfect. Keep the TIFF as your master copy.
- Lossless WebP is usually much smaller than the TIFF but larger than a lossy WebP of the same image — lossless cannot throw detail away, so for photos it can come out bigger than a lossy WebP. If the file comes out bigger than the TIFF, the card says so — use lossy mode for publishing instead.
- 16-bit TIFFs are tone-mapped to 8-bit — WebP only stores 8 bits per channel, so the extra depth is gone. On a standard display the result looks the same, but keep the original if you need the depth.
- CMYK TIFFs use a simple conversion — the decoder converts CMYK to RGB without a colour profile, so colours can shift slightly compared with a colour-managed application. The tool tells you on the file when it happened.
- JPEG-compressed TIFFs are untested with this decoder — the old JPEG-in-TIFF flavour may fail or decode wrongly. Convert the source to an uncompressed or LZW TIFF first if it does.
- TIFF orientation tags are read and reported but NOT applied — a sideways scan stays sideways. Rotate it in an editor first if that matters.
- TIFFs with large flat areas may not shrink much — scanned documents and line art already compress extremely well, so the WebP can come out larger. The tool says so on the file instead of hiding it.
- EXIF metadata is dropped on re-encode — keep the original if you need camera or scan settings.
- "Typically 25–35% smaller" is scoped to PNG/JPG comparison only — it compares a lossy WebP at quality 85 with the same image as PNG or JPG. It is never a guarantee, and it is never claimed against the TIFF itself, which can already be tiny for flat scans.
- Estimates are estimates — the size shown while converting is a rough model; the real size is shown once conversion finishes.
Frequently asked questions
How can I convert TIFF to WebP without uploading it anywhere?
This converter runs entirely in your browser: it decodes your TIFF with a TIFF decoder running on your device and re-encodes it as WebP with the libwebp encoder running on your device. Your file data never leaves the device — the only third-party requests are the site's own analytics, which load at page open and never see your files. Verify it in the Network tab while it works.
What happens to a multi-page TIFF?
Each page becomes its own WebP, named after the original file with the page number added — for example scan.tif becomes scan-page-01.webp, scan-page-02.webp, and so on. You can download pages one by one or grab them all in a single ZIP.
Which TIFF files can this converter open?
Uncompressed, LZW, Deflate and PackBits TIFFs in 8-bit RGB or greyscale, including multi-page files. 16-bit TIFFs are accepted and tone-mapped to 8-bit, which looks the same on a standard display. CMYK TIFFs are converted with a simple profile-free conversion, so colours may differ slightly from a colour-managed application. JPEG-compressed TIFFs are untested with this decoder. Files that are not really TIFFs — a JPEG renamed to .tif, for example — are refused with a message naming the real format.
Is the WebP output lossless?
Only when the Lossless toggle is on. With it on, the encoder is libwebp's true lossless mode, which stores every pixel exactly — a lossless WebP decodes back to the identical image. The one exception is fully transparent pixels: they keep their transparency exactly, but the colour stored underneath them (which nothing can see) is discarded by the encoder. With the toggle off (the default), the output is lossy WebP at the quality you pick: quality 85 looks identical to the original for most photos, and quality 100 is visually near-lossless but not pixel-perfect. Keep your TIFF as the master copy and use WebP as the published version.
Is WebP really smaller than TIFF?
Usually, yes — a TIFF photo re-encoded as lossy WebP at quality 85 is typically 25–35% smaller than the same image as PNG or JPG, because WebP predicts neighbouring pixels better — and this tool shows the before and after size honestly for every file, so you can see the saving instead of taking our word for it. Flat graphics with few colours shrink less, and a lossless WebP can be larger than the TIFF for scans with large flat areas, because lossless cannot throw detail away and TIFF already compresses those areas extremely well. If a file comes out bigger, the card says so and you can keep the TIFF.
What happens to 16-bit TIFFs and CMYK TIFFs?
WebP only stores 8 bits per channel, so a 16-bit TIFF is tone-mapped to 8-bit — the difference is imperceptible on a standard display, but the extra depth is gone, so keep the original if you need it. CMYK TIFFs are converted with a simple profile-free conversion rather than a colour-managed one, so colours can shift slightly; the tool tells you on the file when it happened.
Does the WebP keep transparency?
Yes. WebP stores an alpha channel, so transparent areas in the TIFF stay transparent in the WebP — the preview shows them against a checkerboard so you can see it. A JPG of the same image would flatten transparency onto a solid colour, which is one reason to choose WebP.
Why is my WebP larger than the original TIFF?
TIFFs with large flat areas — scanned documents, line art, diagrams — already compress extremely well, so WebP has nothing to gain and can come out larger, especially with the Lossless toggle on, because lossless cannot throw detail away. Lossy WebP at quality 85 is usually much smaller for photos. The tool tells you honestly on each file when the WebP is larger.
Is there a file size or daily limit?
No daily limit, no account. A 25 MB cap per file and 20 files per batch apply, because browsers cannot safely hold larger images in memory. Very large TIFFs are also limited to 50 megapixels for the same reason.
Does converting strip EXIF data or change orientation?
Re-encoding drops EXIF metadata (camera settings, location, scan settings) — keep the original if you need it. TIFF orientation tags are read and reported but NOT applied, so a sideways scan stays sideways; rotate it in an editor first if that matters.
How do I verify my files really never upload?
Open developer tools (F12), go to the Network tab, then convert a file. Your file data never leaves your device — the only third-party requests are the site's own analytics, which load at page open and never see your files. The live counter above shows the same number.