AVIF to TIFF Converter — Convert AVIF to TIFF Online
Has a print shop, an archive, or a prepress tool asked for a TIFF? Drop your AVIF below and pick TIFF as the output format. Free, private, and entirely in your browser with no upload required.
Drop images here or click to browse
Supports HEIC, WEBP, AVIF, BMP, TIFF, SVG, GIF, ICO, PDF, JPG, PNG
100% Private — Your files never leave your device
All conversion happens directly in your browser using JavaScript. Nothing is uploaded to any server. Your images stay on your computer the entire time.
Why Convert AVIF to TIFF?
These two formats were built for opposite ends of an image's life. AVIF is from 2019, is built on the AV1 video codec, and exists to make web pages load quickly — which it does better than almost anything else. TIFF 6.0 was published in 1992 and exists to be read, reliably, by professional software decades after it was written. Convert when your image is leaving the browser for one of these:
- Print and prepress: commercial printers, RIP software, and layout tools like InDesign and QuarkXPress expect TIFF for placed images. Essentially none of them import AVIF.
- Archival storage: uncompressed TIFF is the long-term preservation standard used by libraries and museums, chosen because its simple, stable structure will still be readable long after today's codecs are forgotten.
- Professional editing: TIFF is a native, fully supported format in Photoshop, Affinity Photo, and GIMP, and is the usual choice for a master file. AVIF support in those tools is patchy and often needs a plugin.
- Scientific and technical imaging: microscopy, GIS, and lab pipelines standardise on TIFF for its metadata support and high bit depths.
- A tool that simply refuses AVIF: the format is barely five years old and is mostly a browser affair. Plenty of desktop and industrial software has never heard of it.
If none of those apply, TIFF is the wrong destination and you should keep the AVIF — or, if you need something more portable that is still compressed, use AVIF to PNG for a lossless copy, AVIF to JPG for a small one, or AVIF to WebP to stay on the web with wider browser support. The image format by use case guide names a target for each job.
AVIF vs TIFF: Quality and File Size Compared
The conversion adds no loss — but it undoes none either
The TIFF written here is uncompressed, so it stores exactly the pixels your browser decoded from the AVIF. Nothing is requantised, resampled, or thrown away on the way out. That is worth stating plainly because it is the question people actually have, and the answer is genuinely reassuring.
What the conversion cannot do is reverse time. AVIF is normally saved lossily, and the codec's decisions — smoothed gradients, softened texture, blurred chroma detail — are part of the pixels by the time any decoder reads them. A TIFF made from a lossy AVIF is a perfect copy of an imperfect image. It will be dramatically larger, and it will not look one bit better than the AVIF did. If you still have the original camera file or master, convert that to TIFF instead.
Where AVIF is ahead, and where it loses
AVIF genuinely beats TIFF on compression, and it is not close: the same photograph is routinely a hundred times smaller. AVIF also stores 10- and 12-bit colour, where the TIFF this tool writes is 8-bit. Two caveats follow from that. First, a 10-bit or HDR AVIF loses its extra headroom here, because the decoded pixels pass through your browser's 8-bit canvas before the TIFF is assembled — the file converts and looks right, but the depth is gone. Second, the TIFF is 8-bit sRGB with no embedded ICC profile and no CMYK. Where TIFF wins is everywhere outside a browser: support in professional software, predictable structure, and a thirty-year track record of still opening.
Transparency survives
If your AVIF carries an alpha channel, the converter writes a 32-bit RGBA TIFF and keeps it, partial transparency included. Fully opaque images get a leaner 24-bit RGB file instead, since a redundant alpha channel costs a byte per pixel and some print software refuses it outright. That is a concrete advantage over AVIF to BMP, where a 24-bit bitmap has nowhere to put the alpha and flattens it onto white.
Expect a very large file
Because the TIFF is uncompressed, its size is fixed by the image's dimensions alone — three bytes per pixel, or four if the AVIF carries transparency, plus a header under 200 bytes:
| Dimensions | Typical source | TIFF size |
|---|---|---|
| 800 × 600 | Small web image | 1.4 MB |
| 1280 × 720 | 720p | 2.6 MB |
| 1920 × 1080 | 1080p | 5.9 MB |
| 2560 × 1440 | 1440p | 10.5 MB |
| 3840 × 2160 | 4K | 23.7 MB |
| 4032 × 3024 | 12 MP phone photo | 34.9 MB |
Those figures are arithmetic, not estimates. To put a real number on the jump: a 1600×2000 photograph saved as a 37 KB AVIF comes out of this converter as a 9.2 MB TIFF — roughly 250 times larger, for pixels that are identical to the ones the AVIF already contained. That ratio is not a bug and it is not a sign that anything went wrong. It is the entire trade: disk space in exchange for a format professional tools will not argue with.
Use Cases: Print and Archival Workflows
Print and prepress
This is what TIFF is for, and getting off AVIF for print is unambiguously right — print drivers, RIPs, and prepress tools broadly do not accept it. The format handles high bit depths, embedded colour profiles, and CMYK separations, which is exactly why print shops ask for it, and its uncompressed variant leaves nothing for a RIP to misinterpret. Two honest caveats about the file this tool produces: it is 8-bit sRGB rather than CMYK, and its header records 72 DPI. Neither is usually a problem — most printers accept sRGB and convert to CMYK in their own colour-managed workflow, and DPI is a note about intended physical size rather than a property of the pixels. Set the real output resolution in your layout software, and let the shop handle the colour conversion unless they have asked you to do it.
Archival and preservation
Uncompressed TIFF is the standard libraries, museums, and national archives reach for, and the reason is structural rather than sentimental: the file is a header followed by raw pixels, with no codec to reimplement and no patents to outlive. AVIF may well still be readable in fifty years, but it depends on an AV1 decoder being available; a TIFF can be parsed from its specification by anyone with a hex editor and an afternoon.
Be clear-eyed about what you are preserving, though. Archiving a TIFF made from a lossy AVIF preserves the compression artifacts in perpetuity, at a hundred times the size. TIFF is the right archival container for a master file — a scan, a raw conversion, an original render. It is a poor one for an image that has already been squeezed for the web. If the AVIF is all you have, converting it to TIFF is a reasonable hedge against future decoder availability, but it buys longevity, not quality.
Where TIFF is the wrong answer
- Anything on the web. Chrome and Firefox will not display a TIFF at all, and while Safari renders it natively, that only makes the failure inconsistent. You would also be shipping megabytes where AVIF ships kilobytes.
- Email attachments. An uncompressed TIFF blows past size limits immediately.
- Keeping an animation. A baseline TIFF holds one still image; an animated AVIF converts to its first frame.
- Saving space. If you want a lossless copy that is a fraction of the size, AVIF to PNG is the better move.
How to Convert AVIF to TIFF
- Drag your AVIF file into the drop zone, or click to browse and select it.
- Choose TIFF from the Output Format menu.
- Download the TIFF — it's saved straight to your device.
There is no quality slider for TIFF, because there is no compression to tune. You can drop several AVIF files at once and take them away together as a ZIP, though bear in mind what the table above implies for a batch: ten 12-megapixel photos come to roughly 350 MB as TIFFs.
Two things to know about how this works. Your browser's own AVIF decoder reads the file, so it needs to be a browser that supports AVIF — Chrome, Firefox, Edge, or Safari 16.4 and later. And the TIFF is assembled in JavaScript on your machine, which means nothing you drop here is uploaded to a server. When you are done, going back is easy: TIFF to JPG flattens the result to a small shareable copy, and TIFF to PNG keeps every pixel while compressing losslessly.
Frequently Asked Questions
Why convert AVIF to TIFF?
Because the image is leaving the web. AVIF arrived in 2019 and is built on the AV1 video codec, so it is superb at making pages load quickly and almost unknown outside browsers. Print shops, prepress software, scientific pipelines, and digital archives were built around TIFF and frequently accept nothing else. You are not converting for quality here — you are converting because the tool on the other end of the request reads TIFF. If the image is staying on a website, keep the AVIF.
Does converting AVIF to TIFF lose quality?
The conversion itself adds no loss at all. The TIFF this tool writes is uncompressed, and it stores exactly the pixels your browser decoded from the AVIF — byte for byte, with nothing requantised or resampled on the way out. What it cannot do is recover detail that was already discarded. Most AVIF files are saved lossily, and those compression decisions are baked into the pixels by the time anything reads them. The TIFF is a faithful, much larger copy, not a restored one.
Why is the TIFF so much bigger than the AVIF?
Because this converter writes an uncompressed TIFF, and AVIF is one of the most efficient still-image codecs ever shipped. AVIF works hard to predict each pixel from its neighbours; an uncompressed TIFF simply writes all of them out at three bytes each. That makes the TIFF's size a function of the image's dimensions and nothing else — a 1920×1080 image is about 5.9 MB whether it is a detailed photograph or a blank white rectangle. Growing by a factor of a hundred or more is the normal, expected outcome, and it is the price of a format that prepress and archival software trusts.
Does the TIFF keep transparency?
Yes. If your AVIF has an alpha channel, the converter writes a 32-bit RGBA TIFF and the transparency survives intact, including partial transparency such as a soft edge or a drop shadow. If every pixel is opaque it writes a smaller 24-bit RGB TIFF instead, because an unnecessary alpha channel costs a byte per pixel and some print software objects to it. This is a real advantage over BMP, which has no alpha channel at all and has to flatten transparency onto white.
Is the TIFF CMYK, and will my print shop accept it?
It is RGB, not CMYK, and it carries no embedded ICC profile. That is fine for the great majority of jobs — most print shops and print-on-demand services accept sRGB files and handle the conversion to CMYK themselves as part of their own colour-managed workflow. If your printer has specifically asked for CMYK separations or a particular profile, do that conversion in Photoshop, Affinity Photo, or GIMP after this step. A browser cannot produce CMYK.
What happens to a 10-bit or HDR AVIF?
It comes out 8-bit. AVIF can store 10- and 12-bit colour, which is one of its genuine advantages over JPEG, but the decoded pixels land in your browser's 8-bit sRGB canvas buffer before the TIFF writer ever sees them. The file converts and looks correct, but the extra headroom is gone and cannot be recovered from the TIFF. If you need to keep a high bit depth for grading or archival master work, decode the AVIF with desktop software that writes a 16-bit TIFF directly.
What DPI is the converted TIFF?
72 DPI, which is simply what the header says because an AVIF does not carry a meaningful print resolution for the converter to preserve. DPI is only a note about intended physical size — it does not change a single pixel. What actually determines print quality is pixel dimensions: a 3000×2400 image prints cleanly at 10×8 inches because that works out to 300 pixels per inch. Set the output resolution in your layout or print software, where it belongs.
Will an animated AVIF stay animated?
No. AVIF can hold an animation, but a baseline TIFF like this one stores a single still image, so converting an animated AVIF gives you its first frame. That is a limitation of the target format rather than of this converter. If you need to keep the motion, convert to GIF instead.
Do I need a browser that supports AVIF?
Yes. The decoding is done by your browser's own AVIF decoder, so the file has to be one it can open — Chrome, Firefox, Edge, and Safari 16.4 and later all qualify. On an older browser the converter will report that it could not load the image. Everything after decoding, including assembling the TIFF itself, happens in JavaScript on your machine, so nothing is uploaded and confidential or client artwork never leaves your computer.