Convert WebP to JPG
Convert WebP to JPG so any app can open it. Adjustable quality, a background colour for transparency, batch input and no uploads.
- Runs in your browser
- Files are never uploaded
- Free, no account
JPG has no alpha channel, so transparent pixels are painted with the colour below.
Metadata is stripped. Re-encoding rebuilds the file from raw pixels, so EXIF — GPS coordinates, camera model, serial number, capture time — and any XMP or IPTC block are dropped. Pixels are written in sRGB.
Nothing leaves this tab. The encoders are WebAssembly builds of libjpeg-turbo (MozJPEG), libpng/oxipng, libwebp and libavif running inside a worker on your machine.
How to convert WebP to JPG
- Drop your .webp files onto the box above. Mixed batches of any size are fine.
- Choose a background colour. WebP can be transparent and JPEG cannot, so transparent pixels are composited onto the colour you pick — white unless you change it.
- Set the quality. The default of 85 is deliberately higher than usual because the source has already been through one lossy codec.
- Save each JPG, or download all of them as a single ZIP.
Why convert at all?
JPEG is the most universally readable image format in existence. Every operating system, camera, printer, photo kiosk, email client and web form from the mid-nineties onward accepts it. WebP, despite full browser support, is still refused by plenty of desktop applications and upload forms. If something will not take your file, converting it to JPG is the shortest path to it working.
The trade is size. The same photograph as a JPEG is normally 25–35% larger than the WebP it came from, because WebP's coder is simply more efficient. You are spending bytes to buy compatibility.
Transparency: what your background choice does
A baseline JPEG stores three colour channels and nothing else — there is no way to encode "this pixel is see-through". Every transparent or semi-transparent pixel in the WebP is blended with your chosen colour using its own alpha value, so a shadow that fades from 60% to 0% opacity fades into the background colour smoothly rather than being cut off.
| Where the image will be used | Suggested background |
|---|---|
| Word document, printed page, most web pages | White (#ffffff) |
| Dark-themed slide deck or app screenshot | Near-black (#1e293b or #000000) |
| Product listing on a marketplace | White — most platforms require it |
| Overlaying a coloured panel | Sample that exact colour and paste the hex value |
If the image will sit on more than one background colour, JPEG is the wrong destination. Use WebP to PNG instead and keep the alpha channel.
Quality guidance for a second-generation encode
- 85–90: the recommended range here. High enough that the second lossy pass does not add visible artefacts on top of the first.
- 80: fine for casual sharing and messaging, where the image will be re-compressed anyway.
- Below 70: the two generations of artefacts start reinforcing each other, most noticeably as blockiness in flat areas and halos around text.
- 95+: only worth it if the JPG is an intermediate step before more editing.
For a lossless target, use WebP to PNG. To convert a folder containing WebP, AVIF and PNG files in a single pass, use the universal image converter.
Questions
What happens to transparent WebP images?
JPEG cannot store transparency, so transparent pixels are composited onto the background colour you choose. White is the default; pick black or a brand colour if the image will sit on a dark surface.
Will the JPG be bigger than the WebP?
Often, yes. WebP compresses more efficiently, so the same picture as a JPEG at comparable quality is typically 25–35% larger. You are trading bytes for compatibility, which is usually the point of the conversion.
Which quality avoids visible damage?
Because the source has already been compressed once, use 85–90 rather than the usual 80. That keeps the re-encoding pass from adding a second, visible layer of artefacts around edges.
Can I convert dozens of files in one go?
Yes — batch conversion is the default. Each file shows its own before and after size, and everything is bundled into a single ZIP when you convert more than one.
What happens to an animated WebP?
JPEG cannot hold animation, so only the first frame is written out. If you need the whole sequence, convert the source to a GIF or MP4 instead — the animation is discarded here, not silently flattened into one image.