AVIF to JPG Converter

An AVIF to JPG converter decodes an AVIF image and re-encodes the same picture as a JPEG. AVIF is what a lot of sites now serve, so the photo you saved from a web page lands in your downloads folder as .avif, and then the thing you wanted to use it in will not open it. Older Windows builds, Office 2019, several print and photo-kiosk uploaders and a long tail of desktop software still expect JPG. JPG is the fallback every one of them reads, which is why this conversion exists.

The conversion is a genuine re-encode rather than a rename. The file is decoded to pixels and written again with the JPEG encoder, so the extension and the contents agree afterwards. Decoding uses the browser's own AVIF decoder, so a current browser is needed: Chrome, Edge, Firefox, or Safari 16 and later. If the browser cannot open the file, the page says so on that row instead of handing you a download that no viewer can read.

Here is what that looks like in practice. A site gives you hero-shot.avif at 1,920 x 1,280 pixels. Drop it here with Quality left at 90 and it converts straight away. You get hero-shot.jpg at the same 1,920 x 1,280 pixels, usually several times larger than the AVIF, because JPEG is an older codec that needs more bytes for the same picture. Pull Quality down to 70 and the file is converted again from the AVIF and comes out much smaller, but the detail that setting throws away is not in the JPG you download.

Two things change on the way across. AVIF can store transparency and JPG cannot, so transparent areas are filled with white and the page tells you it did that. The image is redrawn through a canvas, so EXIF, GPS coordinates and color profiles are dropped, which is handy if you are sharing a photo and less handy if you needed the camera data. Pixel dimensions are left alone. Images above 100 megapixels are refused with a message, empty files are refused, and there is no byte-size cap. It is free, no signup, with a daily usage limit.

• AVIF files are decoded and re-encoded client-side, in this tab, by the browser's own decoder and the Canvas API. No WebAssembly codec is downloaded and no image is uploaded.
• The daily usage check sends a file count, their combined size in bytes and the output format. File names and pixel data are never sent, and no copy of an image is stored on a server.
• EXIF fields, GPS coordinates and color profiles are left behind, because the JPG is built from decoded pixels alone. That strips the location from a photo before you share it.
• The row thumbnails and the Before and After preview are drawn from local object URLs, so viewing them does not send the image anywhere either.
• Converted JPGs live in the tab's memory until you remove them, press Clear All or close the page.