Skip to main content

TIFF to AVIF converter

Convert TIFF images to AVIF format

No watermarkFree & unlimited
All processing happens in your browser. No data is sent to any server.

This pair produces the largest size drop of any TIFF target on the site. The page decodes your uncompressed scan with its own baseline parser, rebuilds the pixels in a canvas, and asks the browser to encode them as AVIF, which is a still image wrapped in AV1 intra-frame coding. Where that encoder exists, a scan that occupied nearly six megabytes typically lands in the low hundreds of kilobytes. The catch is availability: AVIF encoding through the canvas API is a Chromium feature, and browsers without it quietly hand back PNG data instead.

Key facts about TIFF to AVIF converter

Key facts about TIFF to AVIF converter
Encoder usedcanvas.toBlob with image/avif, which routes to the AV1 encoder inside the browser. No codec is fetched.
Encoder availabilityPresent in Chrome and Edge. Firefox and Safari do not encode AVIF this way and return PNG bytes named .avif.
Quality range30 to 100 in steps of 5, default 90, passed to the encoder as its quality parameter.
Typical size deltaA 5.93 MB uncompressed 1920x1080 scan lands near 150 to 400 KB at quality 90, roughly 20 to 40x smaller.
TransparencyAVIF stores an alpha plane, so a four-sample TIFF keeps its cut-out. Three-sample scans stay opaque.
Encoding speedAV1 is slow compared with JPEG. A 12-megapixel scan can take several seconds per file in the tab.
Bit depthThe canvas works in 8 bits per channel, so the AVIF is 8-bit even though the format supports 10 and 12.
Source requirementUncompressed baseline TIFF at 8 bits per sample. LZW and Deflate scans are stopped before decoding.
MetadataNo EXIF, XMP or ICC profile crosses over, so the AVIF is untagged and displayed as sRGB.
PagesOne frame from the first image directory. Multi-page TIFFs do not become AVIF image sequences.
Opens natively inChrome 85+, Firefox 93+, Safari 16.4+, macOS Ventura Preview, Windows 11 with the AV1 extension, GIMP.

What happens to your file

No part of the scan leaves the browser. The TIFF is read as an ArrayBuffer, decoded by the parser that ships with this page, and drawn into a canvas element belonging to this tab. The AV1 encode runs inside your browser through the canvas toBlob API, using your own CPU, which is why a large file takes a moment. The result is handed back as a Blob and turned into a local download link. There is no upload endpoint, no processing queue and no retention policy, because there is nowhere for a copy to exist.

About this tool

  1. 1

    Open the TIFF

    Drag a .tif or .tiff file onto the panel, or click to browse. A run can include up to twenty scans.

  2. 2

    Set the quality

    Anywhere from 30 to 100 works. AVIF holds up better than JPEG low down, so 70 is often plenty.

  3. 3

    Consider a size preset

    Capping the longest edge shortens the encode noticeably, since AV1 cost scales with the pixel count.

  4. 4

    Convert and wait

    Encoding is the slow step. The progress bar advances per file and the panel reports the finished size.

  5. 5

    Verify the output

    Check the downloaded file is genuinely AVIF, not a PNG substitute, before publishing it anywhere.

Specs & compatibility
Input and outputTakes .tiff and .tif only (image/tiff) and returns .avif with the image/avif type; any other extension is refused before decoding.
Conversion pathTIFF to AVIF runs in three steps: the page's own baseline parser reads the IFD and rebuilds the pixels, because no browser decodes TIFF; the pixels land on a 2D canvas in this tab; then canvas.toBlob with the image/avif type returns the finished file.
Browser supportThe TIFF side needs no browser support at all, only a baseline uncompressed source, because LZW, Deflate and JPEG-in-TIFF files stop with an error, while writing the AVIF needs a Chromium browser, since Firefox and Safari return PNG bytes under the .avif name.
Controls for this pairA 30 to 100 quality slider (steps of five, default 90) drives the AVIF encode, max-dimension presets from 3840 down to 200 px resize the TIFF first, and the strip-metadata toggle is moot on this pair.
Batch, caps and namingTwenty TIFF files per run at 500 MB each; one result downloads as a single AVIF, several as converted-avif-files.zip, zipped by JSZip 3.10 in page memory.
Device ceilingThe canvas caps it: past roughly 16,384 px a side Chromium refuses the bitmap and iPhone Safari gives up sooner, so an oversized TIFF fails before any AVIF bytes exist.
  • Run this conversion in Chrome or Edge. Those are the browsers whose canvas implementation actually encodes AV1; elsewhere you will get a PNG with the wrong extension.
  • A suspiciously large result is the giveaway that the substitution happened. A real AVIF of a Full HD scan should be a few hundred kilobytes, not several megabytes.
  • AVIF tolerates low quality settings better than JPEG, so try 65 or 70 on photographic scans before defaulting to 90.
  • Convert wide-gamut scans to sRGB first. No colour profile is written, so viewers assume sRGB and anything else will look desaturated.
  • Ship AVIF behind a picture element with a WebP or JPEG fallback if any of your audience is on older software that cannot decode AV1.
  • Publish a heavy archive or product scan on a site where bandwidth and Core Web Vitals matter more than universal compatibility.
  • Cut a folder of studio TIFFs down to the smallest modern format before handing them to a web team.
  • Store visual references in a repository or wiki where the uncompressed originals would bloat the history unreasonably.
Your browser most likely has no AVIF encoder. The HTML specification says that when canvas.toBlob is asked for an unsupported type it falls back to PNG, so you receive PNG bytes under an .avif filename with no error shown. Firefox and Safari behave this way today. Repeat the conversion in Chrome or Edge and the size drops to what you expected.
Usually about half, at comparable perceived quality. AV1 intra coding uses larger, more flexible prediction blocks than JPEG and handles smooth tonal areas, which dominate flatbed scans, particularly well. The gap narrows on very noisy material, where both encoders have to spend bits on detail that does not predict well from its neighbours.
AV1 encoding is computationally expensive, far more so than JPEG or WebP, and it runs on your CPU inside the tab rather than on a server. A 12-megapixel scan can take several seconds, and a batch multiplies that. Using a size preset to cap the longest edge is the most effective way to speed it up, since cost scales with pixel count.
Yes, when the TIFF has an alpha channel to keep. AVIF stores alpha as a separate plane, and the canvas preserves the fourth sample when the source file declares four samples per pixel. Ordinary three-channel scans, which is most of them, produce a fully opaque image regardless of the target format.
No. The pixels travel through a standard 2D canvas, which is an 8-bit-per-channel surface, so the encoder never sees more than eight bits even though AVIF supports ten and twelve. In addition, the TIFF reader here handles eight bits per sample only; a 16-bit file decodes incorrectly and should be reduced in an editor first.
Chrome and Edge since version 85, Firefox since 93, Safari since 16.4 on macOS Ventura, plus Preview on Ventura and later, Windows 11 with the AV1 Video Extension installed, GIMP and recent Affinity and Photoshop releases. Older desktop software and many email clients still cannot read it, so keep a fallback for public use.

Related tools

View all

Need the opposite? Try AVIF to TIFF

Updated

We use anonymous analytics to improve ToolChamp. No personal data is stored or sold. Privacy Policy