Convert JPG to WebP in your browser
The same photograph, in the format every current browser prefers and every performance audit asks for. Converted on this device, with nothing sent anywhere.
or browse your device. Everything is processed on this device
No JPG to hand?
How to convert JPG to WebP
A whole folder of them if you are converting a site. Nothing is uploaded, so a hundred files cost nothing extra.
Almost always a bigger win than the quality slider. Match the widest the image is ever displayed at rather than shipping the camera original.
Keep the JPG as a fallback if you are serving with a picture element, which is still the safest way to ship WebP.
Converting a JPG that is already lossy
Start with the size question, because the usual answer is misleading. "WebP is 25 to 35% smaller than JPEG" is Google's figure, measured against baseline libjpeg. Against a modern JPEG encoder the gap is much smaller: the sample photograph at quality 80 came out 528KB as WebP and 544KB through mozjpeg, which is about 3%, and at quality 85 the WebP was actually larger. What you will usually see on your own files is a big saving, because a camera or export-tool JPG is rarely encoded efficiently, and most of that saving is the re-encode rather than the format.
The thing to keep in mind is that you are re-encoding, not encoding. Your JPG has already had detail discarded, and WebP is now making its own decisions about what to discard from what is left. Two lossy passes compound in a way that one does not, and it shows up first in flat areas like skies, which pick up faint blotching. That is why the quality here starts at 84 rather than the 80 the WebP compressor uses on a fresh source.
If you still have the originals, converting those directly to WebP will beat converting the JPGs, and by more than any setting on this page. If you do not, run this at a generous quality and check a sky before you convert three hundred files.
JPG to WebP FAQ
How much smaller will it be?
It depends entirely on how well your JPG was encoded. Against an unoptimised camera or export JPG, often most of the file. Against a JPG already squeezed by a good encoder, single digits at matching quality, and sometimes nothing at all. Downscaling to the width you actually display is a larger and more reliable saving than the format change, so do that first.
Will the quality drop?
Slightly, and unavoidably. A JPG is already lossy, so this is a second lossy pass and the two compound. At the default of 84 it is invisible at normal viewing size. Flat areas like skies are where it shows up first, so check one of those before converting a batch.
Should I convert my originals instead?
Yes, if you still have them. Encoding once from a lossless original beats encoding twice, and by more than any setting here can recover. This page is for the very common case where the JPGs are all that is left.
Do I still need the JPG?
Keep it if you are serving with a picture element and a fallback, which is still the safest way to ship WebP, and if anything else in your workflow refuses the format. Every current browser reads WebP; plenty of desktop software does not.
Are my JPG files uploaded to convert them?
No. The JPG is decoded and the WebP is written by your own browser, in this tab. There is no upload endpoint in the site for a file to go to, which you can check in your network tools: convert something and watch that no request carries it. Disconnect from the network after the page loads and it still works.
Does this remove EXIF, GPS and AI metadata?
Yes, every time, and there is no way to turn it off. The image is decoded to pixels and encoded again from those pixels alone, so EXIF and GPS, the XMP packet, embedded colour profiles, and any Content Credentials or AI-generation tags the file arrived with do not survive. There is no switch for this, because there is no way to keep them. What no compressor can remove is a watermark written into the pixels themselves, such as the invisible marks some image generators add: those survive re-encoding here and everywhere else.
Related
Same format joins the queue. Anything else re-routes to its own tool.