Convert AVIF to JPG — no upload, no signup, no tracking
AVIF compresses better than JPG, but support is still patchy in legacy CMSes, email clients, and older software. This converter re-encodes any AVIF to a standard JPG that opens everywhere — entirely inside your browser.
Convert to JPG →Why convert AVIF to JPG?
AVIF is the newest mainstream image format and compresses 30-50% better than JPG at the same visual quality. That's why modern browsers, CDNs, and static-site generators have adopted it aggressively. But every tool that hasn't caught up — some WordPress themes, older email clients, Microsoft Office, legacy desktop apps, a surprising number of print-order kiosks — still only accepts JPG. Converting AVIF to JPG bridges the modern web back into those older workflows.
What you lose and what you gain
Both AVIF and JPG are lossy codecs, so each re-encode discards a small amount of detail. Converting AVIF → JPG at quality 90 produces a JPG that is visually indistinguishable from the AVIF source in blind tests, at the cost of roughly 2-3x the file size. You gain universal compatibility. You do not recover any detail the original photograph lost during its first encode — re-encoding never improves an image, it only preserves more or less of it.
How to convert AVIF to JPG
The whole process runs locally. No uploads, no server, no account. Works offline once the page has loaded once:
- Click "Convert to JPG →" at the top of this page, or drag your AVIF file onto the drop zone on the homepage.
- ConvertMyPic decodes the AVIF using libaom (the reference AVIF decoder, compiled to WebAssembly). You will see a preview appear within a second for typical phone-photo sizes.
- The file is re-encoded to JPG using mozJPEG, the Mozilla-maintained JPEG encoder that produces 5-10% smaller files than the libjpeg-turbo default at the same visual quality.
- Click the download button. The JPG saves straight to your Downloads folder. The filename matches the original with the extension swapped — photo.avif becomes photo.jpg.
- Want a different quality? Open /convert directly and you can tune the quality slider (50-100), optionally strip EXIF, and pick baseline vs. progressive encoding.
File size comparison: AVIF vs JPG at matched quality
Numbers from a real 4032x3024 iPhone 15 Pro photo (coastal landscape, 12.2 MP). AVIF source was emitted at quality 75, then re-encoded to JPG at each quality level using mozJPEG.
| Format | Quality | File size | Visual notes |
|---|---|---|---|
| AVIF (source) | 75 | 612 KB | Original, no visible artifacts |
| JPG | 95 | 2.41 MB | Visually identical to AVIF |
| JPG | 90 | 1.72 MB | Best quality/size balance for web |
| JPG | 75 | 694 KB | Faint banding in sky gradients |
| JPG | 50 | 287 KB | Visible blockiness; not recommended |
When to convert, and when to stay on AVIF
Convert to JPG when the destination tool cannot open AVIF — older CMSes, most print kiosks, WhatsApp on Android 10 and earlier, many corporate email firewalls that sniff MIME types, and Slack's desktop preview on Windows. Stay on AVIF when you control the destination: your own website, a CDN that re-encodes on delivery, modern photo-management apps (Apple Photos, Google Photos, Lightroom), and any tool you know supports it. A good rule of thumb: if the recipient is a system, keep AVIF. If the recipient is a human who will download and open the file themselves, JPG still has the widest compatibility in 2026.
Under the hood: which codecs are used
ConvertMyPic is a fork of Google's Squoosh. AVIF decoding uses libaom compiled to WebAssembly via Emscripten — the same decoder Chrome and Firefox ship. JPG encoding uses mozJPEG, which is a drop-in replacement for libjpeg-turbo that applies trellis quantization, smarter quantization tables, and progressive scan optimization to squeeze out 5-10% additional size at the same SSIM. Both run in a Web Worker so the UI stays responsive. Source: the libaom fork we use is at github.com/AOMediaCodec/libavif; mozJPEG is at github.com/mozilla/mozjpeg.
FAQ
Do my files get uploaded anywhere?
No. The entire conversion runs in your browser using WebAssembly. Open your browser's Network tab during a conversion — you will see zero outbound requests beyond the initial page load. We do not operate a server, so there is nowhere to upload to.
What is the maximum file size?
Browser memory is the only limit. 200MP+ photos (over 50MB AVIFs) work on desktop Chrome with 16GB of RAM. On older phones, expect stability up to around 40MP. If a file is too large, you'll see a clear error rather than a crash.
Will the JPG be as sharp as the AVIF?
At JPG quality 90+, blind A/B testing puts the difference at the single-pixel level. Most people cannot tell. At quality 75, skies and skin tones show JPG-typical banding that AVIF did not have. Use 90 as the default unless file size is critical.
Does the tool preserve EXIF metadata (GPS, camera model, etc)?
Yes by default. If you are sharing the JPG publicly and want to strip location data, the advanced options on /convert include an EXIF-strip toggle. Privacy-sensitive workflows should flip that on.
Does this work offline?
Once the page loads once, the service worker caches the app and WASM decoders. Subsequent visits work with the network disconnected. That's why it's installable as a PWA on desktop and mobile.
Why is this free?
Because we operate no servers. The Emscripten WASM modules weigh a few MB total, served once from a CDN, and all the compute happens on your CPU. Hosting cost is essentially zero, so there is nothing to charge for.
Can I convert multiple AVIFs at once?
The current flow is one file at a time. Batch conversion is on the roadmap. For 10+ files today, a faster approach is to open /convert in multiple browser tabs and process them in parallel.
Does AVIF 12-bit convert correctly to JPG?
Yes. libaom decodes the full 10/12-bit AVIF to a 10/12-bit internal buffer, then mozJPEG tone-maps to standard 8-bit JPG on encode. HDR content gets compressed into SDR; if you need HDR-preserving conversion, stay on AVIF or use a professional tool like ImageMagick.
Is the output a baseline or progressive JPG?
Progressive by default — progressive JPGs render incrementally as they download, which is what you want for web use. /convert advanced options expose a toggle if you need baseline (required by some very old software).
How does this compare to iLoveIMG or CloudConvert?
Both upload your files to their servers. ConvertMyPic does not have a server — your AVIF never leaves the device. Speed is comparable after the first page load. Privacy is the main differentiator.