Converter
Convert WebP to JPG without sending the file anywhere
WebP is efficient, but plenty of destinations still want a JPEG: older software, forms that only accept .jpg, print workflows, and platforms that quietly reject what they do not recognise. This converts WebP to JPG locally, so the file never leaves your device, and lets you pick the quality or aim at a specific file size.
Tap to choose your photosDrop an image anywhere, or browse files
Supports WebP, JPEG, PNG, and AVIF up to 50MB. Processed offline.
Output is preset to JPEG — change it after you drop a file.
How to convert WEBP to JPEG
- Add your image. Drop in a WEBP file — up to 50 MB, decoded on your device.
- Choose the output format. Pick JPEG in the Target Format row.
- Set quality or a size target. Use the quality slider, or set a target file size in KB if the destination has a limit.
- Compare before saving. The slider shows the original against the result so you can see what changed.
- Download. Save the JPEG file. Nothing was uploaded at any point.
What actually changes when you convert
WebP and JPEG are both lossy formats, so a conversion is a decode followed by a fresh encode — the JPEG is built from the pixels the WebP file describes, not from the original photo you started with. Any detail the WebP already discarded is gone for good, and JPEG adds its own compression artefacts on top. Two rounds of lossy compression always cost more than one.
The practical consequence is to convert at a high quality and stop. Around 88–92 keeps edge and text artefacts from becoming visible; pushing the slider much lower than that stacks a second, clearly visible loss on an image that has already been through one. If you still have the original, re-export from that instead.
Transparency is the other thing to check. JPEG has no alpha channel, so a WebP with transparent areas is flattened against white. If you need to keep transparency, choose PNG as the output format, or keep the image as WebP.
Why a WebP file can get bigger as a JPEG
Expect the file to grow. That is not a defect in the converter — it is the trade WebP was designed to make. At visually equivalent quality a WebP is typically the smaller file, so moving back to JPEG costs size to buy compatibility. If the destination also has a byte ceiling, set a target file size rather than lowering quality by guesswork; the compressor will find the best setting that fits.
When converting is the wrong move
If the goal is a smaller image rather than a .jpg file, converting to JPEG is usually the long way round — compressing the WebP further gets you there with less loss. Conversion earns its cost when something genuinely rejects WebP. Otherwise, resize or recompress in the format you already have.
WebP to JPG questions
No. Both formats are lossy, so the conversion decodes one compressed file and creates another. The result looks close at high quality but is not byte-identical, and it is usually larger. Set quality around 90 and check the comparison slider before you commit.
Because WebP is the more efficient of the two at equivalent visual quality. You are paying in bytes for compatibility, which is the correct trade when a form or application only accepts JPEG.
Yes — that is the point of this page. Decoding and encoding both happen in your browser through WebAssembly. Open DevTools’ Network tab while you work and you will see no request carrying image data.
Add several files to the queue and they are processed together with the same settings. Batch conversion is where a local tool pulls well ahead of an upload-based one: a dozen files encoded in your browser never touch a server or a queue.
Not as a JPEG — the format has no alpha channel, so transparent areas are flattened to white. If you must keep transparency, choose PNG as the output instead.
Want the smallest file instead of the most compatible one? Compress to WebP or compress to AVIF.