JPG to WebP Converter

WebP is a newer format than JPEG with a better compressor behind it. At the quality levels websites actually use, it stores the same photograph in roughly a quarter to a third fewer bytes — which is why page-speed audits keep suggesting it. This page converts one JPG at a time, shows you the before and after sizes so you can see the saving on your own file, and lets you adjust the quality until you are happy with the trade.

The encoding uses your browser’s own WebP encoder, which is checked before the option is offered. Nothing is uploaded, and the size you see is the size you download.

1. 1Drop the JPG. The bytes are checked to confirm the format, the original size is shown, and any EXIF rotation is applied so the WebP comes out upright.
2. 2The encoder is verified. The page asks the browser to encode a tiny WebP test image. Only if that produces a real WebP is the conversion allowed to run.
3. 3Set the quality. The default is 88. Moving the slider re-encodes the image and updates the output size, so you can find the point where the saving stops being worth it.
4. 4Compare. The before and after previews sit side by side with their sizes. Compare a busy, detailed area in both to judge the quality yourself.
5. 5Download. The file keeps its name with the extension changed to .webp.

Quality

1 to 100 in lossy mode. WebP degrades more gracefully than JPEG at the low end, so 75 in WebP often looks better than 75 in JPEG.

Lossless WebP

Stores every pixel exactly and hides the quality slider. For a JPG source this usually produces a file larger than the original; it is here for completeness, not as a recommendation.

Output

Fixed to WebP. The switcher above the article leads to the JPG-to-PNG and WebP-to-JPG pages if you need a different target.

Unexpected input

A PNG or WebP dropped here still converts. A WebP source is renamed with a “-converted” suffix so the original is not overwritten.

• Compatibility is broad but not universal. A few older applications, email clients and upload forms still refuse WebP; keep the JPG if the destination is outside your control.
• Re-encoding is lossy. JPEG artefacts already in the source are carried into the WebP and a little more detail is lost on top. Converting from the original RAW or PNG, if you have it, gives a better WebP than converting from a JPG.
• Lossless WebP of a photograph is a large file. Use it for graphics, not for this.
• Metadata is dropped. The WebP has no EXIF, GPS or colour profile.
• The WebP option only appears where the browser proves it can encode it. This is nearly everywhere, but not guaranteed.
• Images over roughly 100 megapixels are refused because the canvas cannot usually be allocated.

A 1920 × 1080 JPG exported at quality 85 weighs around 620 KB. Dropped here at the default quality of 88 it typically comes out between 380 KB and 450 KB with no difference a visitor would notice. Pulling the slider to 80 usually gets it under 350 KB; the readout shows the exact figure for your file at each step.

When you have a whole folder of hero images, the batch converter applies one quality setting to all of them and returns a ZIP. And if you need the WebP to hit a specific byte budget, the compressor can search for it with WebP as the output.

• See the saving before you commit

  The before and after sizes are both real encoded byte counts, updated as you move the quality slider.

• Encoder verified, not assumed

  The WebP option is only offered after the browser passes a real encode test, so you never download a file that is secretly a PNG.

• No upload

  A single conversion finishes in the time an upload would still be showing a progress bar.

• Side-by-side preview

  Original and WebP sit next to each other so you can judge quality with your own eyes rather than trusting a number.

• Honest when it grows

  If the WebP comes out larger — a heavily compressed source, or lossless mode on a photo — the readout says so.

• No account, no watermark

  Nothing gates the download and nothing is added to the image.

It is decoded in this tab and encoded as WebP on your device. No upload request is made to convert it, nothing is stored in local storage or a cache, and the decoded pixels are released when you load another file or close the page.

The page sets no cookies and loads no analytics. Like any web page it is delivered by a server that can log the page request itself; the Privacy Policy describes what that covers.

PixelEditor is a small set of single-purpose image tools that run inside your web browser. Each one does a specific job — resize, crop, rotate, compress, convert, inspect, strip metadata — and each one has its own page so you can bookmark exactly the tool you keep needing.

The tools are built with the Canvas API and Web Workers. When you pick a file, the browser reads it from your own disk, works on it in memory, and hands you the result back as a download. There is no processing server involved, so there is no upload step, no queue, and no account.

Everything is free, there are no watermarks, and there is no paid tier that unlocks the real version. Read more about how PixelEditor works and why.