TIFF to AVIF Converter
Drop TIFF files, get web-ready AVIFs back — 100% in your browser. No uploads, no accounts, no limits. Batch convert, multi-page TIFFs, every page as its own AVIF.
100% in-browserNo uploadsFree · no accountBatch up to 20 filesMulti-page TIFFsLossy AVIF · quality 50–100
Scans and print files saved as TIFF are pixel-perfect but huge — and many apps, forms and the web only accept web formats. AVIF is the smallest modern web format: typically 40–60% smaller than the TIFF at quality 80 with no visible difference, and it keeps transparency — but it is always lossy, so keep the TIFF as your master copy.
Drop TIFF files here
or — multiple files welcome
Up to 25 MB per file · up to 20 files per batch · nothing ever uploads
Loading the AVIF encoder…
Privacy proof — verify it yourself
This page processes your images entirely on your device. Your file data never leaves the device — the only third-party requests are the site’s own analytics, which load at page open and never see your files.
External requests while you use this page: 0 (zero — as it should be)
- Press F12 to open developer tools, then open the Network tab.
- Drop a TIFF file above and let it convert.
- Watch the Network tab: no file uploads while it works — the only requests are the site’s analytics, which load at page open. The counter above shows the same number live.
How to convert TIFF to AVIF without uploading it
- Drop your TIFF files above — or paste one straight from your clipboard. You can add up to 20 at once.
- Pick a quality and width (quality 80 and 800 px are good defaults for the web; Original keeps every pixel). Multi-page TIFFs become one AVIF per page, numbered in order. Encoding takes a few seconds per photo — each card shows how long its encode took.
- Download each page, or grab everything as one ZIP. Your originals are untouched and your file data never leaves your device.
Why convert TIFF to AVIF at all?
TIFF is the format scanners, cameras and print shops use because it keeps every pixel — but that makes files huge, and many upload forms, email clients, messaging apps, websites and older programs only accept web formats. AVIF is the smallest modern web format: the same image is typically 40–60% smaller than the TIFF at quality 80 with no visible difference, it keeps transparency, and every modern browser displays it. That weight is time your visitor waits — especially on a phone — which is why switching a site's TIFFs to AVIF is one of the cheapest PageSpeed wins there is. Keep the TIFF as your master copy for editing, and publish the AVIF.
Why is there no lossless mode?
Because the lossless mode in this encoder is broken — and shipping a broken toggle would be worse than having none. When the vendored libavif encoder is asked for lossless output, it produces a greyscale file: a colour photo comes back without its colour (a solid red test image decodes back as grey). That was verified with two independent decoders, so it is the encoder, not the preview. Rather than offer a control that silently destroys your photos, this tool is lossy only: pick a quality (80 by default) for the image's destination — a website, a blog post, Discord or a forum — and at quality 80 the result looks identical to the original for almost every photo, typically 40–60% smaller than the TIFF. If you need every pixel exactly, convert to PNG instead, which is lossless by design. Either way, keep the TIFF as your master copy and publish the AVIF.
Why is there no canvas fallback?
With WebP, a converter can fall back to the browser's built-in canvas encoder when its own encoder fails. AVIF has no such safety net: canvas toBlob with image/avif is not reliably available — Safari cannot encode AVIF at all — so a canvas "fallback" would either fail silently or hand you a WebP file with an .avif name, which is worse than no file at all. This tool uses the vendored libavif encoder and nothing else. If that encoder cannot load, conversion is disabled and the page says so plainly, with a link to the TIFF to WebP converter instead.
Honest limitations
- AVIF is always lossy — the output discards some detail. Quality 80 is visually identical to the original for most photos, but quality 100 is near-lossless, not pixel-perfect. Keep the TIFF as your master copy.
- No lossless mode — on purpose — this encoder's lossless option produces greyscale files, so the toggle was left out rather than ship a control that silently strips the colour from your photos. For pixel-exact output, convert to PNG instead.
- AVIF encoding is slow — roughly 5–10 seconds for a large photo, because the AV1 encoder searches far more ways to pack the image into fewer bytes. The batch converts one file at a time and each card shows its encode time, so the wait is visible.
- 16-bit TIFFs are tone-mapped to 8-bit — AVIF only stores 8 bits per channel, so the extra depth is gone. On a standard display the result looks the same, but keep the original if you need the depth.
- CMYK TIFFs use a simple conversion — the decoder converts CMYK to RGB without a colour profile, so colours can shift slightly compared with a colour-managed application. The tool tells you on the file when it happened.
- JPEG-compressed TIFFs are untested with this decoder — the old JPEG-in-TIFF flavour may fail or decode wrongly. Convert the source to an uncompressed or LZW TIFF first if it does.
- TIFF orientation tags are read and reported but NOT applied — a sideways scan stays sideways. Rotate it in an editor first if that matters.
- TIFFs with large flat areas may not shrink much — scanned documents and line art already compress extremely well, so the AVIF can come out larger. The tool says so on the file instead of hiding it.
- EXIF metadata is dropped on re-encode — keep the original if you need camera or scan settings.
- "Typically 40–60% smaller" is scoped to the TIFF at the same visual quality — it compares a lossy AVIF at quality 80 with the TIFF it came from. It is never a guarantee, and flat graphics shrink less.
- Estimates are estimates — the size shown while converting is a rough model; the real size is shown once conversion finishes.
Frequently asked questions
How can I convert TIFF to AVIF without uploading it anywhere?
This converter runs entirely in your browser: it decodes your TIFF with a TIFF decoder running on your device and re-encodes it as AVIF with the libavif encoder running on your device. Your file data never leaves the device — the only third-party requests are the site's own analytics, which load at page open and never see your files. Verify it in the Network tab while it works.
What happens to a multi-page TIFF?
Each page becomes its own AVIF, named after the original file with the page number added — for example scan.tif becomes scan-page-01.avif, scan-page-02.avif, and so on. You can download pages one by one or grab them all in a single ZIP.
Which TIFF files can this converter open?
Uncompressed, LZW, Deflate and PackBits TIFFs in 8-bit RGB or greyscale, including multi-page files. 16-bit TIFFs are accepted and tone-mapped to 8-bit, which looks the same on a standard display. CMYK TIFFs are converted with a simple profile-free conversion, so colours may differ slightly from a colour-managed application. JPEG-compressed TIFFs are untested with this decoder. Files that are not really TIFFs — a JPEG renamed to .tif, for example — are refused with a message naming the real format.
Is the AVIF output lossless?
No — this tool's AVIF output is always lossy. The quality slider (50 to 100, default 80) trades file size against detail, and at 80 the result is visually identical to the original for almost every photo. Quality 100 is visually near-lossless but not pixel-perfect. There is deliberately no lossless toggle: the vendored encoder's lossless mode produces greyscale files — a colour photo comes back without its colour — so offering it would silently destroy your photos. If you need every pixel exactly, use our TIFF to PNG converter instead — PNG is lossless. Keep your TIFF as the master copy and use AVIF as the published version.
Is AVIF really smaller than TIFF?
Usually, yes — a TIFF photo re-encoded as lossy AVIF at quality 80 is typically 40–60% smaller at the same visual quality, because AVIF predicts neighbouring pixels better than any older format — and this tool shows the before and after size honestly for every file, so you can see the saving instead of taking our word for it. Flat graphics with few colours shrink less, and at quality 100 the AVIF can be larger than the TIFF for photos. If a file comes out bigger, the card says so and you can keep the TIFF.
What happens to 16-bit TIFFs and CMYK TIFFs?
AVIF only stores 8 bits per channel, so a 16-bit TIFF is tone-mapped to 8-bit — the difference is imperceptible on a standard display, but the extra depth is gone, so keep the original if you need it. CMYK TIFFs are converted with a simple profile-free conversion rather than a colour-managed one, so colours can shift slightly; the tool tells you on the file when it happened.
Does the AVIF keep transparency?
Yes. AVIF stores an alpha channel, so transparent areas in the TIFF stay transparent in the AVIF — the preview shows them against a checkerboard so you can see it. A JPG of the same image would flatten transparency onto a solid colour, which is one reason to choose AVIF.
Why is AVIF encoding so slow?
Because AVIF squeezes harder than any other web format. The AV1 encoder searches far more ways to pack each photo into fewer bytes, and that search takes time — roughly 5–10 seconds for a large photo on a typical laptop, where the same photo becomes a JPG almost instantly. The batch converts one file at a time so the page stays responsive, and each file card shows how long its encode took. The smaller file is the payoff: typically 40–60% smaller than the TIFF at the same visual quality.
What happens if my browser can't run the AVIF encoder?
Conversion is disabled, and the page says so plainly — there is no fallback that produces a different format. Unlike WebP, AVIF cannot be encoded with the browser's built-in canvas encoder: canvas toBlob with image/avif is not reliably available, and Safari cannot encode AVIF at all. Some converters quietly fall back to WebP and hand you a WebP file with an .avif name; this tool never does that. If you see the unavailable banner, try a current version of Chrome, Edge, Firefox or Safari — or use our TIFF to WebP converter instead, which works everywhere.
Why is my AVIF larger than the original TIFF?
TIFFs with large flat areas — scanned documents, line art, diagrams — already compress extremely well, so AVIF has nothing to gain and can come out larger, especially at quality 100, because lossy AVIF at high quality keeps almost every detail. Lossy AVIF at quality 80 is usually much smaller for photos. The tool tells you honestly on each file when the AVIF is larger.
Is there a file size or daily limit?
No daily limit, no account. A 25 MB cap per file and 20 files per batch apply, because browsers cannot safely hold larger images in memory. Very large TIFFs are also limited to 50 megapixels for the same reason.
Does converting strip EXIF data or change orientation?
Re-encoding drops EXIF metadata (camera settings, location, scan settings) — keep the original if you need it. TIFF orientation tags are read and reported but NOT applied, so a sideways scan stays sideways; rotate it in an editor first if that matters.
How do I verify my files really never upload?
Open developer tools (F12), go to the Network tab, then convert a file. Your file data never leaves your device — the only third-party requests are the site's own analytics, which load at page open and never see your files. The live counter above shows the same number.