Convert WEBP to JPG

You saved an image from a website and it landed as .webp, and now Word, an upload form or an older photo editor refuses to touch it. Converting it to JPG fixes that in a second, right here in your browser.

Why you keep ending up with WEBP files

WEBP is a modern image format made by Google. It compresses better than JPG at the same visible quality, so a great many websites now serve their images as WEBP to load faster. When you right-click and save one of those images, you get a .webp file — even though you were expecting a normal photo.

Every current browser displays WEBP without complaint. The trouble starts everywhere else: desktop software, upload forms, print shops, e-mail clients, presentation tools and anything more than a few years old often do not recognise it. Converting to JPG puts the image back into the format that genuinely opens everywhere.

How to convert

1. Drop your WEBP files onto the converter, or click to browse for them.
2. Leave the output set to JPG.
3. Set the quality — 90% is a safe default that keeps the image looking like the original.
4. Download individually or use Download all for the batch.

What to expect from the result

The file may get bigger. This surprises people. WEBP is the more efficient format, so converting to JPG usually costs you size — sometimes 20–40% more. You are trading file size for compatibility, which is normally exactly the trade you want.

Transparency is filled with white. WEBP supports transparent backgrounds and JPG does not. If your WEBP has transparency and you need to keep it, convert it to PNG instead — the same converter does that; just pick PNG as the output.

Animated WEBP becomes a single frame. A WEBP can hold an animation, much like a GIF. JPG cannot, so you will get the first frame. If you needed the animation itself, converting is not the right tool.

Quality is not restored. The WEBP was already compressed; converting re-encodes what is there. It cannot recover detail the original encoder discarded. Keep the quality slider high so you do not stack a second round of loss on top.

Can I stop downloading WEBP in the first place?

Mostly, no — the site decides what format it serves, not you. A few practical workarounds:

• Screenshot it. Fastest route for a one-off. You lose some quality and gain whatever else was on screen, but it is instant and always works.
• Check for a full-size version. Many sites serve WEBP thumbnails but keep an original JPG behind the link.
• Just convert it. For a batch, this is quicker than fighting the website.

Transparency turns white, and an animation turns into one frame

Two things happen in this conversion that surprise people, and both are unavoidable properties of JPG rather than quirks:

• Transparent areas become white. JPG has no transparency channel at all, so something has to go behind the image — and white is deliberately chosen here, because the alternative default is black, which turns a dark logo into a black rectangle. If you saved a logo or an icon from a website and it had a clear background, the JPG will have it sitting on a white square. When that matters, convert to PNG instead: it keeps the transparency exactly as it was.
• An animated WEBP becomes a still. Animated WEBP is used a lot for the small looping clips that replaced GIFs. A JPG holds one image, so you get the first frame. If you wanted the animation, JPG is the wrong destination entirely.

Everything else comes across as you'd expect. Metadata does not: the file is decoded and re-encoded, so any camera, date or location data in the WEBP is not in the JPG — usually welcome, occasionally worth knowing.

You're already at least two generations from the original

This is the part worth understanding, because it changes how you should set the quality slider. A WEBP you saved from a website almost never started life as a WEBP. Someone uploaded a JPG or a PNG, and the site's image pipeline re-encoded it to WEBP at whatever quality it was configured for, probably also resizing it to fit the layout. So the file on your disk is already a second-generation copy — and converting it to JPG makes a third.

Every lossy pass throws away a little detail permanently, and none of it comes back. What follows from that:

• Set the quality high — 90 or above — if this is a file you'll keep. A small saving in size isn't worth adding another visible generation of loss to an image that's already been through the mill.
• Don't convert back and forth. WEBP to JPG to WEBP to JPG degrades noticeably. Convert once, to the format you actually need.
• Look for the original before you settle. Sites usually keep several sizes of the same image, and the one your browser downloaded is the one that fit your screen — not necessarily the biggest. Opening the image in its own tab, or checking the page source for a larger variant, often gets you a sharper file than any amount of careful converting will.
• If it's your own image, go back to your own source file. The version a website served back to you is always a worse copy than the one on your hard disk.

Common questions

Is WEBP worse than JPG? No — technically it is better, at a smaller size. Its only real weakness is that support outside web browsers is still patchy.

Can I go the other way? Yes. The same converter turns JPG and PNG into WEBP, which is worth doing for images on a website you run.

Is there a size or count limit? No cap, no watermark, no account. The only ceiling is your own device's memory on very large batches.

Questions

The other conversions

• HEIC and HEIF to JPG, PNG or WEBP — for iPhone photos
• PNG to JPG — the size-saving one
• WEBP to JPG — for files downloaded from websites
• JPG to PNG — when a tool insists on PNG
• PNG to WEBP — for images on your own site