Why the image you saved turned out to be a .webp
Many websites store their pictures as WebP, a format Google introduced in 2010 to make pages load faster. Every current browser displays it, so you rarely notice — until you choose “Save image as” and end up with something like product-photo.webp.
Outside the browser, plenty of software still treats WebP as an unknown file. Older desktop editors may refuse to open it, print shops often want JPG, some upload forms only take JPG or PNG, and some Office versions won’t insert it. JPG is accepted nearly everywhere, so converting is the simplest way to make a downloaded image behave like a normal photo again.
Turning a batch of WebP files into JPGs
- Add your images. Drag WebP files onto the converter above, drop a whole folder (subfolders included), or paste from the clipboard. One batch holds up to 500 files.
- Pick JPG and set the quality. The slider runs from 50 to 100 and starts at 92. To shrink the pixel dimensions too, choose a maximum long edge of 4096, 2560, 1920 or 1280 px; otherwise the original size is kept.
- Let it run. Your browser decodes each WebP with its built-in decoder and re-encodes it as JPG, using two to four background workers in parallel depending on your device.
- Download. Use each file’s Save link, or “Download all (ZIP)” for the whole set.
Names carry over, so banner.webp becomes banner.jpg; if two files would share a name, the second gets “ (2)” instead of overwriting the first.
What the quality slider means for a WebP-to-JPG conversion
Most WebP images on the web are lossy: some fine detail was discarded when the site created them. JPG is lossy too, so this is a lossy-to-lossy re-encode — the JPG encoder compresses the decoded pixels again in its own way. The slider sets how much that second pass may throw away.
| Setting | What you get | Good for |
|---|---|---|
| 92 (default) | Visually very close to the WebP | Most uses, including printing and listing uploads |
| 95–100 | Marginally cleaner detail, noticeably larger files | Images you’ll edit further before a final save |
| 70–85 | Smaller files; artifacts can appear around sharp edges and text | Forms and email with tight size limits |
A setting of 100 doesn’t bring back detail the WebP already discarded; it only stops the JPG step from discarding more. And the JPG is often larger than the WebP it came from, because WebP generally fits an image into fewer bytes at similar quality. If size matters, try the resize option before dropping quality a long way.
Transparent areas, animations and embedded photo info
- Transparency becomes white. JPG has no transparent pixels, so a logo or cutout comes out on solid white with soft edges blended against it. To keep the transparency, use WebP to PNG.
- Animated WebP gives you the first frame only. This tool doesn’t produce GIFs or video, so an animated sticker or banner becomes one still image.
- EXIF is kept when it exists. Web images often have camera data stripped already, but if a WebP carries EXIF (date taken, camera, exposure, GPS location), it’s copied into the JPG by default, with the orientation tag reset to normal because the pixels are already upright. “Remove GPS location” drops just the coordinates; unticking “Keep photo info” drops everything.
- Colors come out in standard sRGB, because the browser’s decoder converts the WebP to sRGB, which is what JPG viewers expect.
Example: product photos for a marketplace listing
Say a supplier sent you 60 product images as WebP, and the marketplace’s listing form only takes JPG. Drop the folder onto the converter and leave quality at 92 so textures and label text stay crisp. If the marketplace publishes a maximum image size, pick the resize option that keeps you under it — check its own image guidelines rather than guessing. Untick “Keep photo info” if you’d rather not publish camera details or location. Then “Download all (ZIP),” unzip and upload. Shots with transparent backgrounds will land on white, so glance at the edges first.
Need one file for a buyer, like a line sheet? JPG to PDF accepts WebP directly and puts each image on its own page.
When you shouldn’t convert WebP to JPG
- The destination already accepts WebP. Converting a lossy WebP adds another round of compression; upload the original instead.
- You need transparency or animation. Choose PNG for transparency; animation isn’t supported in any output.
- You have more than 500 files. Split them into several batches; each batch is capped at 500 so the browser tab stays responsive.
- Your browser is old. The converter needs a recent Chrome, Edge or Firefox, or Safari 16.4 or later on Mac, iPhone or iPad.
Your images never leave your device
Nothing is uploaded. The WebP is decoded by your browser and encoded to JPG by its canvas encoder, all inside this tab. The page’s Content-Security-Policy only permits network connections to pd00.com itself and to Cloudflare’s cookieless visit counter (page views only, never file data), so the browser blocks any other destination. You can watch this in DevTools → Network; the steps are on our privacy page. Once the page has loaded, you can even go offline and keep converting.