JPG to WebP — Free

Drop the JPG above and press Convert — the WebP downloads immediately. There is no account, no batch limit and no watermark, and the file is never uploaded, since conversion happens entirely in your browser.

Typically 25–35% smaller than the JPG at the same visual quality, and sometimes considerably more on photographs with large smooth areas like skies. Each file shows its before-and-after size after converting, so you can see the actual saving rather than a claimed one. Very small or already heavily compressed JPGs sometimes save little or nothing — at that point the file has already given up most of what there was to give.

A little, and it is worth understanding why. JPG is already lossy, so the WebP inherits everything the JPG previously discarded and then loses a small amount more when it is re-encoded — that is generational loss, and it cannot be undone by converting back. At Maximum quality the additional loss is not visible at normal viewing size, which is why this tool defaults high. What you cannot do is recover detail the original JPG had already thrown away.

Not through a browser, and this page will not pretend otherwise. WebP does support a genuinely lossless mode, but the canvas API browsers expose only produces the lossy variant, so setting quality to Maximum gives you a very high-quality lossy WebP rather than a mathematically lossless one. For a truly lossless WebP you need a desktop encoder such as cwebp. In practice, converting an already-lossy JPG to lossless WebP would preserve the JPG's existing artefacts at a much larger file size, so it is rarely what you actually want.

In browsers, effectively yes — Chrome, Edge, Firefox and Safari have all supported it for years, which is why it is safe to serve on a website today. Outside browsers it is patchier: some older desktop applications, print software and photo utilities do not open it. So WebP is the right choice for images going onto the web, and JPG remains the safer choice for files you are sending to someone else to open in unknown software.

For photographs, usually yes — it is one of the simplest ways to reduce page weight, and image weight is often the largest part of it. Two caveats. Keep the originals, since this conversion is one-way and you may want to re-encode differently later. And for logos, icons and line art, compare against PNG or SVG first, because WebP is not automatically better for flat graphics with sharp edges.

Yes. Add as many as you like and they all convert with the same quality and resize settings. The whole set downloads as a single ZIP, and each file also has its own download link if you only want one of them.

Yes. Tick "Limit the longest side" and give a pixel value — anything larger is scaled down proportionally, and anything already smaller is left alone. Converting and resizing together is usually the bigger win for a website, since serving a 4000-pixel photo into a 800-pixel slot wastes far more bytes than the format choice does.

No. Every image is decoded and re-encoded entirely inside your browser. Nothing is transmitted. That makes it safe for anything you would not upload to an unknown server — product photography before launch, client work, private pictures. Once the page has loaded it works offline.

Yes, as a side effect of how the conversion works. The image is redrawn from raw pixels and re-encoded, which does not carry metadata across, so camera details, timestamps and GPS coordinates are not present in the WebP. That is usually welcome for images going onto a public website.

No. The output is your image as a WebP, nothing added. There is no watermark, no badge, and no paid tier that removes one.