JPG to WebP Converter - Convert JPG to WebP Online Free

Convert JPG images to WebP directly in your browser, one at a time or in batches. The decoding and re-encoding both run locally, so nothing is uploaded to a server.

What JPG to WebP Does

This tool decodes each JPG onto an in-browser canvas and re-encodes the resulting pixel data as a WebP using the browser's own WebP encoder. Nothing is uploaded — the entire decode-and-re-encode cycle runs on your machine, so large batches and files you'd rather not hand to a server both stay local. The reason to do this at all is size: at a comparable perceived quality, WebP's lossy encoder generally produces files 25-35 percent smaller than JPEG's, which is why it has become the default format for images served on the web. There is one thing worth understanding before you convert anything important. A JPG is already the output of a lossy encoder — detail was discarded when the file was first saved — and re-encoding it as a lossy WebP runs the surviving pixels through a second round of lossy compression. The two passes stack rather than cancel out. The WebP encoder has no knowledge of the original detail; it only sees the artifacts the JPEG pass left behind, and it compresses those along with everything else. In practice this means keeping the Quality slider high, and not repeatedly converting JPGs that have already been compressed hard, since each pass compounds the softening and ringing around edges, text, and flat color boundaries. Two more limits follow from the source format. JPG has no alpha channel, so the WebP that comes out will be fully opaque — converting cannot create transparency that was never in the file. And conversion does not resample: the output keeps the same pixel dimensions as the input, only the encoding changes.

Why You'd Convert JPG to WebP

Almost always for page speed — the same image, meaningfully fewer bytes over the wire.

Cut image payload on web pages, the single largest contributor to slow loads
Improve Largest Contentful Paint by shipping smaller hero and above-the-fold images
Lower CDN and hosting bandwidth costs on sites that serve images at volume
Batch-convert an existing JPG asset library to WebP before a site migration or redesign

How to Convert JPG to WebP

Four steps, and the only decision you actually have to make is the quality level.

1

Add one JPG or drop in a whole folder — every file in a batch uses the same settings

2

Set the Quality slider; 92 is the default and keeps the second lossy pass close to invisible

3

Start the conversion — the button reads "Converting..." while the browser encodes each file

4

Download the WebP files individually, or grab the whole batch as a single ZIP

Frequently Asked Questions

For typical photographs at a comparable perceived quality, expect 25-35 percent smaller than the JPG. The real number depends on the source and the Quality setting. A JPG that was already saved at a low quality has little redundancy left to squeeze, so the saving is smaller — occasionally the WebP even comes out larger. Photos saved near maximum quality, and large images generally, tend to land at or above the top of that range.
Yes, a little, and it is worth being precise about why. Your JPG has already been through one lossy encode; converting it to a lossy WebP is a second one. The losses stack rather than cancel out — the WebP encoder cannot see the detail the JPEG pass discarded, so it compresses what remains, artifacts included. At Quality 92 the second pass is hard to spot on ordinary photos. On screenshots, text, and hard-edged graphics, or at low quality values, it shows up as softening and ringing along edges.
The default of 92 is a sensible starting point: visually very close to the source on photographs while still delivering most of WebP's size advantage. Drop to around 80 when bytes matter more than fine detail, such as thumbnails or long-scroll listing pages. Stay at 90 or above for hero images, product photography, and anything containing text. Below roughly 70 the second lossy pass becomes clearly visible, especially where the JPG was already compressed hard.
All current browsers support WebP, as do most modern image viewers and design tools. The gaps are at the edges: some older desktop software, certain print and prepress workflows, a number of legacy content management systems, and a few email clients that reject or fail to render the format. If the file is going somewhere you don't control — a printer, a client, a form uploader — JPG remains the safer choice. Convert to WebP when you know the destination handles it.
You can, and this site has a WebP to JPG tool for exactly that, but it is not a round trip. Going JPG to WebP and back means three lossy encodes on the same pixels, and each one degrades the image further. The returned JPG will also usually be larger than the original, since JPEG is the less efficient encoder. Keep your original JPGs archived rather than planning to reconstruct them from converted WebP files.
No. WebP supports an alpha channel, but JPG does not, so there is no transparency in the source for the converter to carry over. Every pixel in the output is fully opaque. Converting to WebP cannot add transparency any more than it can add detail — if you need a transparent background, that has to come from a source file that already has one, such as a PNG, or be created in an editor before conversion.
No. The JPG is decoded and the WebP is encoded entirely inside your browser using the canvas API, so the image data never leaves your device. There's no upload step, no account, and no server-side storage. The practical trade-off is that very large batches are bounded by your machine's memory and CPU rather than by an upload limit, and the tool keeps working even if you go offline after the page has loaded.
Yes. Add as many files as you like and they all run through the same Quality setting in one pass, then download them individually or as a single ZIP. One caveat: a single quality number lands differently depending on content, so a detailed photo and a flat illustration at the same setting will not degrade equally. Spot-check the most detailed file in a batch before trusting the rest of the run.

Plus d'outils d'image

Explorez d'autres outils puissants pour vos besoins d'édition