AVIF to TIFF, lossless and private. Nothing ever uploads.

Drop AVIF photos below — get a TIFF per file with LZW compression and print-ready DPI tags, in batches of up to 20. Converted entirely on your device.

  • Your file data never leaves the device
  • LZW / PackBits / uncompressed
  • Batch up to 20 files + ZIP
  • Multi-page TIFF combine + DPI tags to 600

Convert AVIF to TIFF

Add your AVIF files

Drag & drop AVIF files here

or browse your files · you can also paste from clipboard (Ctrl+V)

Your browser decodes AVIF natively — no decoder download, no waiting. Animated AVIFs convert to their first frame only, and transparency is flattened onto a white background.

    No files yet. Everything stays on this device. Downloads start instantly.

    Privacy you can verify, not just trust

    Most online AVIF converters upload your photos to their servers first — and some keep a download link live for hours afterwards. This one can't: your browser decodes AVIF natively and the TIFF encoder runs entirely in your browser. Your file data never leaves the device — the only third-party requests are the site's own analytics, which count page views — and it uploads nothing, ever. There is no decoder to download and no file fetched after load for the conversion itself. Don't take our word for it:

    New cross-origin requests during use: 0
    1. Press F12 to open developer tools, then the Network tab.
    2. Convert any AVIF above. Watch: apart from the site's analytics, nothing new is requested — no uploads, and no file data ever leaves your device.
    3. Extra credit: disconnect your internet after this page loads — conversion still works.

    How to convert AVIF to TIFF without uploading it

    Every "free" online AVIF converter you've used uploads your photos to a company server, converts them there, and — in several documented cases — keeps a copy or a live download link for hours. For personal photos and anything you wouldn't post publicly, that's an unnecessary risk. The safer approach is to convert the file where it already is: on your own device.

    This tool does exactly that. When you drop an AVIF here, your browser:

    1. Decodes the AVIF natively — every modern browser includes an AVIF decoder, so there is no decoder file to download and no waiting for a library to load. Only the first frame of an animated AVIF is decoded.
    2. Flattens any transparency onto a white background, because the TIFF written here stores 8-bit RGB with no alpha channel. The file card warns you when this happens.
    3. Re-encodes the pixels as a TIFF with a pure-JavaScript TIFF encoder — little-endian header, one IFD per image, LZW, PackBits or no compression, and the DPI you chose written as XResolution and YResolution tags. Your original file is never modified.

    What makes this converter different

    The converters that top the results for this search mostly upload your files to a server (Pixsterpress, XConvert, HexaConverter and Wondershare UniConverter all convert server-side — Pixsterpress takes a batch of 20 but deletes it after an hour, HexaConverter caps free conversions at 3 files, and UniConverter allows only 1 file online), and the client-side ones we found are thin — filevolve and tools.mapree.dev convert locally in a batch but offer no compression choice, no DPI tags and no multi-page mode, forgeconvert offers LZW for 20 files but no DPI tags, no multi-page mode and no ZIP download, and veconvert is client-side but paywalled after the preview: one file costs $3.49 as a guest. This page is the only fully client-side dedicated AVIF-to-TIFF page we found that combines a batch of 20 files with a ZIP download, a genuine compression choice (LZW by default, PackBits or uncompressed), DPI tags from 72 to 600, a multi-page TIFF combine mode, and no daily limits, no account, no watermark and no paywall. It runs entirely in your browser — there is no server to upload to, no daily limits, no account and no watermark.

    When is TIFF the right choice for an AVIF?

    When the destination demands it: print shops and scanning bureaus that ask for TIFF, archives that store images losslessly, and layout software (InDesign, QuarkXPress and their peers) that places TIFFs at a stated DPI. TIFF is also the format for multi-page scans — one file, one page per image. For anything else — sharing, web, storage — keep the AVIF or use AVIF to JPG instead and keep the smaller file.

    Files are checked by their contents, not their name: an AVIF saved as .txt still converts, because the ftyp box with an avif or avis brand is what matters, while a JPG renamed to .avif is refused with a pointer to the matching converter. A corrupt or truncated AVIF is refused at decode time, with a per-file error explaining what happened.

    Honest limitations

    No quality recovery

    AVIF throws away detail when it compresses. A TIFF holds the same decoded pixels, losslessly — it cannot put back what AVIF discarded. Blocky artefacts in the AVIF stay blocky in the TIFF.

    TIFFs are much larger than AVIFs

    Expect roughly 20× the size for an uncompressed TIFF of a photo, less with LZW. A 300-DPI A4 scan is about 26 MB uncompressed. Every file shows its size multiple honestly, and the batch bar shows the total before you download anything.

    8-bit RGB only, alpha flattened

    Output is 8-bit RGB — no 16-bit, no CMYK, no alpha channel. AVIF transparency is flattened onto a white background, and 10-bit or HDR AVIFs are tone-mapped down to 8-bit by the browser canvas path.

    Animated AVIF: first frame only

    TIFF has no animation, so an animated AVIF becomes a still TIFF of its first frame. The file card warns you instead of silently dropping the animation.

    Multi-page TIFFs are not universal

    Multi-page TIFFs open in most viewers, but some old software shows only the first page. If the destination is old or unknown, send one TIFF per file instead.

    DPI is only a tag

    The DPI you pick never changes the pixels — it only records how large the image prints. A 72-DPI tag on a 4000-pixel photo still prints large; the pixels are what they are.

    Metadata is stripped

    Camera metadata (EXIF, including location) is dropped on re-encode. Orientation is applied where the browser exposes it, so the output is stored upright. There is no text layer, no OCR, and nothing searchable is added.

    Frequently asked questions

    Do my AVIF files get uploaded anywhere?

    No. Your browser decodes the AVIF natively and the TIFF encoder runs entirely in your browser, so your file data never leaves the device. The only third-party requests are the site's own analytics, which count page views. You can verify it in your browser's Network tab, or disconnect from the internet after the page loads — conversion still works.

    Will converting AVIF to TIFF improve the quality?

    No. AVIF throws away detail when it compresses a photo, and no converter can put it back. The TIFF holds exactly the pixels your browser decoded from the AVIF — the same picture, losslessly stored. Converting to TIFF only stops further loss: unlike saving as AVIF again, re-saving a TIFF never degrades the pixels.

    Should I choose LZW, PackBits or no compression?

    LZW is the default and the right choice for almost everything: it is lossless, it shrinks photos and line art well, and it is the prepress standard every print shop and layout program reads. PackBits is a simpler lossless RLE format for very old software that does not understand LZW. Uncompressed stores every pixel as 3 bytes with no compression at all — the largest files, useful only when the destination cannot decode either compression.

    Which DPI should I choose?

    DPI is only a tag — it never changes the pixels, it tells print shops and layout software how large the image prints. 72 DPI is for screen use, 150 DPI is fine for drafts and large prints, 300 DPI is the print standard, and 600 DPI is for high-resolution print work. A 300-DPI A4 scan is 2480 x 3508 pixels, about 26 MB uncompressed, so LZW matters at high DPI.

    What is a multi-page TIFF and when should I combine files?

    A multi-page TIFF is one file holding several images, one per page — the format scanners and archives use for a document of many pages. Choose the combine mode when the AVIFs belong together as one document, for example the pages of a scan, and keep one TIFF per file when each photo is separate. Multi-page TIFFs open in most viewers, but some old software shows only the first page.

    What happens to an animated AVIF?

    Only the first frame is converted. TIFF has no animation, so an animated AVIF becomes a still TIFF of its first frame — the tool warns you on the file card instead of silently dropping the animation. For the full animation, keep the AVIF or convert to a video or GIF format.

    Does converting keep AVIF transparency?

    No. TIFF as written here stores 8-bit RGB with no alpha channel, so transparent areas are flattened onto a white background — the tool warns you on the file card when it finds transparency. If you need the transparency kept, convert to PNG instead with our AVIF to PNG converter.

    Why is the TIFF so much bigger than the AVIF?

    AVIF compresses photos lossily to a fraction of their raw size, while TIFF stores the decoded pixels losslessly — even LZW only compresses them, it never throws detail away. A 1920x1080 photo is about 6 MB as an uncompressed TIFF and often under 300 KB as an AVIF — roughly 20 times larger, less with LZW. This tool shows the original and TIFF size for every file, with the size multiple, so the trade-off is never hidden.