Kit-Bin
Donate

Drop WebP images here or click to browse

Processed entirely in your browser. Never uploaded to a server.

WebP is what most modern websites serve images as, so it's what you often end up with after saving a picture from one. It opens fine in a browser and then gets rejected by an upload form, an older editor, or a print service that only accepts JPG. Converting trades a little file size back for that compatibility.

Decoding happens on your device

Nothing about your image is sent anywhere — the WebP is decoded and re-encoded as JPG entirely inside your browser using WebAssembly.

FAQ

Why can't I use my WebP file somewhere?
WebP displays fine in every modern browser, but plenty of things outside the browser still reject it: some older image editors, some print and passport-photo upload services, some older phones and desktop software, and some CMS or e-commerce platforms with a strict file-type allowlist. Converting to JPG is the fix when something specifically won't take the file.
What happens to transparency?
WebP supports an alpha channel and JPG doesn't. If your WebP has transparency, it's discarded on conversion — JPG has no alpha channel to hold onto it, so the transparent areas keep only their underlying color rather than staying see-through. If you need to keep transparency, convert to PNG instead.
Will the JPG look worse than the WebP?
There's a small quality cost, since this is a second lossy encode on top of whatever compression the WebP already used. In most cases it isn't visible at normal viewing sizes, but it's not a lossless operation, so avoid converting back and forth repeatedly.
Does this work with animated WebP?
No — only the first frame converts, since JPG doesn't support animation. If you need to keep the animation, keep the file as WebP, or convert it to GIF or video instead.

Going the other way, for a website? Try JPG to WebP.

Need the JPG smaller, or a specific size? Try Compress Image or Resize Image next.

Not sure which format you actually need? Read the comparison.