WebP vs JPG: what Google's format actually wins, and where JPG still rules

Google has spent fifteen years trying to retire JPG, and JPG is doing fine. That’s the strangest thing about the WebP vs JPG story: the newer format genuinely is better at its job, has shipped in every browser on Earth, serves a huge share of the images you see online, and still hasn’t replaced the format from 1992. Both facts have good reasons behind them, and they point to a clear answer about which one you should use.

Where WebP came from

WebP appeared in 2010, and its origin explains its personality. Google had just acquired a video compression company and realized that the technology for compressing a single video frame could compress a standalone image too. A WebP file is, in a loose but honest sense, one frame of video wearing an image format’s clothes.

Video codecs are ruthless about size because they have to be, and that ruthlessness carried over. Google’s own published testing found WebP files 25 to 34% smaller than JPGs of equivalent visual quality. Independent tests land in the same neighborhood. For a company serving billions of images a day, a quarter of the bandwidth is a fortune, which tells you exactly why Google built it and why nearly every large website now serves it.

What “smaller” actually costs

Nothing is free in compression, so it’s fair to ask what WebP gives up. At sensible quality settings, the honest answer is: very little you can see. Push both formats hard, though, and they fail differently. JPG breaks up into blocky, gritty artifacts that look damaged. WebP smooths instead, gently sanding away fine texture, so grass, hair, and film grain get subtly waxier. Neither failure mode matters at the sizes real websites use, but it’s why photographers with trained eyes sometimes grumble about WebP renditions of their work.

WebP also brings tricks JPG simply doesn’t have. It supports transparency like PNG, animation like GIF, and a lossless mode, all in one format. On paper it replaces three formats at once, which was precisely the pitch.

So why is JPG still everywhere?

Because compatibility is a feature, and JPG has thirty years of it. Every camera writes JPG. Every photo printer, government upload portal, ancient CMS, embroidery machine, and car infotainment system reads it. WebP’s browser support only became universal in 2020, when Safari finally joined, and browsers were the easy part. The long tail of software that touches images is enormous, and a meaningful slice of it still shrugs at WebP.

That’s how you get the modern absurdity: websites eagerly serve you WebP files that other websites then refuse to accept as uploads. Your browser saves a WebP, your photo editor or marketplace listing form rejects it, and now you’re searching for a converter. If that’s what brought you here, there’s a whole article on that saga, and a fix at the bottom of this page.

The practical decision

For images on a website you run, WebP is close to a free win: same visual quality, meaningfully smaller, universally supported in browsers. Converting JPG to WebP for web use is one of the cheapest performance upgrades available.

For everything else in your life, JPG remains the safe answer. It opens on every device you’ll ever hand a file to, no exceptions and no caveats. When a WebP lands on your disk and needs to go anywhere unusual, converting WebP to JPG ends the compatibility question permanently, and at a small size penalty you’ll never notice on a personal file.

And if the file has transparency, remember JPG can’t hold it: convert WebP to PNG instead, or the transparent areas will be flattened onto a solid background.

One thing neither format decides for you

Where the conversion happens. Most converter sites upload your image to their server, process it there, and send back the result, which means your file took a trip you didn’t need to authorize. Format conversion is pure local computation, and your browser is fully capable of it. The converter below decodes and re-encodes entirely on your device: nothing is uploaded, nothing is retained, there are no file limits, and you can run it in airplane mode to prove it. Drop a WebP in and watch it come back a JPG.