Convert JPG to WebP

How to convert JPG to WebP — 3 steps

1. 1

   Add your JPG files

   Drop in one image or a whole batch. Encoding runs on your own machine, so a folder of photographs converts as fast as your processor manages.

2. 2

   Choose the quality

   Around 80 is the usual balance for photographs. Because the source is already compressed, going much lower means paying the cost twice.

3. 3

   Download the WebP files

   Save the results and compare them against the originals at full size before publishing. Your JPGs are untouched.

What the conversion is actually worth

The gain is page weight, and on an image-heavy site it is substantial. WebP typically produces files 25–35% smaller than a JPG of comparable visual quality, because it uses a more modern compression method derived from video coding. On a page carrying twenty photographs that is the difference between a site that appears immediately and one that visibly loads in pieces — and since images are usually the largest thing a page downloads, it is the single most effective performance change available for most sites.

That saving matters beyond aesthetics. Page speed affects how many visitors stay, and it is a factor in search ranking; it also affects anyone on a metered or slow connection, where a heavy page is a real cost rather than an inconvenience. Performance auditing tools flag JPGs and recommend WebP almost universally, and this is why.

Support is settled. Every current browser decodes WebP natively and has done for years, so for images served over the web the compatibility objection no longer applies. The remaining gaps are outside the browser — email clients, older desktop software, and print workflows — which is why WebP is a delivery format rather than a replacement for your originals.

Compressing something that has already been compressed

A JPG has already discarded detail, and WebP compression will discard more. The two methods work differently, so the losses accumulate rather than cancelling — and WebP has to spend part of its budget reproducing the JPG's existing artefacts as faithfully as the picture itself. At sensible quality settings this is invisible; pushed hard it produces results noticeably worse than compressing the original photograph to the same size would have.

So convert from the best source available. If you still have the camera original or an uncompressed export, encode WebP from that and skip the intermediate step entirely. Where the JPG is all you have, keep the quality setting high, convert once, and avoid re-encoding the WebP again later.

Two practical notes. Keep your JPGs as masters rather than deleting them after conversion — WebP is what you serve, not what you archive, and you will need a widely compatible file the moment someone asks for the image by email or for print. And check the results at full size rather than in a thumbnail grid: smooth areas such as skies and studio backdrops are where a second round of compression shows first, as faint banding that a small preview hides completely.

Related tools