Save a transparent WebP as a JPG without thinking about it, and the see-through parts come back black. That single surprise derails more conversions than anything, and it's worth understanding before you flatten a logo or a cut-out product shot into a JPG.
WebP is everywhere now — Google spent the better part of a decade pushing it because it makes images genuinely tiny — but "tiny" and "opens anywhere" are two different things. Attach one to an email, open it in an older copy of Photoshop, or push it to a marketplace listing, and you can still hit a wall of "unsupported file type." A JPG clears that wall almost every time. For an ordinary photo the swap is invisible; for anything with transparency, as you just saw, it is not.
Why WebP and JPG don't swap cleanly
A WebP file can carry an alpha channel — real transparency — and can even hold a short animation. A JPG does neither; it is a single, fully opaque, rectangular still. So "converting" is never a rename. It is a re-encode: the image gets decoded, painted onto a fresh surface, and re-saved with JPEG compression.
Two things fall out of that, and both matter later:
- Every transparent pixel has to become some solid color. Left unhandled, editors and browsers tend to render those empty areas as black — the exact gotcha from the top. Fill them on purpose and you dodge it.
- You are compressing something already compressed. WebP was lossy, JPG is lossy, and stacking them costs a sliver of quality. You will never spot it on a normal photo, but it is not literally zero.
Turning a .webp into a .jpg
The WebP to JPG tool on Every Boring Tool does the re-encode right on your own machine — the picture is decoded and redrawn locally, nothing shipped off to be processed, which is what you want for a screenshot or anything you'd rather not hand to a stranger's server. No account, and the JPG comes back clean, with nothing stamped across it.
- Open the WebP to JPG tool.
- Click Choose a WebP image and select your
.webpfile. - The tool decodes the picture and redraws it, laying any transparent regions over a white background so they don't come out black.
- Click Convert to JPG.
- Download the finished
.jpg, ready for whatever refused the WebP.
What the converter decides for you
No advanced settings live here, which is a relief until it isn't — so know the three calls it makes for you:
- Quality is pinned at roughly 92%. That is a deliberately generous setting: sharp-looking output that still compresses well. There is no slider, so if you are chasing a specific file size, this is not the tool for that part of the job.
- Transparency is filled with white. The tool literally paints a white rectangle, then draws your image on top. A transparent WebP background comes out white — not black, and not see-through.
- The pixel dimensions stay put. Width and height carry over untouched; nothing is resized or cropped.
Where a JPG is the wrong finish line
A conversion worth trusting is one that tells you when it shouldn't happen. Five cases here qualify.
Transparency is gone permanently. If you need a background to stay see-through — a logo sitting on a colored web page, say — a JPG simply can't hold that, and this conversion bakes in the white fill instead. Keep the WebP, or convert to PNG, which preserves the alpha channel.
An animated WebP collapses to one frame. Some WebP files are short loops. A JPG is a single still, so you keep exactly one frame and lose the motion. If the movement is the point, aim for GIF or MP4 instead.
You can't hit a target size. With quality locked near 92%, this is perfect for "just give me a good-looking JPG" and useless for "get this under 200 KB for the upload cap." For a hard size limit, run the JPG through a dedicated image compressor afterward.
The re-compression doesn't reverse. Going WebP to JPG and back won't recover anything lost on the way, so keep your original if there's any chance you'll want it later.
Big images lean on your hardware. Because the work happens on your device, not a server, a huge file is bounded by your memory. Everyday photos and web graphics are fine; a massive multi-megapixel image on an aging phone might not make it.
Reach for a different tool when
- You need the transparency kept: convert to PNG, not JPG.
- The source is animated: export it as a GIF or a video.
- You must land on an exact file size: convert first, then compress the JPG with a size-target or quality-slider tool.
- You've got hundreds of files: a batch converter — or a command-line workhorse like
cwebp/dwebpor ImageMagick — beats converting one at a time. - You want print-grade quality: trace the image back to its source. If it began life as a lossless PNG or TIFF, convert from that and skip one of the two lossy rounds.
A ten-second check before you close the tab
Open the JPG you just downloaded and eyeball three things: the colors read correctly, any formerly transparent areas are the white you expected, and the file actually opens in the app that rejected the WebP. Pass all three and you're set — an ordinary, universally readable JPG that nothing should turn away.