Free JPG to WebP Converter
Convert JPG images to WebP — smaller files, same quality. All in your browser.
JPG → WebP
Drop a JPG here or click to select
What the WebP quality setting actually saves
WebP's advantage is not a rumour, but the size of it depends entirely on the quality value. We took one 1200×630 image (44,915 bytes as PNG), drew it into a canvas and encoded it with toBlob() at seven lossy settings in headless Chrome, recording Blob.size for both formats. Measured, not estimated:
| Quality | JPEG | WebP | WebP is |
|---|---|---|---|
| 1.00 | 218,307 B | 142,160 B | 34.9% smaller |
| 0.95 | 109,443 B | 41,074 B | 62.5% smaller |
| 0.92 | 90,251 B | 35,916 B | 60.2% smaller |
| 0.85 | 72,233 B | 27,792 B | 61.5% smaller |
| 0.75 | 58,265 B | 22,212 B | 61.9% smaller |
| 0.60 | 46,603 B | 19,178 B | 58.8% smaller |
| 0.40 | 36,427 B | 16,440 B | 54.9% smaller |
| 0.10 | 16,194 B | 11,370 B | 29.8% smaller |
This tool opens at 0.85, and at 0.85 WebP is 61.5% smaller than the JPEG it replaces — 27,792 bytes against 72,233 for the same pixels. It is also 38% smaller than the source PNG. Nothing was resized; only the encoder changed.
The gap is widest near the top of the slider (62.5% at 0.95) and narrows at the bottom (29.8% at 0.10), because by 0.10 the JPEG has already thrown away so much detail that there is little left to save. If you are converting for the web and want one number: 0.80–0.85 lands around 38% of the JPEG's weight on this image — a 62% saving without touching dimensions.
One trap at the other end: quality 1.00 is not lossy WebP. Chromium switches to lossless there, and the file jumps to 142,160 bytes — 3.2× the source PNG, and larger than any sensible setting below it. Pinning the slider to 100% to “keep the best quality” is the one move that makes WebP lose. The JPEG side of the same measurement, including what “quality 75%” does to a JPEG's byte count, is on the compress JPG page.
More Free Tools
Frequently Asked Questions
Yes. The slider value goes straight to the browser's WebP encoder, and WebP honours it — the same 1200×800 photo converted to 17.3 KB at 0.30 and 112.8 KB at 0.95 in Chrome. That is the opposite of this site's PNG tools, where the browser ignores the quality argument completely and the output size never moves.
Not currently; conversion is one image at a time. There is no queue and no account, so a folder of photos has to go through one file per drop. Dropping several files together converts only the first one and ignores the rest.
No. Decoding and encoding both happen in your browser with the Canvas API, so the file never leaves your device.
They are dropped. The file is decoded to pixels and re-encoded as WebP, so only image data survives: a JPEG carrying EXIF metadata converted here produced a WebP with no Exif, XMP or ICC blocks inside it. Keep the original file if you need the shooting data.
Yes. Alpha survives the conversion — a test PNG with a fully transparent corner and a half-transparent block came back as a WebP with identical alpha values. The file picker only accepts JPG, so this path is for drag-and-drop.
Lossy WebP is tuned for photographs, so graphic-style images — screenshots, flat colours, hard edges, or a JPEG that was already optimised — can grow. The readout shows the real percentage with a + sign when that happens: lower the quality slider, or simply keep the JPEG.
A 6000×4000 (24 megapixel) JPEG converted to WebP without trouble, which covers phone and camera photos. The ceiling is whatever your browser's canvas can allocate; if that is exceeded the tool reports the failure instead of saving a broken file.
Only the first frame is converted. The canvas holds a single still image, so the animation is lost — it is not carried into the WebP.