WebP vs JPG: Should You Still Be Using JPG?
5 min read
WebP was developed by Google to replace JPG and PNG on the web. It is supported by every modern browser, Chrome, Edge, Firefox, and Safari since 14, and typically produces files 25–35% smaller than JPG at comparable visual quality.
Why WebP wins on size
WebP's lossy mode uses a more modern compression method (based on the VP8 video codec) than JPG's discrete cosine transform. At the same perceptual quality, that translates directly into smaller files, which means faster page loads, less bandwidth, and better Core Web Vitals.
WebP also has a lossless mode that usually beats PNG by ~26%, and it supports alpha transparency in both modes.
Where JPG still makes sense
JPG remains the universal exchange format: every camera, editor, operating system, and app from the last 25 years reads it. If you're emailing photos to someone, uploading to a service that rejects WebP, or archiving family photos, JPG is the safer choice.
- Web performance work → WebP
- Images with transparency that must stay small → WebP
- Maximum compatibility (email, legacy software) → JPG
- Camera originals and long-term archives → keep the original format; export copies as needed
Quality considerations
Like JPG, lossy WebP accumulates generation loss when re-encoded repeatedly. Convert from your original files rather than re-saving converted copies.