WebP to JPG Converter

A WebP to JPG converter turns a .webp image into the .jpg file that an upload form was expecting. The pattern is always the same: you save a photo from a site, the site served WebP, and now a job application portal, a marketplace listing, a print shop or a school system tells you to supply a JPEG. The file is a perfectly good image. It is the three letters after the dot that the form is refusing.

Converting happens in the page. The browser decodes the WebP, redraws it and encodes a JPEG, all client-side, so the photo never leaves your device and there is no queue to wait in.

One thing changes in a way you should know about before you add a file. JPEG has no transparency, so any transparent pixel has to become something, and the converter fills it with white. Say you have badge.webp at 1200 x 800, a logo on a cut-out background, and you convert it at the default Quality of 90. The 960,000 pixels come through unchanged where the logo is, and the empty background arrives as a solid white rectangle. The row underneath tells you: transparent areas were filled with white, because JPG has no transparency. On a white page nobody notices. On a dark page it is a box.

The Quality slider runs from 10 to 100 and starts at 90. It is a real trade, not a cosmetic setting: JPEG throws away detail to get smaller, and once thrown away it does not come back. Because most WebP files were already lossy, converting to JPEG is a second generation of loss stacked on the first, which is why 90 is a sensible default and why dropping to 40 for a photo full of fine texture will show. Each finished row prints the input size, an arrow, the output size and the percentage change, and moving the slider converts every added file again, so you can compare two settings instead of guessing at one.

The rest of the limits are short. Metadata is dropped in the re-encode, so EXIF, GPS coordinates and colour profiles do not reach the JPEG. An animated WebP contributes only its first frame. Images over 100 megapixels are refused with a message, empty files are refused, there is no byte-size limit, and a daily conversion limit applies. The tool is free, no signup.

• Your WebP files are converted client-side with the browser's own Canvas API. They are not uploaded, and no WebAssembly codec is fetched to do the work.
• The only network requests are for the daily limit: one asks whether a batch is allowed, and one afterwards records the number of files, their total size in bytes and the output format.
• File names, image dimensions and pixel data are never part of those requests.
• EXIF fields, GPS coordinates and colour profiles are left behind, because the JPG is encoded from the decoded pixels alone. That makes the output safer to post on a public listing.
• Results are kept in the tab's memory only, and are gone when you remove them, press Clear All or close the tab.