What this does
Every WebP you drop is decoded by your browser, drawn onto a canvas at its original pixel dimensions, filled onto the background colour you choose, and re-encoded as a baseline JPEG. The result is a normal .jpg that opens anywhere — older email clients, Word, print shops, government forms, and apps that never added WebP support.
This is a converter, not a compressor. WebP is typically smaller than JPEG at the same quality, so your output will often be a bigger file. If size is the goal, use the image compressor and set a target.
Why convert at all
WebP is well supported in current browsers and increasingly elsewhere, but plenty of desktop software still refuses it: photo editors, print workflows, some email clients and a long tail of upload forms. Converting is the fastest way past "this file type is not supported".
Transparency and animation
JPEG has no alpha channel and no animation. Transparent pixels become the background colour you pick, and an animated WebP converts only its first frame. If you need either feature preserved, keep the WebP or use PNG.
When to use something else
- PNG to JPG — screenshots and graphics with transparency.
- Compress to an exact size — 100 KB, 200 KB, 500 KB targets for upload forms.
- HEIC to JPG — iPhone photos that arrive as
.heic. - Resize to exact dimensions — profile pictures and fixed-size requirements.
Questions
Are my images uploaded?
No. There is no server involved. Load the page, disconnect from the internet, and the converter still works — that is the test.
Why did my file get bigger?
Because WebP is a more efficient format. That is normal and expected; you are trading bytes for compatibility. Lower the quality slider if the size matters.
Does it keep the resolution?
Yes, unless you set a maximum dimension. JPEG is lossy, so fine detail softens slightly, but the pixel dimensions do not change.
Does it strip metadata?
Yes. Re-encoding through a canvas drops EXIF, including GPS coordinates.