How to convert WebP to JPG

WebP is great for websites and a nuisance almost everywhere else. You’ve probably saved an image from a browser, gone to upload it to a CMS or attach it to an email, and been told the format isn’t supported. The fix is a quick conversion to JPG. Here’s when to do it, what quality setting to pick, and how to handle the transparency quirk that catches people out.

Why WebP exists

Google built WebP to shrink web images. At comparable quality, a WebP file is typically 25-35% smaller than the equivalent JPG, which adds up when a page ships 20 images. Chrome, Firefox, Safari, and Edge all handle WebP natively, so most websites serve WebP and save on bandwidth. That’s the whole story on the web.

Why JPG is still the safe default

The moment an image leaves the browser context, WebP support gets patchy. Specific places it breaks:

• Older CMSs (some WordPress installs without the right plugin, legacy enterprise tools) — the upload fails or the image won’t render.
• Print shops — almost none of them accept WebP. JPG or TIFF, period.
• Some email clients — Outlook in particular. Ship a WebP as an inline image and half your recipients see a broken icon.
• iMessage photo previews — WebPs don’t generate a preview reliably; JPGs do.
• Old slideshow and document software — PowerPoint, older Keynote, most Word versions before 2021.

If you’re not sure where an image is going, convert to JPG. You’ll add 100KB and avoid a dozen possible failures.

Quality slider guidance

JPG quality is on a 0-100 scale. For photographs, 92 is the sweet spot: essentially indistinguishable from the source, reasonable file size. Drop to 85 for general web use, 75 for thumbnails. For screenshots or graphics with text (even though JPG isn’t really the right format for those), stay at 95+ or the text edges go fuzzy.

Don’t crank quality to 100 thinking it’s best. 100 disables most JPG compression and bloats the file with barely any visual improvement over 92. 92 is the practical max.

The transparency problem

WebP supports transparency (alpha channel). JPG does not. When you convert a WebP that has transparent areas to JPG, those transparent pixels need to become something — and if the converter silently picks black, you end up with a logo on a black square where you expected a clean cutout.

The standard fix: flatten to white. Set the background to white before export, so transparent areas become white pixels. That matches most document and email backgrounds, so the image looks clean. If you know the final background (a specific brand color, a dark theme), flatten to that color instead.

If you actually need transparency preserved, convert to PNG instead of JPG. Bigger file, but the alpha channel survives.

Batch conversion

Converting one file at a time is fine for a one-off. If you just downloaded 40 WebP images from a photo dump, drag them all into a batch converter at once. Our WebP to JPG converter handles batches in the browser, and the more general image format converter handles any format-to-format combination if you also have a few PNGs or HEICs mixed in.

One gotcha on filenames

If you’re converting images destined for a CMS or a file share, make sure the filename extension actually changes from .webp to .jpg. Some tools keep the original name, which leaves you with photo.webp that’s technically a JPG — some systems infer format from the extension and will reject it. Thirty seconds of rename saves the support ticket.