AVIF to JPG, in your browser
Drop an AVIF file. Get a JPG. Modern browsers decode AVIF natively; the conversion stays in your tab.
Loading...
Files stay on your device. Nothing uploads.
Why convert AVIF to JPG?
AVIF is the newest mainstream image format and arguably the best on paper. It uses the AV1 video codec's I-frame compression, which produces files around 50 percent smaller than JPG at the same visual quality. Browsers caught up fast: Chrome since 85, Firefox since 113, Safari since 16. CDNs serve AVIF aggressively.
The downside is a long tail of software that does not yet read AVIF. Stock photo sites, design tool import dialogs, several email clients, and many enterprise workflows still expect JPG. When a recipient says "the photo will not open", JPG is the safe answer.
How this converter works
Your browser already knows how to decode AVIF. We hand the file to createImageBitmap, which returns an ImageBitmap holding the decoded pixels. We draw the bitmap onto an OffscreenCanvas inside a Web Worker, fill the background with white (JPG cannot store alpha), then call convertToBlob with type "image/jpeg" and your chosen quality. The result is a JPG-encoded Blob.
No WebAssembly module is involved. The browser does the decoding; the browser does the encoding. The shipped JavaScript for this converter is tiny. Open DevTools, switch to Network, drop an AVIF: the only requests are for our static assets and the manifest JSON. Your file is never sent.
Browser support and graceful failure
If your browser shipped AVIF decode support, this just works. If not (older Firefox before 113, older Safari before 16, archaic Edge releases), createImageBitmap throws an error and we surface a clear message instead of silently failing. The fix is to update your browser; for offline batch work, ImageMagick or libheif on the desktop also handles AVIF.
You can check Can I Use for the live support matrix. As of 2026, AVIF decode coverage is over 95 percent of browser sessions worldwide.
Quality and size trade-off
Quality 1..100, default 90. At 90, the JPG is visually identical to the source for most photographic content. At 75, you save about 30 percent more space at the cost of mild artifacts in skies and skin tones. Below 60 the loss is visible.
Expect the JPG to be roughly 1.5-2x the AVIF file size at the same visual quality. AVIF's codec is genuinely better than JPG's; you cannot get the same size out of JPG without losing quality. If small files matter more than universal compatibility, keep the AVIF.
Metadata, color, and limits
Color profiles embedded in the AVIF (DCI-P3, Display P3, etc.) get flattened to sRGB by the browser's decoder. EXIF is not preserved through the canvas re-encode; the output JPG has no metadata. If you need both color management and metadata round-trip, run a desktop tool with libavif and exiftool.
A typical 12 MP AVIF (around 1-2 MB) converts in a fraction of a second on a modern laptop. Very large images may exhaust the browser's memory budget. The manifest exposes a rough memory hint so you know what to expect.
Frequently asked questions
- How much bigger will the JPG be?
- For typical photos, expect 1.5-2x the AVIF file size at quality 90. For graphics with flat colors, the ratio can be larger because JPG handles flat color poorly.
- Does this preserve metadata?
- No. Color profile, EXIF, IPTC, and ICC are stripped through the canvas re-encode. The output is sRGB JPG with no metadata. Run a desktop tool if metadata round-trip matters.
- Why does conversion fail in my older browser?
- Pre-2023 browsers do not decode AVIF. Update your browser, or use ImageMagick on the desktop for offline conversion.
- Will animated AVIF work?
- Only the first frame. Animated AVIF and AVIS sequences would convert to animated GIF or APNG, neither of which JPG supports. The first frame is exported as a static JPG.
- Does this work offline?
- After the first visit, yes. The Service Worker caches everything; you can convert AVIF files on a plane with the Wi-Fi off.