WebP to JPG: When the Downgrade Is the Right Call

You saved an image off a website and it came down as .webp. Now the client's designer, who is still on a copy of Photoshop from 2014, can't open it. Or the print shop's pre-flight check spits it back. Or a marketplace listing tool says the file type isn't allowed.

Nothing is wrong with the WebP. It's smaller and better looking, byte for byte, than the JPG you're about to make from it. You're going backwards on purpose because something further down the chain won't cooperate, and that's a perfectly reasonable thing to do.

First, check whether you actually need to

WebP support crept up quietly and a lot of "it won't accept WebP" beliefs are years out of date. WordPress has accepted WebP uploads since version 5.8. Photoshop reads and writes it natively since 2022. Microsoft Office, Windows Photos, macOS Preview, and every current browser all handle it.

What still refuses it, in practice: older versions of Photoshop, Illustrator, and InDesign, some print workflows and RIP software, a number of ecommerce and marketplace uploaders, plenty of enterprise CMS platforms that were built a decade ago, and various desktop tools nobody has updated since. Also older Android devices, though that's rare now.

So try uploading the WebP first. Half the time it just works and you've saved yourself a conversion.

How to convert WebP to JPG

1. Open the Image Converter.
2. Drop your .webp files in, as many as you want.
3. Set the output format to JPG.
4. Set quality to 90 or higher. This is not the place to economise, and the next section explains why.
5. Convert and download, individually or as a ZIP.

Two things this conversion costs you

Transparency, if the WebP had any

WebP supports transparent pixels. JPG does not, at all. A product cutout with a see-through background becomes a product on a solid rectangle. If your WebP has transparency and you still need something universally accepted, convert it to PNG instead. PNG keeps the transparency and every tool on earth reads PNG.

A second round of lossy compression

Most WebP files you'll encounter are lossy, which means detail was already thrown away once. Converting to JPG decodes what's left and compresses it again with a different method that throws away different things. That's generation loss, and it stacks.

One pass at high quality is nearly invisible. The damage shows up when people convert at quality 70, then open the result in an editor, save it again, and mail it to someone who saves it again. Set the slider high, do it once, and stop.

Worth knowing: if the WebP was saved in lossless mode, which is common for screenshots and exported graphics, converting to JPG is a much bigger step down than usual. A pristine lossless image is about to become an approximation. PNG is the better target for those.

Your JPG might come out bigger, and that's normal

People are often surprised when a 180 KB WebP turns into a 340 KB JPG. Nothing went wrong. WebP is a more efficient format, full stop, typically producing files around 25 to 35 percent smaller than JPG at comparable quality. Going the other direction, you pay that difference back. You're buying compatibility with bytes.

Don't convert your website's images

If someone tells you to switch your site's WebP images to JPG "for compatibility", push back. Every browser in current use displays WebP, and you'd be making every page heavier for no one's benefit. If you're worried about the tiny remainder, the fix is a fallback in the HTML rather than a downgrade for everybody. Our WebP vs AVIF vs JPEG comparison covers what each format is actually good for.

Convert to JPG when a specific program, printer, or portal in front of you refuses the file. Not as a general policy.