Hacks VitaeAll tools
freecompressconvert
client-side only

JPG to WebP

Smaller images for a website, converted in this tab. The tool shows you the before and after size for every file, so you can see the ones where it was not worth it.

· PNG, JPG, WebP, GIF, BMP

A whole folder at once is fine. Nothing is uploaded.

Files0
In0 B
Out0 B
Change–
No upload
Output format
How to decide the size
    Quick answer

    Worth doing for a website, with one caveat

    // Answer

    For images served by a web page, yes: WebP is usually meaningfully smaller than JPG at the same measured quality (Google reports 25 to 34 percent). The caveat is that you are compressing an already compressed file. If you still have the original photograph, converting that directly gives a better picture at the same size than going through the JPG.

    Worth knowing

    Some of the saving is just more loss

    When a 400 KB JPG becomes a 260 KB WebP, it is tempting to read that as free. It is not entirely free. Part of the difference is WebP being a better codec, and part of it is a second round of approximation removing detail the JPG had kept.

    This matters in two situations and in no others. If the image will be enlarged, cropped into, or printed later, start from the original. If it is a hero image or a photo gallery where quality is the point, start from the original. For an ordinary page image at ordinary size, going JPG to WebP is perfectly fine and you should not lose sleep over it.

    What you should not do is run the file through repeatedly, or re-encode an image that has already been through three tools. Each pass takes a little more, and none of it comes back.

    Watch for this

    When WebP comes out bigger

    It is not universal. A JPG that was already compressed hard can produce a WebP that is larger than the file you started with, because the WebP is saved at a higher quality setting than the JPG was. WebP wins on average, not always. One more limit: Safari cannot save WebP from a web page, so in Safari the converter says so instead of saving a file; use Chrome, Edge or Firefox for this one.

    The tool prints both sizes for every file. When the new one is bigger, keep the original — there is nothing to gain. To see where the real boundary sits for the kind of pictures you work with, the format benchmark encodes your own files at every quality setting and shows you the point where the file starts growing faster than the picture improves.

    Related

    If your images started somewhere else

    Photos straight off an iPhone are HEIC, and converting those to WebP directly avoids a pointless trip through JPG — HEIC to WebP does it in one step. Artwork and screenshots are usually PNG, which converts to WebP with the transparency kept. And if you are going the other way because a WebP will not open, WebP to JPG is the page you want.

    FAQ

    Frequently asked questions

    No. The JPG is already an approximation, and WebP makes a second approximation of it. The result is smaller and slightly further from the original photograph than the JPG was. At a high quality setting the difference is invisible, but it is real and it accumulates if you keep re-encoding.
    Because for a website the trade is usually worth it: meaningfully smaller files, pages that load faster, and a visual difference nobody notices. The recommendation is sound. What is usually left out is that converting from the original photograph rather than from a JPG gives you a better result for the same file size.
    It happens most with images that were already compressed hard. WebP is not smaller than JPG in every single case, only in most of them. When a file comes out larger, keep the JPG — the tool shows you both sizes so you can see it.
    No. Keep the best copy you have as the master and treat WebP as a derivative for delivery. If you later need a different size, a different format, or a print, you want to start from the best original available rather than from a twice-compressed file.
    You can, but they may not be able to open it. WebP is reliable in browsers and less dependable outside them. Anything going to a person rather than onto a web page should stay a JPG.

    Ask an assistant about this page

    Opens in a new tab with this page and the question already filled in.