Convert WebP to JPEG
Drop a WebP file below and get a JPEG back. The conversion happens on your own machine, so nothing is uploaded and there is no size or quantity limit beyond what your browser can hold in memory.
Drop images here
Ctrl/⌘ VPaste a screenshot or copied image
Accepts WebP
Lower means a smaller file. 75 is a good default for photos.
100% in your browser Files are never uploaded.
Why convert WebP to JPEG?
Plenty of websites, content management systems and older desktop programs reject WebP uploads outright. JPEG is accepted just about everywhere, and that alone accounts for most of these conversions.
Expect the JPEG file to come out larger than the WebP you started with. That is the price of the broader compatibility and simpler decoding JPEG gives you.
WebP can carry transparency; JPEG cannot. Transparent pixels are composited onto white during conversion, so a logo with a see-through background will come out sitting on a white rectangle.
Both formats are lossy. Every re-encode discards a little more detail, so it is worth starting from the original rather than from a copy that has already been through this a few times.
You saved something from a website and got a .webp, and now you need a file that everything on earth will open. JPEG is that file. It has been the universal currency of images for thirty years — every phone, every printer, every ancient upload form takes it without complaint. That universality is the whole reason to do this conversion, and it is a good enough reason on its own.
Before you convert
If the image has transparency, decide before you convert
WebP can carry an alpha channel and JPEG cannot, so any see-through area has to be filled with a solid colour on the way over. This converter uses white. If the transparency matters — a logo you plan to drop onto a coloured background, a product cutout — then JPEG is the wrong destination and PNG is what you want instead. Compatibility is not worth much if the result is a logo sitting on a white box.
Expect the file to grow a little, and do not chase quality 100
WebP compresses roughly a third better than JPEG at similar quality, so the same picture in JPEG needs more bytes. That is normal. What is not worth doing is pushing quality to 100 to compensate — you get a dramatically larger file and no visible improvement, because the detail lost by the WebP encoder is already gone. Around 85 is the sensible landing spot.
Animated WebP will not survive
A fair number of the WebP files floating around the web are animations that replaced GIFs. JPEG holds exactly one frame, so an animated source arrives as its first frame and the motion is gone. Nothing warns you about this in most tools — the file simply stops moving.
What carries over
- Pixel dimensions
- Colour profile
- Compatibility with essentially everything
What does not
- Transparency — filled with white
- Animation frames beyond the first
WebP vs JPEG at a glance
| Property | WebP | JPEG |
|---|---|---|
| Compression | Lossy | Lossy |
| Transparency | Yes | No |
| Typical file size | 65-75% of an equivalent JPEG | 100% of an equivalent JPEG |
| Compatibility | Supported by all current browsers and most apps | Opens everywhere, including decades-old software |
| Usually comes from | Websites optimising page weight | Digital cameras and photo sharing |
Frequently asked questions
Are my WebP files uploaded anywhere?
No. The decoder and encoder are WebAssembly modules that run inside this page. The network tab may show a codec downloading the first time you use a format, but no request contains your file. On supported browsers, a codec that has already been used is cached so the same conversion can work offline.
Is there a file size or quantity limit?
There is no limit imposed by us. The practical ceiling is your device’s memory, since the image has to be held uncompressed while converting. On a typical laptop, images up to around 100 megapixels convert without trouble.
Will converting to JPEG lose quality?
JPEG is a lossy format, so some data is discarded. At the default quality setting the difference is not visible at normal viewing sizes. If you need an exact copy of the pixels, choose PNG instead.
Does it work on a phone?
Yes. The same WebAssembly modules run on mobile browsers. Conversion is slower than on a desktop because phone CPUs are weaker, and very large images are more likely to hit memory limits.
Why did I end up with a WebP file?
Most websites now serve WebP because it is smaller than JPEG, so saving an image from a web page usually hands you one. Browsers support it well, desktop software noticeably less so — which is why converting it away is such a common need.
What quality setting should I use?
For photographs, 75 to 85 is the range where most people cannot tell the result from the original at normal viewing size. Below about 60 you start seeing blocky artefacts around sharp edges. Above 90 the file grows quickly in exchange for very little visible gain.