Initializing... drag & drop files here
Supports: WEBP
.tif (3-char DOS-era) or .tiff — bytes are identical, only the extension differs. Use .tif for legacy software, Windows file dialogs that hide extensions, or any tool with an 8.3-filename habit.WebP (Google, 2010) is a web-delivery format: 8-bit RGB/RGBA, ICC profile support, lossless or lossy, max canvas 16,383 × 16,383 px. TIFF (Aldus, 1986) is a container format built for print, archival, and scientific imaging: arbitrary bit depths, CMYK and other subtractive color models, multi-page, optional layers, and a half-dozen compression options. They serve different ends of the pipeline, and most WebP → TIFF conversions happen because a downstream tool refuses WebP outright:
| Property | WebP | TIFF (.tif /.tiff) |
|---|---|---|
| Released | 2010 (Google) | 1986 (Aldus / Adobe), v6.0 in 1992 |
| Compression | Lossless (VP8L) or lossy (VP8) | LZW, ZIP/Deflate, JPEG, PackBits, CCITT G3/G4, or none |
| Max bit depth | 8-bit per channel (24-bit RGB / 32-bit RGBA) | 1-, 2-, 4-, 8-, 16-, 32-bit per channel |
| Color models | RGB, RGBA only | RGB, RGBA, CMYK, YCbCr, Lab*, grayscale, palette |
| Max dimensions | 16,383 × 16,383 px | 4 GB per file (classic), exabyte-scale with BigTIFF |
| Multi-page / multi-image | No (animated frames only) | Yes — primary use case for fax, scans, multi-spread layouts |
| Layers | No | Yes (Photoshop extension) |
| Transparency | Yes (8-bit alpha) | Yes (alpha channel, plus mask channels) |
| ICC color profiles | Yes (ICCP chunk, sRGB if absent) | Yes (full ICC, plus calibration tags) |
| Browser native support | Chrome, Firefox, Edge, Safari 16+ (~96% global) | None — browsers cannot render TIFF |
| Typical file size (12 MP photo) | 1-3 MB (lossy) / 8-15 MB (lossless) | 30-50 MB LZW, 50-70 MB uncompressed |
| Best for | Web delivery, small CDN assets | Print, archive, prepress, scientific imaging |
| Compression | Lossless? | Size vs uncompressed | Best for | Compatibility |
|---|---|---|---|---|
| None (uncompressed) | Yes | 100% (baseline) | Scientific imaging, raw pixel handoff to RIPs | Universal |
| LZW | Yes | ~50-70% for photos, ~30-50% for graphics | Print, archive, Photoshop default, Library of Congress preservation | Near-universal (every TIFF reader since the 1990s) |
| ZIP / Deflate | Yes | ~5-15% smaller than LZW on photos | Modern Photoshop/GIMP/Capture One workflows | Wide but not universal — some pre-2005 readers and embedded RIPs skip it |
| JPEG (in TIFF) | No | ~10-20% of uncompressed | Embedding lossy data inside a TIFF container when downstream insists on.tif | Most modern tools; native JPG usually a better choice |
| PackBits | Yes | Minimal (~0-20%) | Legacy fax, RLE-friendly graphics | Universal but obsolete for photos |
| CCITT Group 4 | Yes | Very small | Black-and-white document scans only | Document scanners, fax systems |
Stick with LZW unless you have a specific reason to choose otherwise — it's the standard for TIFF and offers the best compatibility.
None — they're the same format with two filename extensions. .tif is the 3-character DOS / Windows 8.3 holdover from the 1980s; .tiff is the modern 4-character form. The file bytes are byte-for-byte identical, and any tool that reads one reads the other. xconvert lets you pick either under File extension. If you're sending files to legacy software, a Windows pipeline that truncates extensions, or anything that originated on a pre-Windows-95 system, choose .tif.
By design. A 12 MP photo as lossy WebP runs 1-3 MB; the same image as LZW TIFF is typically 30-50 MB — roughly 15-50× larger. WebP discards visual data (the human eye won't notice) to hit small sizes for the web. TIFF preserves every pixel exactly. If your WebP was lossy, the TIFF can't recover detail that WebP already threw away — but it freezes the current state losslessly. Use LZW or ZIP compression in TIFF to claw back ~30-70%, or pick JPEG-in-TIFF if you need much smaller files.
No. TIFF can hold multiple images per file, but the typical WebP-to-TIFF path extracts only the first frame. If you need every frame from an animated WebP, convert to GIF or extract individual frames first (WebP to GIF preserves animation), then re-import the frames as a multi-page TIFF if needed.
The TIFF container supports CMYK, but the conversion preserves WebP's source color model — WebP is RGB-only. The output TIFF will be RGB (or RGBA if your WebP has transparency) with the source ICC profile embedded. For commercial CMYK offset printing, open the converted TIFF in Photoshop and use Image → Mode → CMYK Color with your printer's destination profile (e.g., GRACoL 2013, FOGRA51) before sending to the press.
LZW for almost everything — it's lossless, the Photoshop default, the Library of Congress preservation recommendation, and every TIFF reader since the 1990s handles it. Pick ZIP if you're squeezing photos and your downstream tools are modern (5-15% smaller than LZW). Pick JPEG-in-TIFF only when a workflow demands .tif extension but storage matters more than fidelity. Pick None when a RIP, scientific tool, or specific archival policy mandates uncompressed pixels.
Yes. WebP supports 8-bit alpha, and TIFF stores it as an alpha channel in the converted file. Photoshop, GIMP, Capture One, and most modern image tools will see it correctly. Some prepress tools and older Windows preview apps render TIFF alpha as solid white — if that happens, the data is intact; the renderer just isn't honoring it. Check in Photoshop's Channels panel to confirm.
Photoshop has supported WebP natively since version 23.2 (February 2022) — older installs need the WebPShop plug-in from Google. Lightroom Classic added WebP import in 11.4 (June 2022) but treats animated WebP as a still. Many pros still convert to TIFF first because their team is on mixed Adobe versions, or because their DAM (Bridge, Capture One, PhotoMechanic, Aperture-replacement) doesn't reliably index WebP catalogs. Converting to TIFF sidesteps all of that.
Yes. Drop an entire folder onto the page and apply the same compression, dimensions, and extension settings across the batch. Output downloads as a ZIP. Browser-session processing means no sign-up — fine for confidential client work, prepress masters, or NDA assets. For the other direction, see TIFF to WebP or TIF to WebP.
Re-export with PackBits or None (Uncompressed) compression. Legacy industrial software (1990s scanner drivers, older fax stacks, some embedded label printers) often can't decode LZW or ZIP. PackBits and uncompressed TIFF are the lowest common denominator. Also try .tif instead of .tiff if the tool's file picker hides 4-character extensions. For other format paths, see WebP to PNG, WebP to JPG, or Image to TIF.