Why you keep ending up with WebP files
Almost nobody sets out to create a WebP. You right-click an image on a website, choose save, and get a file with an extension you have never used — and then something refuses to open it.
Where the file came from
Websites serve WebP because it is smaller than JPEG at the same quality, so pages load faster. Your browser saves whatever the site sent, and what the site sent was a .webp.
The file is not corrupt and you did nothing wrong. It is simply newer than some of the software you now need to hand it to.
What refuses to open it
Every current browser reads WebP. So do Photoshop 23 and later, Windows 11’s Photos app, and macOS Preview.
The problems are elsewhere: older Office documents, some content management systems, print shops, and plenty of upload forms that only ever added JPG and PNG to their allow-list. That mismatch is the whole reason to convert WebP to JPG.
What WebP actually is
WebP is a Google image format from 2010 that rolled several jobs into one container.
Lossy, lossless and animated, all in one extension
A .webp can be a lossy photograph, a lossless graphic with transparency, or a full animation. The extension tells you none of that, which is why two WebP files can behave completely differently in the same tool.
This matters for conversion, because two of those three things do not fit inside a JPG at all.
Converting WebP to JPG costs size, not saves it
This is the part every other converter leaves out, so here is the measurement.
The numbers
The same 1600-pixel image, downloaded as a 282 KB WebP, came back as a 340 KB JPG at quality 85 — 121% of what we started with. Even at quality 80 it was still larger, at 295 KB. At quality 95 it nearly doubled.
WebP simply encodes more efficiently than JPEG. There is no quality setting at which converting WebP to JPG produces a smaller file for the same picture.
So convert for the right reason
Do it because something you need to use will not accept a WebP. Do not do it to save space or tidy up a folder, because it achieves the opposite.
Quality is lost twice, not once
Why re-encoding a lossy file costs more
The WebP you downloaded was already compressed by the website that served it — detail was discarded before you ever saw the file. Encoding that to JPG throws away a second helping, and this time there is no original to fall back on.
At quality 85 the second loss is hard to spot on a photograph. On text, flat colour or a screenshot it is much more visible, because JPEG smooths inside 8×8 blocks and those subjects have hard edges.
When to keep the WebP instead
If the file is only going somewhere that reads WebP — a modern browser, a current design tool, your own archive — keep it. It is smaller and it has lost less.
Convert a copy when a specific destination demands JPG, and keep the WebP as the better version.
Animated WebP files
You get the first frame
A JPG holds exactly one image. There is nowhere for frames two onward to go.
Most converters simply hand back a still and say nothing, which looks like a bug. This tool reads the header before converting and flags animated files in the queue, so you find out before you download rather than afterwards.
If you need every frame
Your original is untouched and still holds the whole animation. To keep the motion, convert to GIF or MP4 with a tool built for that, rather than to a format that structurally cannot store it.
What happens to transparency
WebP can store an alpha channel. JPG cannot. Something solid has to go behind the transparent pixels, and the choice is not always white.
Choosing a background colour
A logo with a soft shadow gets a grey halo on white. Artwork drawn for a dark interface arrives in a bright box. Pick white, black, or any colour you like — and files carrying transparency are flagged before you convert, so you know when the decision matters.
If your source is a PNG rather than a WebP, our PNG to JPG converter works the same way.
And if the WebP has a transparent background you want to keep, WebP to PNG avoids the question entirely — PNG has an alpha channel, so nothing has to be painted in.
How to convert WebP to JPG, step by step
The tool at the top of this page does the whole job, but it is worth knowing what each step is for.
1. Add the files
Drag them in, click to browse, or paste from the clipboard with Ctrl+V. Paste is the quickest route when you have just copied an image out of a browser tab.
Add as many as you like. Everything is read locally, so a large batch costs you nothing but a moment of your own processor.
2. Read what the queue tells you
Each file is checked from its header before anything happens. Animated files are called out, and so are files carrying transparency.
This is the step other converters skip, and it is the one that prevents the two surprises people actually hit when they convert WebP to JPG: a still image where an animation used to be, and a white box behind a logo.
3. Set the quality and the background
Quality 85 is the default and suits nearly everything. Raise it for gradients and skin tones; there is little reason to lower it here, because the file is going to grow anyway.
Pick the background colour if any file needs one. It only affects transparent areas.
4. Download
Take each JPG individually, or the whole batch as one ZIP. Your original WebP files are never modified.
When people need this conversion
Knowing which situation you are in tells you what settings to use — and occasionally that you should not convert WebP to JPG at all.
An upload form that rejects the file
The most common case by far. Job portals, marketplaces, government forms and older content systems often accept only JPG and PNG, and a WebP is refused with an unhelpful error.
Quality 85 is right here. Compatibility is the goal, and the file size does not matter much when the destination is a form.
Handing an image to someone else
Email attachments, printers, colleagues on older software. JPG is the format nothing has ever refused, which is exactly why it is worth the extra bytes.
Putting the image into a document
Word, PowerPoint, InDesign and similar tools vary in whether they accept WebP, and older versions generally do not. Converting first avoids finding out mid-deadline.
When you should not convert at all
If the destination reads WebP — a modern website, a current design tool, your own storage — leave it alone. Converting a WebP to JPG there costs you quality and adds bytes for no benefit whatsoever.
WebP vs JPG at a glance
| WebP | JPG / JPEG | |
|---|---|---|
| File size | Smaller | Larger for the same quality |
| Transparency | Yes | No |
| Animation | Yes | No |
| Opened by older software | Often not | Essentially always |
| Upload forms accept it | Sometimes | Almost always |
| Best use | Websites, storage | Compatibility, handing files to other people |
Going the other way is also worth knowing about: HEIC to WebP turns iPhone photos into the smaller format for a website, and HEIC to JPG does the compatible one.
Before you send the file on
A converted JPG can still carry the metadata that came with it — camera, timestamps, sometimes GPS coordinates. If the image is going to somebody else, it is worth checking.
You can remove EXIF data without re-encoding the picture at all, which matters here: this file has already been through two lossy encoders and does not need a third.
Privacy: why this runs in your browser
The engine is WebAssembly executing on your own machine. Your files are never uploaded, never queued on a server, and never retained “for an hour” the way several competing converters state in their own terms.
For an image you saved off a public website that may not matter. For a screenshot of something private, it matters a lot — and a tool should not quietly behave differently depending on which one you happened to drop in.
It also makes the batch honest
Converting fifty WebP files costs us nothing, because your own machine is doing the work. There is no bandwidth bill, so there is no quota to invent and no premium tier to sell you.
The one trade is that the first conversion waits a moment while the engine loads. After that it is entirely local, and it keeps working even if your connection drops mid-batch.
No retention, because there is nothing to retain
Several converters for this format state in their own terms that uploads are deleted after an hour. That is a reasonable policy, and it is still a policy — it describes what happens to a copy of your file that they hold.
Here there is no copy. Convert WebP to JPG, close the tab, and the only files involved are the ones on your disk.