WebP, explained without the hype
WebP gets talked about like a revolution. It's not — it's just a better-engineered format that usually saves you bytes. Here's where it genuinely helps and where I'd still reach for an old-fashioned JPEG.
WebP is basically "JPEG and PNG, but smaller"
WebP is Google's image format, and the short version is that it usually does the same job as a JPEG or PNG in noticeably fewer bytes. In my own testing it lands roughly 25–30% smaller than an equivalent-quality JPEG, and it can do transparency like a PNG too. One format, both jobs, smaller files.
It manages that because it borrowed its compression tricks from video encoding — instead of storing every pixel from scratch, it predicts each pixel from its neighbours and only records the difference. You don't need to know the maths; you just get a smaller file for the same picture.
So why isn't everything WebP already?
Honestly, it's mostly habit and tooling. WebP works in every current browser — Chrome, Safari, Firefox, Edge — so the old "will it display?" worry is over for the vast majority of visitors. The real friction is everything around the browser: the photo someone emails you is a JPEG, the export button in their camera app says JPEG, and a lot of platforms still expect a JPEG on the way in.
So my rule is simple. For images you control on your own website, WebP is a great default and worth the switch. For files you're handing to someone else — an email attachment, a marketplace that's picky about uploads, an old internal system — stick with JPEG to avoid the "it won't open" support ticket.
Don't double-compress it
One trap worth naming: if you've already got a WebP that someone exported at low quality, squeezing it again just piles loss on loss, the same way re-saving a JPEG does. Whenever you can, compress from the original JPEG or PNG and export to WebP once. Going from a clean source straight to a well-tuned WebP gives you the cleanest result and the smallest file.
What this does for a real page
On an image-heavy page — a shop, a gallery, a long article — moving everything to WebP routinely strips a third or more off the total page weight. That's the kind of change you can feel: faster loads on mobile, a better Core Web Vitals score, and a page that doesn't hang while a hero image crawls in. It's rarely the only thing a slow site needs, but it's usually the easiest big win on the list.
The honest summary
Use WebP for images on your own site — it'll cut a third or more off your page weight. Keep JPEG for files you're sending to other people or uploading to systems that are fussy about formats.
Written by
Sanjay Sahani — Solution Architect
Sanjay Sahani is a solution architect with 21+ years building software. He created InstaShrink after one too many projects where “just compress the images” meant uploading client photos to a server he didn't control — so this tool does all its work inside your browser instead.
More about InstaShrink →