JPG to WEBP
JPG to WebP conversion, with the quality and size consequences stated up front.
Why convert JPG to WEBP
WebP at the same visual quality is typically 25 to 34 percent smaller than JPEG, which is why it is the sensible default for images on a website.
What you give up
It is a second generation of loss. The JPEG artefacts are already in the pixels and the WebP encoder compresses them again. Convert from a PNG or the original capture when you can.
When it is the right move
Do this for any image you control the delivery of — blog posts, product photos, landing pages. Every current browser supports WebP, so the compatibility argument has largely expired.
Size, honestly
Expect 25–34 percent smaller than the equivalent-quality JPEG; more if you also drop metadata.
Why this runs in your browser
The file is read from your disk by the browser, decoded with the browser's own codecs, and re-encoded in this tab. No upload request is made, nothing is queued on a server, and closing the tab leaves no copy anywhere. You can verify this in the network panel while it works.
How to use it
- Drop one or more JPG files on the drop zone.
- Set the output format to WEBP.
- Convert and check the reported before-and-after file sizes.
- Open the result and check transparency and edge detail before shipping it.
Worth knowing
- Output format is WEBP and input is read as JPG.
- Size expectation for this direction: Expect 25–34 percent smaller than the equivalent-quality JPEG; more if you also drop metadata.
- Conversion happens in the browser; no file leaves your machine.
- Metadata is discarded by the canvas round-trip.
Limitations
- It is a second generation of loss. The JPEG artefacts are already in the pixels and the WebP encoder compresses them again. Convert from a PNG or the original capture when you can.
- Animation is not preserved when converting from an animated source.
- Converting between two lossy formats compounds compression artefacts.
- Writing WEBP depends on your browser exposing that encoder.