IntactFile

AVIF to JPG — converted in your browser, not on a server

Drop an AVIF and get a universal JPEG back. AV1 decodes natively in modern browsers, so the whole conversion runs on your machine — the image is never uploaded.

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

Drop a AVIF image file hereTap to choose a AVIF image file

Decodes the AV1 image in your browser and re-encodes it as JPG. Nothing is uploaded.

100% in your browser. 0 bytes uploaded — open DevTools → Network and watch. Your file is read, never sent.

In short

AVIF (AV1 Image File Format) wraps AV1-coded picture data in the same ISO base-media box container that MP4 and HEIC use. The important difference from HEIC is that AV1 decodes natively in current browsers — so this converter is a clean, truthful operation: your browser decodes the image, draws it to a canvas, and re-encodes it as JPEG at quality 0.92. You get a real .jpg you can open anywhere. Nothing is uploaded, and you can prove it in the Network tab.

Why convert AVIF to JPG at all?

AVIF is excellent — it typically produces smaller files than JPEG at the same visual quality, and it supports transparency, wide color gamut and HDR. The catch is compatibility. Plenty of software still can't open an AVIF: older phones, desktop apps that predate the format, email clients, some CMS uploaders, and older operating systems. JPEG, by contrast, opens literally everywhere. Converting to JPG trades AVIF's efficiency for universal reach — the right call when you need to email a photo, upload it to a site that rejects AVIF, or hand it to someone on older software.

The honest fidelity caveats

We would rather tell you the trade-offs than pretend there are none. First, double compression: AVIF is already lossy, so re-encoding its decoded pixels to JPEG adds a second lossy pass — generation loss. Quality 0.92 keeps that small and usually invisible, but the JPG is not identical to the source. Second,transparency is lost: JPEG has no alpha channel, so any transparent areas are flattened onto white; if you need transparency, use PNG. Third, bit depth and gamut: the browser canvas is 8-bit sRGB, so a 10/12-bit HDR or wide-gamut AVIF is tone-mapped down to 8-bit sRGB — and JPEG couldn't store the extra range anyway. What you do keep exactly is the pixel dimensions — no resizing, no cropping.

Why "no upload" is verifiable, not a slogan

The AVIF is read with the browser's file APIs and decoded by the same native AV1 support that lets Chrome, Firefox, Edge and Safari show AVIF on the open web. The re-encode to JPEG happens on a<canvas> in the page. No request carries your image — don't take our word for it: open DevTools, select the Network tab, drop a file, and watch nothing leave. It's the same principle as ourzero-upload proof page, applied to conversion. The free size ceiling for photos is 50 MB; over that, the tool says so and points to pricing — still without uploading anything.

If the file is damaged, repair it first

A conversion tool can only convert an image the browser can decode. If your AVIF was truncated by an interrupted download, carries a garbage prefix from a recovery tool, or has a broken box structure, the AV1 decoder will refuse it — and no honest converter can produce a JPG from pixels that never decoded. When that happens, the tool runs a local structural scan and, if it finds damage, links you straight torepair AVIF to rebuild the container first. Repair the file, then come back and convert the repaired copy here.

FAQ

How do I convert AVIF to JPG?

Drop an AVIF above. Modern browsers decode AV1 — the codec inside AVIF — natively, so the image is decoded on your machine, drawn to a canvas, and re-encoded as a standard JPEG at quality 0.92. A Download button appears with the finished .jpg. Nothing is uploaded at any point: the file is read with the browser's own file APIs and never sent to a server.

Will converting AVIF to JPG lose quality?

A little, and it's worth being honest about why. AVIF is already a lossy format, so its pixels are a compressed version of the original. Saving those pixels as JPG applies a second round of lossy compression on top — this is generation loss. We encode at 0.92, which is visually high quality, but the JPG will not be bit-for-bit identical to what the AVIF decoded to. If you need to keep editing, hold on to the AVIF; if you need a file that opens everywhere, JPG is the pragmatic choice.

Does JPG keep transparency?

No. JPEG has no alpha channel, so any transparency in the AVIF is flattened onto a solid white background before encoding. If your AVIF has transparent regions you want to preserve — a logo, a cut-out, a UI asset — use the AVIF to PNG converter instead; PNG is lossless and keeps the alpha channel.

What happens to HDR or 10-bit AVIF images?

The browser's 2D canvas works in 8-bit sRGB, so a 10-bit or 12-bit HDR / wide-gamut AVIF is tone-mapped and clamped down to 8-bit sRGB during conversion. For ordinary photos this is invisible; for HDR masters destined for a color-managed pipeline it is a real limitation, and JPG (an 8-bit SDR format) couldn't carry that extra range anyway.

My AVIF shows an error and won't convert — what now?

The tool reads the file locally and tells you which problem you have. If the browser's AV1 decoder refuses it, we run a structural scan: a genuinely damaged container is flagged and linked to the AVIF repair page, while a structurally intact file that still won't decode usually just means an older browser — try the latest Chrome, Edge, Firefox or Safari. We never fabricate a converted file the browser couldn't actually decode.

Is anything uploaded?

No — 0 bytes leave your device. Open DevTools, switch to the Network tab, drop your AVIF, and watch: not a single request carries your file. Decoding and re-encoding both happen in the browser.

Related: keep transparency — AVIF to PNG · just look at it — AVIF viewer · broken file — repair AVIF