Initializing... drag & drop files here
Supports: TIFF, TIF
.tif / .tiff images. Multi-page TIFFs and batch uploads are both supported.TIFF is the gold standard for print masters, scanner output, and archival imaging — but it is dead weight on the web. Browsers don't render TIFF natively, the files routinely run 20-100 MB apiece, and every megabyte you ship costs page-load time and bandwidth. WebP, released by Google in 2010, was built specifically to fix this: it reduces file size by 26% vs PNG (lossless) and 25-34% vs JPEG (lossy) at equivalent visual quality, and it now reaches roughly 95% of global browsers including Safari 16+ (Sept 2022), Chrome 32+, Firefox 65+, and Edge 18+.
<img> and <picture> accept WebP directly.| Property | TIFF (.tif /.tiff) | WebP (.webp) |
|---|---|---|
| Released | 1986 (Aldus, now Adobe) | 2010 (Google) |
| Compression | Lossless (LZW, ZIP, PackBits) or uncompressed; lossy JPEG-in-TIFF optional | Both lossless and lossy in the same container |
| Typical size (12 MP photo) | 30-70 MB | 0.5-3 MB lossy; 5-12 MB lossless |
| Max dimensions | 4,294,967,295 x 4,294,967,295 px (theoretical) | 16,383 x 16,383 px |
| Bit depth | 1, 4, 8, 16, 32 bit per channel | 8 bit per channel |
| Color spaces | RGB, CMYK, Lab, Grayscale, indexed, multi-channel | RGB + alpha (no CMYK) |
| Transparency | Yes (alpha channel) | Yes (alpha channel) |
| Multi-page / animation | Multi-page TIFF (each page a separate image) | Animated WebP (frame sequence) |
| Browser support | None (no major browser renders TIFF) | ~95% global support — Chrome 32+, Firefox 65+, Edge 18+, Safari 16+ |
| Best for | Print masters, archival, prepress, scientific imaging | Web pages, app assets, e-commerce thumbnails |
Sources: MDN Image Types, caniuse WebP, Google WebP.
| Preset | Approx. quality factor | Size vs TIFF source | Typical use |
|---|---|---|---|
| Lossless (Yes) | 100 (pixel-perfect) | 50-75% smaller | Archival masters, OCR source images, technical drawings |
| Very High (Recommended) | ~90 | 90-98% smaller | Hero images, photography portfolios, product galleries |
| High | ~80 | 95-99% smaller | Blog images, CMS uploads, social previews |
| Medium | ~65 | 97-99% smaller | Thumbnails, lazy-loaded gallery tiles, email signatures |
| Low / Lowest | ~50 / ~30 | 98-99.5% smaller | Placeholder / LQIP, dominant-color previews |
If the TIFF is a scan, a CAD render, a screenshot, or any image with sharp edges and flat color regions, lossless WebP preserves every pixel and still beats PNG by about 26% in file size. If the TIFF is a photograph or a scan with continuous-tone color, lossy WebP at Very High is almost always visually indistinguishable from the source and is 10-30x smaller. Try one of each and compare side-by-side at 100% zoom — for photographic content, most people can't tell the difference.
WebP is an 8-bit-per-channel format, so a true 16-bit TIFF (common from RAW conversions, medical imaging, or HDR workflows) gets quantized to 8 bits per channel during conversion. For most display targets — web, social, presentations — this is invisible. For print proofing, color grading, or scientific analysis, keep the original TIFF and convert only the deliverable to WebP. Wide-gamut color profiles (Adobe RGB, ProPhoto) are converted to sRGB during the WebP conversion.
Yes. A multi-page TIFF (common from scanners producing multi-sheet documents or fax archives) converts to one WebP per page, batch-named so they sort in order. If you want a single animated WebP from the pages instead, the GIF to WebP flow accepts an animated source — convert your multi-page TIFF to GIF first, then to animated WebP.
Yes. WebP has a full 8-bit alpha channel in both lossless and lossy modes. Google's data shows that lossy WebP with transparency is typically 3x smaller than the equivalent PNG, which is why product-photography teams that previously shipped transparent PNG cutouts are migrating to lossy WebP with alpha.
Roughly 95% of global browsers support WebP today, but the ~5% gap is older Safari (pre-16, released before September 2022), legacy in-house enterprise browsers, and certain native email clients. For broadest compatibility, serve WebP inside a <picture> element with a JPEG or PNG fallback — modern browsers pick WebP, older clients fall back automatically.
Drop the Quality Preset to Lossless to get a pixel-identical copy, or stay on Very High and disable any "compression speed" reduction. Lossy WebP applies a YUV color subsampling step that can soften high-contrast edges (text on a colored background, fine line art). If you see this, lossless is the right answer — your file will still be far smaller than the source TIFF.
The converter accepts large TIFFs (multi-hundred-MB scans are common). The output WebP is capped by the format itself at 16,383 x 16,383 pixels per Google's spec. If your TIFF exceeds that, use the Image resolution field to scale down, or split it into tiles before converting. For most web use cases you'll be downsizing anyway — 4K hero images are already 3840 x 2160.
Standard EXIF tags (camera, date, exposure) and the ICC color profile are preserved in the WebP output by default. GPS and proprietary maker-note tags may be stripped depending on the source. If you're publishing online and want to scrub all metadata for privacy, run the file through a stripper after conversion or use a dedicated JPG to WebP round-trip with metadata removal enabled.
Yes — see WebP to TIFF. Be aware that converting back will not restore any data lost in a lossy compression pass. If you might need the print master later, archive the original TIFF and keep the WebP as a derivative.