Where WebP files actually come from
Almost nobody sets out to save a WebP file on purpose. It happens because most browsers now save images from the web in whatever format the site served them in, and a large share of the web serves WebP by default — it compresses better than JPEG at the same visual quality, so sites use it to load faster. You right-click, choose "Save Image," and a `.webp` file lands on your device without you ever choosing the format.
Where WebP still gets rejected
| Where it's going | Accepts WebP? |
|---|---|
| Modern browsers (viewing) | Yes, universally |
| Printer upload portals | Often not |
| Older Photoshop, older photo software | Frequently not |
| Some phone photo/gallery apps | Inconsistent |
| Older CMS platforms and web forms | Often restricted to JPG/PNG/GIF |
Browser support for WebP has been solid for years; the gap is everything outside the browser. A print shop's upload form, a decade-old desktop application, an e-commerce platform's product image field — a lot of software still only recognizes the formats that have been standard since the 1990s. Until that catches up, "convert to JPG" stays the fastest way through a rejected upload.
Transparency needs a decision
WebP can store an alpha channel the same way PNG does, but JPG has no concept of transparency at all. Converting a transparent WebP to JPG means every transparent pixel has to become some solid colour, so a background colour picker is built into this tool rather than silently defaulting to black, which is what happens when transparency is dropped carelessly. If you need to keep the transparency intact, choose PNG as the output instead of JPG.
Both WebP and JPG are lossy formats, so converting between them re-compresses the image once. At the maximum quality setting here that cost is not visible in normal viewing - it only compounds if you convert the same file back and forth repeatedly.
A whole folder at once
Drop in as many WebP files as you have and each converts on its own, with a single ZIP download once they are all done. There is no file count limit, since nothing is uploaded to a server that would need to handle the load.
Nothing is uploaded
Both the decoding and the re-encoding happen entirely inside your browser, using the canvas your browser already has built in for exactly this. The images never leave your device.