Why you keep running into AVIF files
AVIF has quietly become one of the most common image formats on the web. Sites serve it because it compresses well, and when you right-click and save a picture from Chrome or Firefox, you often get an .avif file whether you wanted one or not. The trouble starts afterward: Windows photo viewers on older builds won't open it, plenty of editing programs don't recognize it, and upload forms on government portals, job boards, and marketplaces frequently reject anything that isn't a JPG or PNG. Converting to JPG solves all of that in one step, because JPG is readable by effectively every device and application made in the last two decades.
How this converter works
Modern browsers can decode AVIF natively, and this tool uses that built-in capability rather than shipping a heavy decoder library. When you drop a file in, a Web Worker running on a separate thread decodes the AVIF and re-encodes it as a JPEG using the browser's own image pipeline. There is nothing to install and no server round trip, which is why even large photos convert in a second or two. You'll see the original and converted file sizes side by side before you download anything.
Batches, ZIPs, and what happens to your images
You can queue as many files as you like; three convert at a time, and you can grab each JPG individually or download the whole batch as a ZIP. Because every step runs inside your browser tab, your images never travel across the network — there is no upload, no processing queue, and no copy sitting on a server. That matters when the pictures you saved contain private conversations, documents, or work material. There are also no accounts, watermarks, or daily caps.