Initializing... drag & drop files here
Supports: TIFF, TIF
.tif/.tiff images from your computer. Batch conversion is supported, so you can queue a whole scan folder or photo set at once.TIFF is the workhorse of scanning, printing, and archival photography because it stores every pixel losslessly (often uncompressed or with LZW/Deflate) and supports up to 16-bit per channel color. The cost is file size — a 24-megapixel uncompressed TIFF can exceed 140 MB, which is unworkable for the web. AVIF, the AV1-based image format finalized in 2019, gives you a modern container that holds 8/10/12-bit color, HDR, wide color gamut, and alpha transparency while cutting bytes by roughly half compared to JPEG at matching quality (and far more compared to TIFF). It is now supported by Chrome 85+, Firefox 93+, Safari 16.4+, and Edge 121+, putting global browser support above 94% as of 2026.
| Property | TIFF | AVIF |
|---|---|---|
| Released | 1986 (Aldus) | 2019 (AOMedia) |
| Underlying codec | None / LZW / Deflate / JPEG / PackBits | AV1 (intra-frame) |
| Compression | Lossless (default) or lossy JPEG-in-TIFF | Lossy and lossless |
| Bit depth per channel | 1, 4, 8, 16 (and up to 32-bit float) | 8, 10, 12 |
| Color spaces | sRGB, CMYK, YCbCr, Lab*, ICC profiles | sRGB, Display P3, Rec. 2020, ICC profiles |
| HDR support | Stored, but not standardized for display | Native HDR with HLG/PQ metadata |
| Alpha transparency | Yes (1-bit or 8-bit) | Yes (8-bit alpha) |
| Multi-image / pages | Yes (multi-page TIFF) | Yes (image sequences / grids) |
| Typical file size (24 MP photo) | 70-140 MB uncompressed | 0.5-3 MB at Very High |
| Browser support | Safari only natively | Chrome 85+, Firefox 93+, Safari 16.4+, Edge 121+ |
| Best for | Print masters, scans, archival | Web delivery, modern app images |
| Preset | Approx. quality | Use it for |
|---|---|---|
| Highest | ~95% (visually lossless) | Master replacements, gallery prints, side-by-side comparisons |
| Very High (default) | ~80% | Hero images, product photography, photo blogs |
| High | ~70% | Article body images, thumbnails at 2x density |
| Medium | ~55% | Avatar tiles, listing grids where speed > pixel-peeping |
| Low / Lowest | ~35-45% | Placeholder/LQIP images, infinite-scroll preview tiles |
Need the reverse direction or a different web format? See AVIF to TIFF for restoring an archival master, TIFF to WebP for broader legacy-browser support, or Compress TIFF if you want to keep the TIFF container.
For typical photographic content the AVIF is usually 30-100× smaller than an uncompressed TIFF and roughly 5-20× smaller than an LZW-compressed TIFF. A 24 MP RGB photo that lands around 140 MB uncompressed TIFF will typically encode to 0.8-2 MB at the Very High preset. Synthetic content (line art, screenshots) compresses even more aggressively because AV1 handles flat regions extremely well.
AVIF tops out at 12 bits per channel, so a 16-bit TIFF will be rounded to 12-bit (or 10-bit depending on encoder choices). For viewing this is imperceptible — 12-bit per channel is more than four times the precision of 8-bit JPEG and well beyond what any current consumer display can show. For further editing keep the TIFF master; for distribution AVIF preserves smoother gradients than 8-bit JPEG.
Yes. AVIF carries an 8-bit alpha channel, so a TIFF with a knocked-out background (transparent PNG export from Photoshop, then saved as TIFF) keeps its transparency through conversion. This is one of AVIF's main advantages over JPEG, which has no alpha.
AVIF natively encodes HDR with HLG, PQ, and Rec. 2020 primaries. If your TIFF stores HDR metadata that the source application wrote (Photoshop, Capture One, Lightroom Classic 13+), the AVIF preserves those primaries and modern Chrome/Safari on HDR displays will tone-map them correctly. Most plain sRGB TIFFs do not carry HDR data, so converting them yields an SDR AVIF.
AVIF works in Chrome 85+ (Aug 2020), Firefox 93+ (Oct 2021), Safari 16.4+ (March 2023), Edge 121+ (Jan 2024), and Opera 71+. That covers about 94% of global browser sessions in 2026. The notable gap is legacy Internet Explorer and very old Safari/iOS (< 16). For those audiences serve a <picture> element with a JPEG or WebP fallback.
Use Quality Preset when consistency of visual quality matters more than predictable file size — every image lands at the same perceptual quality but bytes vary with content. Use Specific File Size when you have a hard byte budget (an ad-network limit of 200 KB, a CMS upload cap, an email attachment ceiling). The encoder will reduce quality just enough to fit.
Standard AVIF treats each image as a single still. If your source is a multi-page TIFF (e.g., a scanned multi-page document), we extract the first page by default. To convert all pages, split the TIFF into individual files first or use a PDF workflow — converting the multi-page TIFF to PDF and then to per-page images keeps the original order.
Against JPEG at matched quality, the Alliance for Open Media and independent studies typically measure AVIF at 30-50% smaller for the same VMAF/SSIM. Against WebP it is usually 15-25% smaller on photographic content. JPEG XL achieves similar or slightly better ratios on lossless and high-fidelity content, but browser support is far narrower in 2026 — Safari ships JPEG XL, Chrome and Firefox do not. AVIF is the safest universally supported "next-gen" choice today.
Yes. Uploads are processed for conversion only, deleted on a short retention window, and never indexed or shared. We do not sign you up, watermark output, or store the source TIFF beyond what is needed to deliver your AVIF.