WebP and JPG, and why you’d switch
WebP is the newer one. Google built it for the web, and it squeezes photos down to roughly 25-35% smaller than the same JPG at matching quality. Great for page speed. Less great when you hand the file to something that has never heard of it.
That’s the whole reason this page exists. You grabbed a .webp off a site, or a tool spat one out, and now Etsy, an old CMS, your insurance portal, or somebody’s 2014 photo printer is refusing it. JPG, on the other hand, opens literally everywhere. Decades of universal support. Boring, but it works.
The catch worth knowing: JPG can’t store transparency. If your WebP had a see-through background, those areas come out white here, because that’s the sane default for photos. Need the transparency kept? Use a PNG converter instead.
How the conversion happens
Everything runs on your machine. The file gets decoded into an off-screen canvas, then re-encoded as a JPG with canvas.toBlob. Nothing uploads. No server sees your image, which also means it’s quick and works offline once the page has loaded.
- Drop a
.webponto the box, or click to browse. - Drag the quality slider. 80-92% is the sweet spot for most photos.
- Hit Convert to JPG.
- Check the before and after sizes, then Download .jpg.
The slider maps straight to JPG’s compression. Pull it down to 60% and the file shrinks hard, but you’ll start seeing blocky artifacts around sharp edges and text. Push it to 100% and you get near-perfect quality at the cost of size. The readout shows you exactly what each setting costs, so you don’t have to guess.
Good to know
- It’s all client-side. Your photo never leaves the browser tab. Handy for anything you’d rather not upload.
- White fills the transparent bits. JPG has no alpha channel, so any transparency becomes a white background.
- Animated WebP gives you one frame. The browser draws the first frame to the canvas, so you get a single still image.
- Output dimensions match the input. A 1920x1080 WebP comes out a 1920x1080 JPG. This converts the format, not the size.
- Big files are fine. A 12MP photo converts in well under a second on a normal laptop.
Once you’ve got the JPG, you can run it through the Image Compressor if you want to shave off a few more kilobytes, or the Image Resizer if it needs to fit a specific box.
Common questions
Does the quality drop when I convert?
A little, yeah. JPG is lossy, so re-encoding always tosses some data. At 90% the difference is invisible for almost any photo. Go below 70 and you’ll notice it on fine detail and edges.
Why did my image get a white background?
JPG can’t do transparency. The transparent pixels from your WebP get painted white before encoding. If you need the background kept, convert to PNG rather than JPG.
Is anything uploaded to a server?
Nope. The decode and encode both happen in your browser using a canvas. Close the tab and there’s nothing left anywhere.
My JPG is bigger than the WebP. What gives?
That’s expected. WebP usually beats JPG at the same visual quality, so reversing it often costs you size. Lower the quality slider if you need a smaller file.
Can I convert several WebP files at once?
This handles one image per run. Convert one, hit New File, drop the next. For large batches you’d want a desktop tool.
Will it work on my phone?
Yes. Modern mobile browsers handle WebP decoding and canvas encoding fine, so the converter runs the same on a phone as on a desktop.