Converting TIFF to AVIF produces the smallest possible modern image files from archival TIFF source. AVIF typically compresses to 50% of equivalent WebP, making it ideal for modernizing large TIFF libraries for web delivery.
Drag & drop image files here, or browse
Drop your TIFF files here
Encoding is slow (AVIF uses AV1 video compression). Lossless AVIF preserves exact 8-bit pixels; lossy AVIF at high quality is visually indistinguishable. 10- and 12-bit AVIF can preserve more of 16-bit TIFF's precision than WebP or JPG. Alpha transfers cleanly.
AVIF works in Chrome 85+, Firefox 93+, Safari 16+, modern Edge, macOS, and iOS.
TIFF is a 1986 container format used throughout professional photography, print production, and archival imaging. It supports lossless compression, multiple pages, 16-bit-per-channel color, embedded color profiles, and high bit-depth grayscale. Print shops, medical imaging, and GIS systems expect TIFF.
AVIF is an image format built on the AV1 video codec, standardized in 2019. It supports HDR, wide color gamut, 12-bit depth, alpha, and animation. At matched perceived quality it's typically 50% the size of JPG and 20% smaller than WebP. Support is near-universal in modern browsers but spottier in image editors.
AVIF supports 10- and 12-bit output, which captures more precision than 8-bit formats. Not quite 16-bit, but much closer than JPG, PNG, or WebP.
AVIF doesn't have native multi-page support. Only the first page converts.
TIFF is a 1986 container format used throughout professional photography, print production, and archival imaging. It supports lossless compression, multiple pages, 16-bit-per-channel color, embedded color profiles, and high bit-depth grayscale. Print shops, medical imaging, and GIS systems expect TIFF.
AVIF is an image format built on the AV1 video codec, standardized in 2019. It supports HDR, wide color gamut, 12-bit depth, alpha, and animation. At matched perceived quality it's typically 50% the size of JPG and 20% smaller than WebP. Support is near-universal in modern browsers but spottier in image editors.
Yes. The converter runs entirely in your browser using WebAssembly. Your images are never uploaded, never sent to a server, and never leave your device.
There's no hard limit, but because everything runs in your browser you're bounded by available memory. Very large images (over a few hundred megapixels) can hit browser memory limits. Process in smaller batches if you run into issues.