How to Convert Images Between JPG, PNG, WebP and AVIF

Converting an image from one format to another sounds like it should be trivial, and for JPG, PNG and WebP it is - a browser can decode and re-encode any of them natively. AVIF is the one exception worth knowing about before you start.

Step 1 - drop in your files

Image convert accepts JPG, PNG, WebP, AVIF, GIF and BMP as input, up to 20 files at once, each up to 100MB. Nothing is uploaded - conversion happens on your device.

Step 2 - pick the target format

Choose JPG, PNG, WebP or AVIF as the output. For JPG, PNG and WebP, this uses the browser's own built-in canvas, the same rendering engine that draws every image on every page you visit - no extra download, no library. AVIF is different: no browser has a built-in way to encode AVIF yet, so the tool loads a small WebAssembly codec the first time you pick it, vendored on this site rather than fetched from anywhere else. It only loads when you actually choose AVIF as the target, not on page load.

That vendoring choice is deliberate rather than incidental. A number of browser-based tools load their codecs from a third-party CDN at runtime, which means every use of that feature quietly tells the CDN operator your IP address and that you're using that tool. Keeping the AVIF codec on this site's own server means encoding to AVIF makes exactly the same number of outside requests as encoding to JPG, PNG or WebP: zero.

Step 3 - set the quality, for lossy targets

Converting to a lossy format (JPG, WebP, AVIF) offers a quality slider, same idea as the compressor: higher keeps more detail at a larger size, lower shrinks the file at some cost to fine detail. Converting to PNG is lossless, so there's no quality setting to make - the picture data is preserved exactly.

If a browser can't run the AVIF codec for some reason - genuinely rare on a current, up-to-date browser, but possible on an unusual or very old one - the tool tells you plainly that AVIF needs a modern browser and suggests picking a different target format instead, rather than leaving you staring indefinitely at a conversion that silently never actually finishes on its own.

This is a deliberate design choice, not an oversight: a tool that fails should always say so clearly, in plain language, rather than leaving a user to guess whether something is broken or just slow.

The one warning: transparency doesn't survive going to JPG

JPG has no concept of transparency at all. If your source image has a transparent background (a PNG logo, a cutout from Background remover) and you convert it to JPG, the transparent areas get filled in with a solid colour - the tool offers a white or custom colour matte for exactly this, so the result is deliberate rather than a surprise. If you need to keep transparency, convert to PNG or WebP instead, both of which support it fully.

Step 4 - download

One file downloads directly; a batch downloads as a zip. Each converted file keeps its original name with the new extension, so a batch conversion doesn't leave you guessing which output matches which input.

Files convert one after another rather than all at once, each with its own row and its own progress, so a batch that includes both a fast JPG-to-PNG conversion and a slower AVIF encode doesn't hide which files are actually taking the time. If one file in a large batch fails - an unsupported or corrupted source, say - it's flagged with a clear message and skipped, and the rest of the batch still completes rather than the whole job stopping over one bad file.

Nothing here needs a second visit to check

Every step above happens in the same browser tab, in the time it takes the conversion to run - there's no email confirmation to wait for, no "your file will be ready shortly" holding page, and no account to create first. Drop a file in, and the result is either downloading a few seconds later or you already know exactly why not, with a specific, readable reason rather than a spinner that never resolves.

Converting a mixed batch in one go

You don't need every file in a batch to start in the same format. Drop in a folder that's a mix of JPGs, PNGs and even the odd GIF or BMP - up to 20 files, each up to 100MB - and pick a single target format for all of them at once. This is useful when standardising an existing image folder to one format going forward, rather than sorting files by their current type before converting each group separately.

What happens to an animated GIF

Worth stating plainly rather than discovering it after the fact: this tool converts still images, and an animated GIF has no still-image equivalent that preserves the animation. Converting one produces a single frame as the output - the first frame, not a summary or a highlight of the whole animation. If keeping the motion matters, this isn't the right tool for that file; if you specifically wanted one static frame from a GIF (a thumbnail, a preview image), this does exactly that.