JPG to WebP
Your images never leave this device
WebP compresses photographs meaningfully better than JPEG at the same apparent quality. Google’s own comparison puts it at 25 to 34 per cent smaller for a matched SSIM score. That measurement was taken encoding from uncompressed originals, though, and you are starting from a JPEG, which changes what you should expect.
How to convert JPG to WebP
The 25 to 34 per cent figure comes from encoding PNG sources into both formats and comparing at matched quality. Re-encoding an existing JPEG is a different situation. That JPEG has already thrown away the high-frequency detail WebP would also have thrown away, so a good part of the advantage was spent before you started. The saving is still real; it is usually just smaller than the headline. If the camera original or the export from your editor still exists, convert from that instead and you get the full benefit.
Both formats are lossy, so this is a second generation. One re-encode from a decent original is invisible at sensible settings. What does damage is a cycle: JPEG to WebP to JPEG and back again, each pass quantising whatever the last pass left behind. Convert once, in the direction you actually need, and hold on to the source.
There is one case where WebP is structurally the weaker format. Lossy WebP is built on VP8’s intra-frame coding, which always stores colour at half resolution in each direction and offers no full-resolution mode at all. For photographs that never shows. For fine coloured lettering on a flat background it is the format’s worst case, and an image like that belongs in PNG regardless of which lossy format you were choosing between.
What people use it for
- Answering a PageSpeed warning about next-generation image formats
- Re-exporting a photo gallery before it goes onto a site
- Getting a hero photograph under a page-weight budget
- Converting camera originals once rather than repeatedly through an editor
- Keeping a JPG for email and a WebP for the web page
Questions
Google measures 25 to 34 per cent at matched SSIM, encoding both from uncompressed sources. Starting from an already-compressed JPEG, expect less than that.
Every lossy re-encode loses a little. One conversion from a good original is fine; going back and forth repeatedly is not.
For anything you might send by email or open in older desktop software, yes. For a website, the WebP alone is enough.
82 is the default and holds up well. WebP is generally cleaner than JPEG at the same number, so you can go lower here than you would there.
Support is patchy in desktop mail clients. Attach a JPG if you do not know what the recipient uses.
Yes. Lossy WebP stores its dimensions in fourteen bits, so neither side can exceed 16,383 pixels.
No. The output is rebuilt from decoded pixels, so camera data, capture date and GPS coordinates all go.
No. The browser decodes the JPG and encodes the WebP locally.