Convert JPG to WebP
Turn JPG photos into lighter WebP files for the web — right here in your browser. Your images are never uploaded.
Drop JPG files here or click to choose
Converted on your device — never uploaded
How to convert JPG to WebP
- Drop your JPG files into the box above, or click it to pick files.
- Pick a quality. 80 suits most photos; raise it to 85–90 for large hero images.
-
Download each result —
photo.jpgbecomesphoto.webp.
Why move photos from JPG to WebP?
JPEG was standardised in 1992 and has aged remarkably well, but WebP was designed two decades later with the same job in mind and simply does it more efficiently. For the same perceived quality it needs roughly a quarter to a third fewer bytes, which on an image-heavy page is often the difference between a fast site and a slow one.
It is worth being clear about the scale of the win: the dramatic 90%-smaller numbers you see quoted for WebP come from converting PNG, not JPG. Going from JPG, a 25–35% reduction is the honest expectation — still very much worth having, and free of any visible cost at sensible quality settings.
Lossy or lossless WebP?
| Mode | Good for | Result on a JPG photo |
|---|---|---|
| Lossy (used here) | Photographs, screenshots of photos | 25–35% smaller than the JPG |
| Lossless | Logos, icons, flat graphics, line art | Several times larger than the JPG |
Because a JPG is by definition already lossy, there is nothing pristine left for lossless mode to protect — it would only spend bytes preserving the compression artefacts. This tool therefore uses lossy WebP, with the quality slider deciding how much detail to keep.
Frequently asked questions
Are my JPG files uploaded anywhere?
No. Encoding runs in your browser with a WebAssembly build of libwebp, Google’s own WebP encoder. The photos stay on your device from start to finish.
How much smaller will the WebP be?
At the same visual quality, WebP is typically 25–35% smaller than JPEG for photographs. That is a real saving on a page full of images, but it is a smaller jump than PNG to WebP, because JPEG is already a lossy format doing a decent job.
Which browsers support WebP?
Every current one. Chrome, Edge, Firefox, Safari and their mobile versions have all supported WebP since 2020, and it is around 96% of global browser traffic. The remaining gap is old software rather than old browsers — some desktop editors and office suites still refuse it.
Is converting JPG to WebP lossy?
Yes, at the default settings: the JPG is decoded and re-encoded with WebP’s lossy mode, so it is a second generation of lossy compression. In practice that is invisible at quality 80 and above. WebP also has a lossless mode, but using it on a photo produces a file far larger than the JPG you started with, so it is not what this tool does.
Does re-encoding an already compressed JPG hurt quality?
A little, in theory. Pushing the quality slider to 85–90 keeps the loss below what anyone can notice while still landing well under the original file size. If you are working from a high-quality original, converting that instead of an already-compressed export gives the cleanest result.
What quality setting should I use?
80 is the sweet spot for photographs on a website. Use 85–90 for hero images, product shots or anything with visible detail in shadows; 70 is fine for thumbnails and background images where size matters more.
Should I serve WebP to every visitor?
On a modern site, yes — and keeping the original JPG as a fallback in a picture element costs nothing. WebP is one of the easiest wins for Largest Contentful Paint and Core Web Vitals scores because images are usually the heaviest thing on the page.