TIFF to AVIF: Complete Conversion Guide for Web & Archiving

By Bill Crawford  ·  March 2026  ·  9 min read  ·  Last updated March 6, 2026

Connect on LinkedIn →

Why Convert TIFF to AVIF?

TIFF (Tagged Image File Format) was designed for print and archival workflows — pixel-perfect quality at any resolution. That's its strength and its weakness for the web: a single uncompressed 12-megapixel image easily exceeds 35 MB, which is completely impractical for web delivery.

AVIF (AV1 Image File Format) was built for the opposite goal: maximum visual quality at minimum file size. Using the AV1 video codec's compression engine, AVIF achieves file sizes 50–90% smaller than TIFF while remaining visually indistinguishable at quality settings of 80 or above. For web delivery, AVIF is simply the better format.

TIFF vs AVIF: Key Differences

When to Convert — and When Not To

Convert to AVIF when: you need to publish images on the web, deliver assets through a CDN, or share images via email and modern apps. AVIF will load dramatically faster and consume far less bandwidth.

Keep TIFF when: you need to edit the image in Lightroom, Photoshop, or another professional editor. TIFF is your non-destructive master file. Always archive the original TIFF before converting — AVIF is a one-way export format, not a replacement for your editing archive.

Quality Settings Explained

The quality slider runs from 1 (maximum compression, lowest quality) to 100 (minimum compression, highest quality). Here's a practical guide:

• Quality 90–95: Near-lossless. Virtually identical to the TIFF original at a fraction of the file size. Use for fine art, product photography, or medical imaging where accuracy is critical.
• Quality 80–89 (including the 85 default): Excellent quality for most photographic content. Artifacts are only visible under extreme zoom. Ideal for editorial, portfolio, and e-commerce images.
• Quality 70–79: Good quality for thumbnails, previews, and background images where slight compression is acceptable. File sizes are very small.
• Quality below 70: Visible compression artifacts. Use only for tiny thumbnails or when bandwidth is severely constrained.

Browser Support in 2026

AVIF is now well-supported across modern browsers:

• Chrome 85+ — Full encode and decode support
• Edge 85+ — Full encode and decode support
• Firefox 93+ — Full encode and decode support
• Safari 16.4+ — Decode support; canvas encoding may vary

For legacy browser support, serve AVIF with a WebP fallback using the HTML <picture> element:

<picture>
  <source srcset="image.avif" type="image/avif">
  <source srcset="image.webp" type="image/webp">
  <img src="image.jpg" alt="Description">
</picture>

AVIF vs WebP vs JPG: Which Is Best for Web?

At equivalent visual quality (as judged by SSIM scores), AVIF files are typically 20–50% smaller than WebP and 50–80% smaller than JPG. For photographic content, AVIF wins on compression efficiency every time.

That said, WebP remains the safer choice when you need to support older browsers without a fallback mechanism, and JPG is still universal when you need compatibility with every device and platform including email clients and legacy CMS tools.

Command-Line Alternative: libavif

For automated workflows or large batch jobs, libavif's avifenc tool handles TIFF input directly:

# Convert single TIFF to AVIF at quality 85
avifenc --quality 85 input.tiff output.avif

# Batch convert entire directory
for f in *.tiff; do avifenc --quality 85 "$f" "${f%.tiff}.avif"; done

For one-off conversions in the browser with no setup required, the TIFF to AVIF tool is the fastest option.

Frequently Asked Questions