JPG to WebP converter
Convert JPG files to WebP inside this page. No upload, no limit on how many, no watermark.
- 0 uploads
- No limits
- No signup
- Works offline
This one is about page weight. If you run a website, the JPEGs are almost certainly the largest thing your visitors download, and WebP will carry the same pictures at roughly two-thirds of the bytes. It is the single cheapest performance improvement available to most sites — no redesign, no code change, just a smaller file at the same visual quality. Doing it in bulk is the point, which is why there is no limit on how many files go through at once.
When you actually need this conversion
- You are optimising a site or a blog and the image folder is the bottleneck in your page-speed score.
- You are preparing product photos, article headers or gallery images where the same picture is downloaded thousands of times.
- You want to keep a JPEG original as the fallback and serve WebP to browsers that accept it.
What to watch out for
- Re-encoding a lossy file with a lossy codec loses a little more. Convert from the highest-quality JPEG you have, not from one that has already been squeezed.
- Do not throw away the originals. If you ever need to re-export at a different size, you want the best source you still have.
- Anything outside a browser may not open the result — this is a delivery format, not an archive format.
JPG and WebP, side by side
| JPEG | WebP | |
|---|---|---|
| Released | 1992 | 2010 |
| Compression | lossy | both |
| Transparency | no | yes |
| Animation | no | yes |
| Support | everywhere, without exception | all current browsers; patchy outside them |
The most common optimisation for a website. Expect 25–35% smaller files at visually identical quality. Serve WebP with a JPEG fallback and older clients still work.
How the conversion works here
Your file is decoded in a Web Worker inside this browser tab — by the browser's own image pipeline where it can, and by a WebAssembly build of libheif or libavif where it cannot. The decoded pixels are then re-encoded with Google's libwebp, the same encoder Squoosh uses.
All of that happens on the processor in front of you. There is no upload step, no queue and no server, which is why there is no size cap, no daily allowance and no paid tier — and why the whole thing keeps working with the network switched off.
Doing more than one thing
Most people converting a format also need it smaller or a different size. The result screen hands your converted files straight to the compressor or the resizer in one click — no second download, no re-selecting files. If you need several formats, the general converter lets you pick the output each time.
How it works
- 01Add your JPG filesDrop them on the page, click to browse, paste from the clipboard, or drop a whole folder.
- 02Conversion runs on your deviceEach file is decoded and re-encoded as WebP by a WebAssembly codec in a background thread. Nothing is uploaded.
- 03Adjust if you need toMove the quality slider — 90 is visually indistinguishable from the source for most photographs.
- 04DownloadSave one file, or take the whole batch as a zip built on your device.