Convert JPG to WebP
The usual reason is web performance: WebP typically lands 25–35% smaller than JPEG at matched visual quality.
Options
All processing runs in your browser. No file leaves this device.
WebP is supported by every current browser, and has been since Safari 14 in 2020. For a site serving photographs, switching to it is one of the least invasive ways to reduce page weight — the images look the same and the bytes drop by roughly a third.
One caveat specific to this conversion: your JPG has already been through lossy compression, and encoding to WebP compresses it again. The two codecs discard different things, so a second generation of loss is real even though it is usually invisible at the default quality. Where possible, encode WebP from the original rather than from an already-compressed JPG.
Keep the quality slider high — 85 to 90 — when converting from JPG, precisely because you are stacking a second lossy pass. Pushing WebP down to 60 on a source that was already a 75% JPEG produces visible mush in flat areas like skies.
Every file is processed on this device, in parallel across your CPU cores. Nothing is uploaded.
Common questions
- Do all browsers support WebP?
- For viewing, yes — Chrome, Firefox, Edge, and Safari since version 14 in 2020. Creating WebP is a separate question: Safari has no WebP encoder in canvas, so this particular page cannot run there. It will say so rather than failing on every file. Use Chrome, Edge or Firefox to do the conversion.
- How much smaller will the files be?
- Typically 25 to 35 percent at matched visual quality, though it varies a lot with content. Smooth gradients and skies benefit most; noisy, highly detailed images benefit least.
- Are the files uploaded?
- No. Decoding, resampling and encoding all run inside this page. Nothing is transmitted, and there is no server that could keep a copy. Watch the Network tab in your devtools during a conversion if you want to confirm it.
- Can I convert many files at once?
- Yes — drop in as many as you like and they are processed in parallel across your CPU cores. A single file downloads directly; multiple files come back as a ZIP. In Chrome and Edge you can also write them straight into a folder you pick.
This converter is part of a full editing pipeline — tone, colour, lens correction and batch export all run the same way, without uploading.
Open the full pipeline