IntactFile

Repair corrupted AVIF images — they never leave your device

The symptom tells you the prognosis. Match your image to one of the three cases below and you'll know whether it's truly damaged — or just opened in software too old to support AVIF — before you spend anything.

Your file never leaves your device — repair runs in your browser. 0 bytes uploaded.

Your data is the big block — usually intact. What breaks is the small index. Repair rebuilds it.

Drop a file here or browseTap to choose a file

ZIP · Office · PDF · video · JPG · PNG · RAR/7z · SQLite — repaired right here in your browser. Nothing is uploaded

0 bytes uploadedFree: 3 repairs/day — up to 500 MB video, 100 MB docs & archives, 50 MB photos. Free download. Single repair €5.90. No account required.

Short answer: drop an AVIF here and the tool sorts it into one of three cases — won't-open (a damaged container or offset table around an intact image), incomplete (the download or save was truncated, so part of the image is gone), or unsupported (not corrupt at all — the software is simply too old for AVIF). It runs in your browser: the file is never uploaded, 0 bytes leave your device, and you can confirm that in the browser's Network tab. It repairs the container structure right in your browser now — stripping a garbage prefix, resyncing box sizes, re-anchoring the offset table — and because AV1 decodes in browsers, the repaired file can be previewed right here. The honest limit: a truncated tail, missing tiles, and payload bit-rot can't be brought back — that data isn't in the file.

AVIF shows a broken image, or won't open? Start here

  1. Drop the image
  2. Local read — which of the three cases it is
  3. Honest prognosis, before anything else

Fixing an AVIF starts with knowing whether it's actually damaged. AVIF uses the same box container as HEIC and MP4 — a run of structural boxes (dimensions, an item-location table) wrapping an AV1-coded picture — so the repairs are the same shape: strip a garbage prefix, resync box sizes, re-anchor the offset table, salvage what survived a truncation. Where the product stands, plainly: the structural AVIF enginerepairs the container in your browser now; it recovers the container and the surviving image data and Exif, and because AV1 decodes in browsers it can confirm the recovered image actually renders, previewed right here. It runs the same way as everything we make: in your browser, no upload.

What broken AVIFs look like — three cases

These blocks are illustrations, not screenshots, but if you've got a problem image open right now, you'll recognize yours:

Won't open anywhere. Broken-image icon in every viewer. Usually a damaged container box or an item-location table pointing the wrong way — the coded picture behind it survived.Best structural repair odds of the three.
Half renders, then stops. The download or save was truncated, so the tail is missing. The part that arrived is real and salvageable; the rest is data that no longer exists.Partial recovery only, honestly.
Works in a new browser, not an old app. Nothing is wrong with the file — that software just doesn't support AVIF yet.Not a repair problem: open it somewhere newer.

Why the cases differ: an AVIF is a short run of structuralboxes (dimensions, the meta box, aniloc table of byte offsets) followed by an AV1-coded picture — one image or a grid of tiles. Box or offset damage leaves the picture intact but unreachable (case 1): repair the structure and it returns. Losing the end of the file removes real image data (case 2): a hard boundary, because there's nothing left to decode there. And case 3 isn't corruption at all — it's just software older than the format.

The symptoms this covers

The image cannot be displayed because it contains errors.

Browser — a damaged container, or a download that arrived truncated.

Unsupported image type.

An older app or browser — misleading here: the file is usually fine, the software just predates AVIF. Try it somewhere newer before assuming it's broken.

Broken-image icon, half the picture, then nothing.

A partial download or interrupted save — the classic incomplete case.

Where broken AVIFs come from

Two sources dominate. Transfer trouble: an interrupted download, a CDN that cut the response short, a save that stopped partway — the file ends up truncated, missing its tail.Conversion and recovery output: image pipelines that crashed mid-encode, or files carved back by a recovery tool that guessed the boundaries and returned a garbage prefix or the wrong length. Recovery finds bytes; repair makes them a picture again. If your AVIFs came out of a download that failed or a recovery tool, diagnose them here before assuming they're lost.

What this can and can't fix

Repairable

  • A garbage prefix before the file, or wrong box sizes — stripped and resynced so the container parses again
  • An item-location (iloc) table pointing at the wrong offsets — re-anchored to the real image data
  • Truncated files — the surviving image data and Exif are salvaged and reported honestly

Not repairable

  • The part past a truncation — that region is data that doesn't exist in the file, and no tool invents it; no AI fill
  • An "unsupported" AVIF in old software — nothing to repair; open it in a newer browser instead of trying to fix a healthy file
  • Files that read 0 bytes or contain another file's fragments — a recovery problem, not a repair problem

The current honest boundary: this page tells you which of the three cases your AVIF is and, when the container is the problem, repairs it right in your browser now — and because AV1 decodes in browsers, previews the result here — like everything else we make. The diagnosis is free either way — you'll know the prognosis before anyone asks you for a cent.

FAQ

How do I fix a corrupted AVIF file?

First separate two things that both look like "broken." An AVIF that shows a broken-image icon everywhere usually has a damaged container — the box structure or the offset table around an intact AV1 image — which is the structural class worth repairing. An AVIF that works in a new browser but not an old app isn't damaged; that software just doesn't support AVIF yet. Drop the file above: the tool reads it locally, tells you which one you have, and repairs the container structure right in your browser now — stripping a garbage prefix, resyncing box sizes, re-anchoring the offset table. Because AV1 is decodable in browsers, the repaired file can be previewed right here. Like every engine here, it runs in your browser with nothing uploaded. The honest ceiling: truncated or missing tiles and payload bit-rot can't be recovered — that data isn't in the file.

Why does my browser show a broken image for an AVIF?

Two common reasons, and they have opposite fixes. If the download was interrupted or the CDN truncated the response, the file is genuinely incomplete — the tail is missing and only the part that arrived can be recovered. If instead the browser or app is simply old, AVIF isn't supported there and the untouched file will display fine somewhere newer. The tool tells the two apart by reading the file's structure, so you fix the right problem.

Is a half-rendered AVIF recoverable?

The part that arrived is; the part that didn't isn't. AVIF stores the image as AV1-coded data — a single image or a grid of tiles. A truncated file loses whatever sat past the cut, and that region can't be reconstructed because it isn't in the file. Repair salvages the surviving structure and any embedded Exif and reports honestly how much made it, rather than pretending the missing part can be guessed back.

Can I just re-download the AVIF instead?

If the source is still there, yes — and it's the cleanest fix. A broken-on-download AVIF is a truncation, and a fresh, complete download replaces the missing tail entirely, which no repair can do. Reach for repair when the original is gone and the only copy you have is the incomplete one: then salvaging the surviving portion is the best available outcome.

Does repairing an AVIF upload it anywhere?

No. AVIF repair runs entirely in your browser — 0 bytes leave your device, verifiable in the browser's Network tab. Nothing is sent to a server. AVIF's AV1 image data is, unlike HEVC, broadly decodable in browsers, so the tool can preview the repaired image right here to confirm it actually decodes — still without uploading anything.

Related: iPhone photo won't open — repair HEIC · JPG shows gray boxes — repair JPG ·verify the zero-upload claim