Convert JPG to WebP

• Decodes the JPEG and writes a lossy WebP at quality 80, which usually comes back lighter than the JPEG it was made from.
• Costs a second lossy generation, since the picture is compressed again rather than repackaged into a new container.
• Reports the real before and after byte counts, measured on your own file rather than quoted from an average.

• Does not change the pixel dimensions, so resize first if the photo is larger than it will ever be shown.
• Does not produce an animated WebP — one still frame goes in and one still frame comes out.
• Does not carry EXIF or GPS into the WebP, including the camera and location tags the JPEG was holding.

1. Choose the JPG on your device. Drop it onto the panel above or press Browse files. The pair is already set, so a file that is not a JPEG is refused at the drop.
2. Press Convert to WebP. Your device decodes the JPEG and writes a WebP at quality 80, at the same pixel dimensions. That is a second lossy generation, which is why you work from the best JPG you have.
3. Download the WebP. The panel prints the real before and after byte counts, so the saving is measured on your own file rather than quoted from an average.

WebP encodes the same picture with a more modern method than JPEG, and at a matched visual quality it typically lands 25 to 35 percent smaller. On a single photo that is a few hundred kilobytes. On a page carrying twenty of them it is the difference between a gallery that appears immediately on a phone connection and one that fills in while the visitor waits.

How much you actually get depends on the picture, not on the format alone. Smooth gradients — sky, water, skin, plain backdrops — compress far better than fine high-contrast texture such as foliage or crowds. The panel above prints the measured before and after sizes, so you can see the real number for your own file rather than an average from somebody else.

Support inside the browser has been settled for years: Chrome, Edge, Firefox, and Safari from version 14 in 2020 all display WebP without a fallback. If the image is going onto a web page, there is no compatibility argument left to have.

Outside the browser it is a different picture. Mail clients frequently show nothing at all, older desktop editors refuse to open the file, some content systems reject the extension on upload, and a few social platforms will not take it either. The rule that works: WebP for what you publish, JPG for what you hand to a person.

Your JPG has already been through one round of lossy compression. Converting it to WebP decodes it and compresses it again, here at quality 80. One extra round on a good-quality source is close to invisible; four rounds on a file that has been through a chat app and two re-saves is not.

So convert from the best original you hold, once, and keep that original. Treat the WebP as a delivery copy — the thing you upload to the site — rather than as the file you go back and edit.

Format is the smaller of the two levers. A 4000-pixel-wide photo displayed in a 900-pixel column is carrying more than four times the pixels it can ever show, and no encoder can compensate for that. Cutting the dimensions to what is actually displayed usually saves more than the format change does.

Do both, in that order: resize to the largest size the image will ever be shown at, then convert the result to WebP. A 4000-pixel JPG taken down to 1600 pixels and written as WebP routinely ends up a tenth of what it started at, with nothing visibly different on the page.

• This page takes one JPEG at a time, up to 20 MB, so a gallery is converted photograph after photograph rather than in a single pass over a folder.
• How much weight comes off depends on the picture: a busy, high-contrast frame can come back only slightly smaller, and the measured figures in the panel are the only reliable number.
• The longest side may not exceed 8000 pixels, and an image past that is turned down before any pixels are allocated rather than partway through the encode.