Convert WebP to JPG
The format your browser saved by default, in the format everything else knows how to open.
92 is where a second round of compression stops being visible. Below 80 you start to see what the WebP already threw away, twice over.
Why you ended up with a .webp
WebP is Google's image format, and since roughly 2020 most large sites serve it to any browser that will take it — it is genuinely 25–35% smaller than an equivalent JPEG. When you right-click and save an image from one of those sites, the browser saves what the server actually sent, which is the WebP. You did not choose it; the CDN did.
That is fine until something downstream refuses it. Windows Photo Viewer, older Photoshop, most print shops, a lot of job-application and government upload forms, eBay and Etsy listing tools, and almost every piece of software written before 2019 will either reject the extension or show a broken thumbnail. Converting to JPG is not an upgrade — it is a compatibility tax.
What the conversion costs you
Almost every WebP on the web is lossy WebP. It has already been through a compressor once. Re-encoding it as JPEG compresses an already-compressed image, and the two rounds of artefacts stack: the JPEG encoder faithfully preserves WebP's blocking and smearing, then adds its own.
At quality 92 — the default here — that second round is not visible at normal viewing sizes. At 65 it is, particularly around text, logos and any hard edge. This is also why the JPG usually comes out larger than the WebP it came from, often by 20–60%. JPEG is simply a less efficient format; you are paying bytes for compatibility. If the file size is the problem rather than the format, compressing to an exact size is the better tool.
Transparency and animation
WebP can carry an alpha channel; JPEG cannot, at all. Any transparent area is flattened onto white before encoding, because the alternative — leaving it undefined — turns transparent regions black in most decoders. If the transparency is the point, WebP to PNG keeps it.
Animated WebP is a container of frames. Browsers hand a single still frame to the canvas, so what you get back is one frame, not a sequence. There is no honest way to make a JPEG animate, and this page does not pretend otherwise.
Common questions
Why is the JPG bigger than the WebP I started with?
Because WebP compresses better. A WebP at a given visual quality is typically 25–35% smaller than the JPEG that matches it, so going the other way costs you those bytes back. A 20–60% increase is normal and is not a sign that anything went wrong.
Can I keep the transparent background?
Not in a JPG — the format has no alpha channel. Transparent pixels are filled with white here. If you need the transparency to survive, convert to PNG instead.
What happens to an animated WebP?
You get the first frame as a still image. The browser's decoder hands one frame to the canvas and JPEG cannot store a sequence in any case.
Which quality setting should I use?
92 unless you have a reason. It is high enough that the second round of compression is invisible while still producing a sensible file size. Use 100 only if the file is going into further editing, and 65 only if you have looked at the result and accepted it.
Does anything get uploaded?
No. The file is decoded and re-encoded by your own browser using the Canvas API. Load this page, disconnect from the internet, and conversion still works — that is the easiest way to verify the claim.