How to convert WebP to JPG

WebP became the default format for a lot of the web because it is usually smaller than JPG at the same visual quality. The trade-off is compatibility: plenty of desktop software, older phones and print workflows still expect JPG or PNG. Converting WebP to JPG solves that, and the conversion is simpler than it looks once you know what the two formats can and cannot store.

What changes when WebP becomes JPG

Two differences matter in practice. The first is transparency: WebP can store an alpha channel and JPG cannot. If your WebP has transparent areas, those pixels have to become something, and the only sensible choice is a solid colour. This tool uses white, and says so in the result. If you need the transparency kept, convert to PNG instead.

The second is that both formats are lossy by default, so the conversion re-encodes the image. JPG discards a little more detail each time it is saved, so converting a WebP that was itself made from a JPG means two generations of loss. The result will still look fine at normal viewing sizes; it just will not be identical to the original.

Choosing a quality setting

The quality slider controls how much detail JPG keeps. A few rules of thumb, from experience rather than measurement on your particular file:

• 90 to 95 for images you will edit again or print. Files stay large.
• 80 to 90 is the usual sweet spot for photographs on the web. Most people cannot see the difference and the file is much smaller than lossless.
• 60 to 75 when the image is decorative or the file size really matters. Flat areas start to show faint mottling and sharp edges pick up a slight halo.
• Below 50 is rarely worth it. Blocky artefacts around text and edges become obvious.

Where the conversion runs

Current browsers can decode WebP natively through the canvas element, so this conversion runs entirely on your device and the file is never uploaded. The result panel labels every file with where it was processed, so you can confirm that rather than take it on trust. If a browser cannot decode WebP, the tool sends the file to the server instead and the label changes to say so.

When not to convert

If the WebP is destined for a website, leave it as WebP. Converting to JPG will make the file larger in most cases and lose a little quality for no benefit. Convert when the destination software cannot read WebP, which is the problem this conversion actually solves.