Free, in your browser — your AVIF never leaves you. Transparent areas become white.
or drop the image here
Converting…
RoundCut converts AVIF to JPG in your browser using the native AVIF decoder and JPG encoder. The file is never uploaded. Transparent areas flatten to white, since JPG has no alpha. The JPG output is usually larger than the AVIF, because AVIF compresses more efficiently — the trade-off is compatibility with software and platforms that cannot open AVIF.
Drop an AVIF file on the upload area, or click to pick one. The conversion starts the moment the file lands — there is no "Convert" button to chase. Your browser decodes the AVIF natively, then re-encodes the pixels as JPG using the platform's image engine. When the result is ready, the stats line shows the input and output size, and the Download button saves the JPG to your device. The whole round trip is typically under a second for photos under 4 megapixels.
AVIF supports a full alpha channel — pixels can be transparent or semi-transparent. JPG cannot. Every transparent or partially transparent pixel in your AVIF must be replaced by a solid color before the JPG is written, and the conversion flattens those pixels to white. If you need a different background color, open the AVIF in an editor and paint the color onto the transparent regions before converting. If you need to keep the transparency, JPG is the wrong destination — WebP or PNG preserve alpha.
AVIF is newer and more efficient — at the same visual quality it is typically 30 to 50 percent smaller than JPG. Keep AVIF when file size matters and the audience is on modern browsers and a recent OS. Switch to JPG when you need the file to work everywhere: Instagram and WhatsApp uploads, Windows photo viewers without the AVIF codec installed, older versions of Photoshop, print services, email attachments to coworkers on legacy software. JPG is the universal format; AVIF is the optimised one.
JPG is lossy and AVIF is lossy, so the conversion is a lossy-to-lossy chain — some compression artifacts can compound. The JPG encoder runs at a near-lossless setting tuned for photographs, measured at 43.66 dB PSNR on our test inputs, which is visually indistinguishable from the source on the naked eye. The output file will usually be larger than the AVIF input, because AVIF compresses more efficiently. That size increase is the cost of compatibility, not a bug. There is no quality slider.
The whole pipeline runs in the browser's native image engine plus its native AVIF decoder. Nothing is uploaded, nothing is logged, nothing is queued on a server. If you open DevTools and watch the Network panel while you convert, you will see zero outbound image requests during the conversion. The same client-side code path runs on every supported browser — there is no server fallback, no telemetry on your file, and no third-party processing. The AVIF stays on your device from the moment you pick it.
AVIF is not universally supported yet. Instagram and WhatsApp uploads are inconsistent, Windows without the AVIF codec extension cannot preview the file in Explorer, older versions of Photoshop and most print services do not accept it. JPG works everywhere — every browser, every operating system, every social platform, every editor. Converting trades AVIF's superior compression for guaranteed compatibility wherever you need to send or open the file.
Yes. JPG is lossy, AVIF is lossy, so the chain is lossy-to-lossy and some compression artifacts can compound. The JPG encoder runs at a near-lossless setting (measured at 43.66 dB PSNR) that is visually indistinguishable from the source for photographs. Graphics with sharp edges or fine text may show subtle JPG artifacts. The output file will usually be larger than the AVIF, because AVIF compresses more efficiently — converting back inflates the file.
AVIF supports transparency through a full alpha channel; JPG does not. The conversion flattens transparent pixels to white. If you need a non-white background, paint the color onto the AVIF in an editor before converting. If you need to keep the transparency entirely, JPG is the wrong destination — WebP and PNG both preserve alpha and are widely supported.
No. Only the first frame is converted to JPG. JPG itself has no animation support, and the converter does not iterate through AVIF animation frames. If your AVIF is an animated sequence, every frame after the first is dropped. For animated output you need a video format or animated WebP through a dedicated tool — that is not what this converter does.
Your file never leaves your browser. The conversion runs entirely on your device — the browser decodes the AVIF, the canvas re-encodes the JPG, and the download saves to disk. No upload, no server, no telemetry on your image. You can verify it with DevTools open: there are zero outbound image requests during the conversion. The same code path runs in every supported browser.
Not yet — the current version converts one file at a time. Batch conversion is planned for a later release. If you need to convert several AVIF files now, drop them through the tool one after the other; each conversion runs in milliseconds for typical photos, so it is fast even without batch.