Convert WebP to JPG
Output is typically about 52% larger.
- Files stay on your device
- Free, no sign-up
Related tools
All image toolsQuestions
Will anyone notice the quality drop?
At quality 85 and above, almost certainly not at normal viewing size. The real risk is not photographs but flat graphics — logos, screenshots and anything with text pick up halos around hard edges no matter how high you set the slider, because that is how JPEG's compression works. Convert those to PNG instead.
Will converting WebP to JPG make the file smaller?
Usually, yes. A 12-megapixel photo is around 2.1 MB as WebP and around 3.2 MB as JPG — about 52% larger. Because JPG is a lossy format you can trade quality for size, so the exact result depends on the quality setting you pick.
Does converting WebP to JPG lose quality?
A little, by design. WebP is lossless and JPG is lossy, so some detail is discarded in exchange for a much smaller file. At quality 80–90 the result is visually indistinguishable from the original for photographs. For screenshots, logos or anything with sharp text, stay with a lossless format instead — lossy compression creates visible halos around hard edges.
What happens to transparent areas?
JPG has no alpha channel, so transparency cannot be preserved. Any transparent or semi-transparent pixels are composited onto a solid background — white by default — before encoding. If transparency matters, convert to PNG or WebP instead, both of which support it fully.
What happens to an animated WebP?
Only the first frame is converted. Every conversion here decodes one frame onto a canvas and re-encodes it, so the result is always a still image — that applies to JPG as much as to any other target. To shrink an animation while keeping the motion, a video file (MP4 or WebM) is usually around a tenth of the size of the equivalent WebP, and needs an encoder we do not ship yet.
What quality setting should I choose?
Quality 80 is the sweet spot for photographs — visually indistinguishable from the original for almost everyone, at a fraction of the size. Go to 90–95 for images you will edit or print later. Below 70, blocking artefacts start showing in smooth gradients like skies. Remember that JPEG loses a little more on every re-save, so always edit from the original.
How it works, and more about webp to jpg
How it works
- Add your WebP file. Drag a WebP file onto the drop zone, or click to browse. You can select several at once.
- Choose your settings. Adjust the quality slider if you want a smaller file or a sharper result. 80 suits most photographs.
- Download the JPG. Conversion runs on your device as soon as each file is added — no upload, no queue. Download each result when it is ready.
Why people convert WebP to JPG
Same origin story as WebP to PNG — an image saved from the web that a local tool refuses — but here the destination is a printer, an email attachment, or a form that names JPEG explicitly.
JPEG at 85 or above is the right call for photographic content. Its compatibility is the entire point: if a device can display an image at all, it can display a JPEG.
Worth knowing: This is a second lossy pass over lossy data, so stay off the low end of the quality slider. If the WebP had transparency, choose the background colour first — JPEG has no alpha channel and will flatten it to whatever you pick.
WebP and JPG side by side
| WebP | JPG | |
|---|---|---|
| Full name | WebP | JPEG |
| Compression | Lossy or lossless | Lossy |
| Transparency | Yes — alpha channel | No |
| Animation | Yes | No |
| Browser support | All modern browsers — Chrome 32+, Firefox 65+, Safari 14+ (2020), Edge 18+ | Universal — every browser, every device |
| Typical 12 MP photo | ~2.1 MB | ~3.2 MB |
| Usually used for | Web images where page weight matters and modern browsers are the audience | Photographs, email attachments and anything needing maximum compatibility |
On a typical 12-megapixel phone photo, the JPG output comes out about 52% larger than the WebP original. These are order-of-magnitude figures for one kind of image — your own results will vary a great deal, because flat colour, text and line art behave nothing like photographic detail, and the quality slider moves the figure substantially.
What this tool actually produces
Not estimates. Each row below was produced by running the file through this page in a real browser and measuring the result, at the default quality of 82.
| Test image | WebP in | JPG out | Change |
|---|---|---|---|
| Smooth gradient 1600 × 1200, broad tonal transitions — where banding and blocking show | 175 KB | 237 KB | +35% |
| UI screenshot 1440 × 900, dense text on flat panels — the hardest case for JPEG | 44 KB | 87 KB | +98% |
| Line-art diagram 1200 × 800, hard edges and large flat areas | 12 KB | 46 KB | +271% |
| Logo with transparency 512 × 512, flat colour on a transparent background | 7 KB | 13 KB | +90% |
Every test image got larger. That is expected for this pair rather than a fault: JPG is not the efficient choice for content that already suits WebP, and you are converting for compatibility or for editing headroom, not to save space. Measured in Chrome 150.0.7871.46; other browsers encode slightly differently.
What to watch out for
- Lossy — quality degrades a little every time you re-save
- No transparency; transparent pixels are flattened to a solid colour
- Visible ringing and blocking around sharp text and hard edges
- Roughly 30% larger than WebP at matching visual quality
- Transparency is lost. WebP supports an alpha channel and JPG does not, so transparent pixels are flattened onto a solid background colour. Pick the background above before converting, or convert to PNG or WebP instead.
- Animation is lost. Only the first frame is converted — every conversion here decodes a single frame onto a canvas and re-encodes it, so the result is a still image whatever the target format. To shrink an animation and keep the motion, a video file is typically around a tenth of the size of the equivalent WebP.
About the two formats
WebP is the pragmatic modern choice for the web: roughly 25–35% smaller than JPEG at comparable quality, with transparency and animation that JPEG lacks, and — since Safari 14 in 2020 — support in every browser that matters. It is the format to reach for when you want smaller pages without worrying about fallbacks.
JPEG has been the default photo format for three decades, and its compatibility is unmatched — if a device can display an image at all, it can display a JPEG. The trade-offs are that it discards detail permanently on every save, and it has no transparency channel at all, so anything transparent becomes a solid background.
Other conversions
Everything runs on your device — nothing is uploaded, so there is no size limit, no queue and no copy left on a server afterwards. There is more on how browser-based conversion works if you want the detail. Otherwise, browse every image tool, or convert JPG back to WebP.