Convert JPG to WebP
Drop your JPG photos below, keep quality 80 and download WebP copies that are usually much lighter for the web. Each photo is decoded and re-encoded in this tab. 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 one or more
.jpgor.jpegfiles into the box above, or click it to choose them. - Leave quality at 80 for ordinary photos. Raise it to 85–90 for a large hero image or a product shot where people will zoom in.
-
Compare the two sizes on each result row —
photo.jpgbecomesphoto.webp— and download the ones that are worth it.
Searching for “JPG to web”? You are probably after a photo that loads faster on a website. WebP is the format built for exactly that, and every current browser shows it.
What the conversion does to file size
We ran the same encoder this page uses, at the same default quality, on test images our measurement script draws pixel for pixel, so the numbers can be reproduced exactly. They are synthetic, not your photos: read them for the pattern, and trust the sizes the tool shows you for your own files.
| Test image | JPG | WebP | Change |
|---|---|---|---|
| Landscape photo, JPG saved at quality 90 | 253.8 KB | 93.1 KB | −63% |
| Same photo, JPG saved at quality 75 | 135.2 KB | 92.7 KB | −31% |
| App screenshot saved as JPG (quality 90) | 170.7 KB | 49.5 KB | −71% |
The lesson is in the first two rows. Both WebP files are almost the same size, because the encoder is describing the same picture. What changes is how much fat the JPG was carrying: a camera-quality export has plenty to lose, a JPG that was already squeezed has much less.
| Quality | WebP size | Versus the JPG |
|---|---|---|
| 60 | 60.5 KB | −76% |
| 70 | 68.9 KB | −73% |
| 80 (default) | 93.1 KB | −63% |
| 90 | 155.1 KB | −39% |
The honest cost: a second round of compression
A JPG is already lossy, and so is the WebP this tool writes. Converting one into the other means the encoder works from the JPG’s pixels, artefacts included, and makes its own compromises on top. We measured that drift with PSNR, a standard score of how far a copy has moved from the original in decibels (higher is closer). Against the lossless master our photo was made from, the quality-90 JPG scored 41.1 dB and its WebP 38.1 dB; the quality-75 JPG scored 39.1 dB and its WebP 37.4 dB.
That gap is small enough to be hard to see at normal size, but it only goes one way. Two habits keep it small: convert from the best copy you have (the camera file or the original export, not a JPG that has already been through a chat app), and do it once. Re-converting a WebP back to JPG and then to WebP again stacks the loss each time.
When WebP is the right call, and when to keep the JPG
- Convert photos for a website, online shop, blog or portfolio. Images are usually the heaviest part of a page, so lighter files help it load faster on phones.
- Convert before uploading to a site builder or CMS that keeps your file as-is instead of optimising it for you.
- Keep the JPG for photos you email, print or hand to someone whose software you do not know. JPG opens everywhere.
- Keep the JPG as your archive copy. Treat the WebP as the delivery version you can always regenerate.
If your site template supports it, a <picture>
element can offer the WebP first and fall back to the JPG for the rare
visitor whose software cannot read it.
Frequently asked questions
Are my JPG files uploaded anywhere?
No. Your browser decodes each JPG and a WebAssembly build of libwebp, Google’s own WebP encoder, writes the WebP inside the tab. The page itself, the encoder download and the ads make ordinary network requests, but your photos are not sent with any of them.
Can every browser open WebP in 2026?
Current Chrome, Edge, Firefox and Safari all display WebP, on desktop and on phones; Safari was the last to join, with version 14 in 2020. Where WebP still trips people up is outside the browser — some older desktop editors, office suites and upload forms reject it. For a website that is rarely a problem; for a photo you are emailing to someone, JPG is still the safer file.
What does the quality slider actually mean?
It is libwebp’s lossy quality setting from 1 to 100, not a percentage of the original. Lower numbers let the encoder discard more fine detail. On our test photo, quality 60 gave a 60.5 KB file and quality 90 a 155.1 KB file, from the same 253.8 KB JPG. 80 is the default as a sensible starting point for photographs; open the result and step up if you see blur in fine texture or sharp edges.
Is WebP always smaller than my JPG?
No. How much you save depends on how hard the JPG was already compressed. In our test the same photo shrank 63% when the JPG had been saved at quality 90, but only 31% when it had been saved at quality 75. Every result row shows both sizes; if the WebP is barely smaller, keep the JPG.
What happens to EXIF data, GPS and orientation?
They are not copied. The new file is built from decoded pixels only, so camera model, date, GPS position and any embedded colour profile are left behind. Current browsers apply the rotation flag while decoding, so the picture itself should come out upright even though the flag is gone. Keep the original JPG if you need that metadata.
Can I convert a whole folder of JPGs?
Select all the files inside the folder and drop them in together; each one is converted separately at the quality you set and gets its own download. Dropping the folder itself does not work in every browser. Very large batches are limited by your device’s memory, not by a quota on our side.