Home/JPG to WebP
100% local · nothing is ever uploadedConvert JPG to WebP
Drop your JPG files below for an instant size cut — WebP typically comes out 25-35% smaller at the same visual quality, with nothing uploaded and no account needed. A whole batch runs just as easily as one photo.
Drop your images here
or browse files
JPG, PNG, WebP, AVIF, or HEIC (Safari only) · processed locally · never uploaded · paste with Ctrl+V also works
No images yet. Drop some above to get started.
Why convert to WebP?
At the same visual quality, WebP files typically come out 25-35% smaller than the equivalent JPG. Every modern browser has supported it for years, so there's no compatibility tradeoff to weigh — it's a straightforward swap that makes a page full of photos load faster.
Converting an already-lossy JPG into WebP is technically a second lossy pass, so a small amount of extra degradation is unavoidable in the strictest sense — but at a reasonable quality setting it's not something you'll notice at normal viewing size.
How to convert JPG or PNG to WebP →How much smaller, in practice
The usual figure is 25-35% off the JPG at matched visual quality, and for most photographs it holds. The gain comes from WebP's newer compression finding redundancy JPG's cannot, not from discarding more detail — matched quality means the two genuinely look the same.
Where you'll save less: a JPG that was already compressed hard has little redundancy left to find, so a heavily optimised one might give up only 10-15%. And very small images can come out slightly larger, because WebP's per-file overhead stops paying for itself below roughly 40 pixels a side.
It's a second lossy pass
A JPG has already thrown detail away. Converting it to WebP encodes what's left a second time, so in the strictest sense a little more is lost — you are not converting from a pristine original, and nothing can change that.
In practice, at a sensible quality setting, it isn't visible at normal viewing size. The honest framing is that this is a good trade, not that it's free. If you still have the original uncompressed image, converting that directly gives a cleaner result than going through the JPG.
Doing a whole folder at once
Drop as many files in as you like — the queue runs them one after another and hands back a ZIP, and because everything happens in your browser there's no upload wait and no per-file limit imposed by a server.
The practical ceiling is your own device's memory. Several hundred photos at once on a phone is asking a lot; splitting a very large batch in two is usually quicker than watching one tab struggle.
FAQ
Is WebP supported everywhere I might need it?
Every modern browser displays WebP without any plugin or setting, and has for years — Chrome, Firefox, Safari, and Edge all support it natively. The exceptions tend to be older, specific tools: some email clients, a handful of CMS platforms, and print software still expect JPG or PNG.
Can I convert a WebP file back to JPG later?
Yes — img-compress's WebP to JPG converter handles that the same way, entirely in your browser. Converting to WebP isn't a one-way trip.
Do I need an internet connection for this to work?
Only to load the page the first time. The conversion itself runs entirely offline in your browser after that, so nothing is sent anywhere even on a spotty connection.