JPG to WebP
Cut a JPG down for the web — never uploaded.
How it works
Three steps, and nothing leaves your device.
-
1
Drop the JPG in
It is decoded in the page; nothing is sent anywhere.
-
2
It is encoded as WebP
At 92% quality, which holds up well on photographs.
-
3
Download the WebP
Smaller at the same visible quality.
Worth knowing before you convert a whole folder
- WebP beats JPG at the same visible quality. That is the reason to do this: the picture looks the same and the page gets lighter. On a photo-heavy page the saving adds up quickly.
- You are re-compressing something already compressed. The JPG has already thrown detail away, and WebP encodes that result again. At 92% it is not visible, but converting a JPG that was itself saved from a JPG a few times over will show it. Start from the highest-quality original you have.
- A very small or already-tiny JPG may not shrink. Below a few tens of kilobytes the format overhead starts to dominate and the WebP can come out the same size or larger. Check before replacing it.
- Serve both if your audience is broad. The usual production pattern is a
<picture>element offering WebP with the JPG as the fallback, so anything that cannot read WebP still gets an image.
Frequently asked questions
How much smaller will the WebP be?
Usually a meaningful reduction at the same visible quality. It varies with the picture.
Will quality drop?
It is a second lossy encode, so technically yes. At 92% it is not visible on a photograph.
Can the WebP come out bigger?
On very small images, occasionally. Compare before replacing the original.
Is my image uploaded?
No. Everything runs in your browser.