FineDocs

Convert AVIF to JPG

Convert AVIF images to JPG in your browser so they open in older software. Your browser already decodes AVIF, so no codec is downloaded at all.

Drop files here (up to 30)

or paste from the clipboard

Preview

Choose an image and the result appears here as you change the options.

Shows the framing and the colour that replaces transparency. Compression quality is not simulated.

Options
%

Set this higher than usual. AVIF holds gradients cleanly and JPEG needs headroom to keep them.

#ffffff

AVIF may carry transparency; JPEG cannot, so those pixels take this colour.

Results appear here. Nothing is uploaded.

    How it works

    No AVIF decoder is shipped, because your browser already contains one: AVIF decoding has been built into Chrome since version 85, Firefox since 93 and Safari since 16. The file goes to createImageBitmap, the pixels land on an OffscreenCanvas over your chosen background, and the browser's JPEG encoder writes the result. Zero kilobytes of wasm are transferred.

    Measured results

    These figures come from running this exact tool over a fixed set of sample files on every build, not from an estimate.

    Sample fileSettingsBeforeAfterChange
    logo-transparent.avifquality 883 KB14 KB+316%
    photo-gradient.avifquality 8815 KB103 KB+573%

    Benchmark run 2026-08-01.

    What to watch out for

    Wide-gamut and HDR images are flattened to ordinary sRGB

    AVIF can store ten or twelve bits per channel and describe colours outside the sRGB range. The canvas works in eight-bit sRGB, so a photograph mastered in HDR arrives tone-mapped, with highlights compressed and saturated colours pulled inward. For screen use this is usually invisible; for grading work it is not.

    Expect the JPEG to be considerably larger

    AVIF descends from the AV1 video codec and is far denser than JPEG at matching quality, often by half. Converting therefore inflates the file, and the reason to do it is that something downstream cannot read AVIF, never that you wanted a smaller image.

    A very old browser will refuse the file, and say so honestly

    If your browser predates AVIF support the decode fails, and this tool reports that the browser is the limitation rather than blaming your file. The image itself is almost certainly fine; opening it in a current browser is the fix.

    Limits

    Files up to about 50 MB work reliably. Beyond that, the ceiling is your device's memory rather than any rule we impose — the work happens on your own machine. Tested in Chrome 140, Firefox 143, Safari 18.

    Why AVIF files turn up and then cause trouble

    AVIF is a still image wrapped in the machinery of the AV1 video codec, and it is remarkably good at its job — frequently half the size of a comparable JPEG. Sites serving images at scale have adopted it quickly, which is how one ends up in your downloads folder.

    The friction begins outside the browser. Support in desktop applications, print services, older phones and business software lags years behind. A file that displays perfectly on a web page can be rejected by the very next thing you try to open it with, and JPEG remains the format that everything accepts.

    What no codec download actually means

    Most converters for a format this new have to fetch a WebAssembly decoder, typically a megabyte or more, before they can do anything. This one does not, because AVIF decoding is already part of your browser.

    The practical difference is immediate: the conversion starts the moment you drop a file, there is nothing to wait for on a slow connection, and the tool keeps working with the network switched off once the page itself is cached.

    Choosing a quality setting

    AVIF is unusually good at smooth gradients — skies, studio backdrops, soft shadows — which is exactly where JPEG is weakest. Converting a clean AVIF sky at quality 75 can produce visible banding that was not there before.

    Starting at 88 rather than the more usual 85 gives JPEG the headroom to keep those transitions smooth. If the image is mostly detailed texture you can go lower and save space; if it has large soft areas, go higher.

    Since everything runs locally, comparing two settings is a matter of seconds and costs nothing. No upload, no queue, no watermark.

    Your files never leave your browser. Last updated 2026-08-01.