Skip to main content

AVIF to TIFF converter

Convert AVIF images to TIFF format

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

This pair goes the opposite way from most conversions: AVIF is one of the most tightly compressed still formats in use, and the TIFF written here carries no compression at all. Your browser decodes the AV1 bitstream, the pixels land on a 2D canvas, and a compact TIFF writer in this page emits a little-endian baseline file with ten IFD tags, eight bits per sample, three samples per pixel and a single uncompressed strip. Expect the file on disk to grow by an order of magnitude or more, which is exactly what editing and print pipelines usually want.

Key facts about AVIF to TIFF converter

Key facts about AVIF to TIFF converter
Output file sizeExactly width x height x 3 + 134 bytes. A 1920x1080 frame is 6,220,934 bytes no matter what the AVIF held.
Typical size deltaA 200 KB 1920x1080 AVIF becomes a 5.93 MB TIFF, roughly 30x larger. An 8000x6000 source reaches 137 MB.
Compression writtenCompression tag 1, meaning none. No LZW, PackBits, Deflate or JPEG-in-TIFF variant is offered.
TransparencyThree samples per pixel, so alpha is discarded. Transparent AVIF regions arrive as solid black, not white.
ColourPhotometric 2 (RGB), PlanarConfig 1 (chunky). No ICC profile is embedded, so editors assume sRGB.
Resolution tagsNo XResolution or YResolution entries are written, so a layout app applies its own default DPI. Set it there.
Bit depth8 bits per channel. A 10-bit or 12-bit AVIF is rounded down at the canvas stage before the TIFF is built.
PagesOne IFD, one page. Multi-frame AVIF sequences contribute only the first frame.
Byte orderLittle-endian (II, magic 42) classic TIFF, not BigTIFF, so stay under the 4 GB offset ceiling.
Opens natively inPhotoshop, Affinity Photo, GIMP, macOS Preview, Windows Photos, ImageMagick and InDesign place dialogs.
Browser requirementAVIF decode arrived in Chrome and Edge 85, Firefox 93, and Safari 16.4 on macOS Ventura.

What happens to your file

Nothing is transmitted. The AVIF is wrapped in an object URL and decoded by the AV1 support compiled into your own browser, then drawn into a canvas element that exists only in this tab. The TIFF bytes are assembled in a plain ArrayBuffer by JavaScript running on this page, wrapped in a Blob and handed straight to the download. Because the buffer holds the entire uncompressed image at once, very large conversions are limited by your device memory rather than by any server quota.

About this tool

  1. 1

    Select the AVIF

    Drag one or more .avif files onto the drop panel, or click it to browse. The queue accepts twenty files.

  2. 2

    Pick an output size

    Leave the size on Original, or choose 4K, 2K, Full HD, HD, Medium, Small or Thumbnail to cap the longest edge.

  3. 3

    Convert

    Each file is decoded, rasterised and written as an uncompressed RGB strip. Large frames take a moment to allocate.

  4. 4

    Download

    Grab a single .tiff, or collect a multi-file batch as one ZIP archive.

  5. 5

    Set the DPI in your editor

    Open the TIFF in your layout or retouching app and assign the print resolution there, since none is stored in the file.

Specs & compatibility
Input and outputTakes .avif only (image/avif) and returns .tiff with the image/tiff type; any other extension is refused before decoding.
Conversion pathAVIF to TIFF runs in three steps: an <img> element decodes the AVIF, which the browser itself must be new enough to read; the pixels land on a 2D canvas in this tab; then getImageData feeds a baseline IFD writer that assembles the file in page memory.
Browser supportThe AVIF side needs Chrome 85, Firefox 93 or Safari 16.4 to decode, while writing the TIFF needs nothing from the browser, the directory being written in the page.
Controls for this pairNo quality slider, TIFF not being a lossy target here, so the max-dimension presets from 3840 down to 200 px are the only way to hold the TIFF down in size against the AVIF.
Batch, caps and namingTwenty AVIF files per run at 500 MB each; one result downloads as a single TIFF, several as converted-tiff-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 AVIF fails before any TIFF bytes exist.
  • Use the size presets deliberately on this pair. Halving the longest edge quarters the output, because uncompressed TIFF scales with raw pixel count and nothing else.
  • If the AVIF has transparency you care about, convert to PNG instead. TIFF output here is three-channel and turns those areas black.
  • Once the file is open in an editor, re-save it with LZW or ZIP compression. Photographic content typically shrinks by a third with no pixel changes.
  • Very large sources can exhaust memory before the download starts, since the whole uncompressed image sits in one buffer. Convert big frames one at a time.
  • A TIFF this page writes is untagged RGB. Assign an sRGB profile on import so your editor does not guess a different working space.
  • Hand a print shop or a magazine production desk a format their prepress software accepts, starting from a web-optimised AVIF master.
  • Bring an AVIF into an older scientific or GIS tool that reads baseline TIFF but has never heard of AV1.
  • Produce an uncompressed intermediate before heavy retouching, so repeated saves add no further generation loss.
AVIF stores a photograph as an AV1 keyframe, which is one of the densest still encodings available. The TIFF written here stores every pixel literally: three bytes per pixel, plus a 134-byte header. That is the point of the format in a print workflow, but it does mean a thirtyfold jump is normal rather than a fault.
Not on this page. The writer sets the Compression tag to 1, uncompressed, because that path needs no codec and always produces a file every reader can open. If you need a smaller archive copy, open the result in Photoshop, GIMP or ImageMagick and re-save it with LZW or Deflate, which is lossless and typically saves a third.
No. The file is written with three samples per pixel, so there is no alpha channel to store it in. Areas that were transparent in the AVIF end up as black, because an untouched canvas pixel is zero in all four channels and only the first three are copied. Convert to PNG or WebP when the alpha matters.
Whatever its own default is. The writer emits ten IFD tags and XResolution and YResolution are not among them, so the file states no physical resolution. InDesign, Photoshop and most RIPs fall back to their configured assumption. Place the image, then set the effective resolution by scaling it to the physical size you actually need.
No. One image directory is written and its next-IFD pointer is set to zero, which marks the end of the chain. If you need several images in one TIFF, convert each separately and combine them with a desktop tool such as ImageMagick, which can append pages into a single multi-directory file.
No pixels are thrown away beyond two rounding steps. The AVIF is decoded once and copied into the TIFF as-is, so the only losses are the reduction of 10- or 12-bit samples to 8 bits and any resize you deliberately select. Everything the AV1 encoder already discarded before you got the file is, of course, still gone.

Related tools

View all

Need the opposite? Try TIFF to AVIF

Updated

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