Convert a JPG to WebP to keep the same photo at a smaller file size for the web. Free online, no signup. Part of the image converter.
Drop images or browse
JPEG · PNG · WEBP · AVIF · HEIC · up to 50 at once · max 30 MB each
Auto tunes each image.
A hard cap for the number your form demands.
A floor for forms that refuse small files.
Empty side keeps the ratio. Never enlarges.
More image tools
JPEG · 74 KB
WebP · 19.2 KBJPG to WebP converter
Free, in your browser, with no sign-up. Each step below is the real tool on this page.
Up to 10 JPG files at once. WebP is already picked.
Auto picks the best WebP setting. A size cap is never exceeded.
See each measured size, then drag the slider to check the look.
Take each file on its own, or all of them together in one ZIP.
Free, no sign-up
Up to 10 JPG files at once, every result measured to the byte, and nothing kept after you leave.
Fast and easy
WebP keeps the look of a JPG photo in far fewer bytes, so pages load faster. This photo went from a 846.3 KB JPG to a 177.9 KB WebP, 79% smaller.
Why this converter
Every size on this page is a file the engine wrote, measured to the byte.
Batch
Convert up to 10 JPG files to WebP in one run. Each file shows its own measured size, so you see what changed.
Quality
This photo went from a 300.2 KB JPG to a 46.5 KB WebP. Check any file at full size before you keep it.
Exact size
Set a maximum size and the converter finds the best quality that fits. A hard cap: at or under it, never over.
Compress image to 100 KBOur own benchmark
Everyone quotes Google's range. Nobody shows their own numbers. These are ours, and every byte count below is a real encoded file, not an estimate.
| Encode | Relative to source | Size | vs source JPEG |
|---|---|---|---|
| WebP (Auto)Our default | 218.9 KB | −62% | |
| WebP (quality 80) | 262.3 KB | −55% | |
| WebP (quality 90) | 416.5 KB | -28% | |
| AVIF (Auto), for comparisonOther format | 123.9 KB | −79% |
Source: photo.jpg, 576.8 KB, the reference image. Every row is the file the engine wrote from that one JPEG.
Every byte count is the size of the actual file our engine produced from the named source, the same bytes you would download, not an estimate. The reference photo is one of our own photographs, an iguana on a branch, and the camera photo is a real one too. Drop your own file into the tool above to rerun any of them. How we measure names the sources and the settings.
One-off migration
Three steps, then two decisions. Filenames are preserved through the whole flow, so re-linking is mechanical rather than manual.
Format choice
The same source file, both formats, measured the same way. AVIF is simply the smaller format now, and support is close enough that you do not have to choose.
Two points of browser support separate them. That gap is exactly what the fallback beside this is for.
The browser takes the first source it understands and stops.
<picture>
<source srcset="photo.avif" type="image/avif">
<source srcset="photo.webp" type="image/webp">
<img src="photo.jpg" alt="Sunlit desk">
</picture>The JPG stays as the last resort, so no visitor is left without an image.
JPG to AVIFKnow when to stop
Three cases where the honest advice is to leave the file alone.
The JPEG was already well-compressed. A format change for single-digit savings is not worth the re-encode, the re-linking, or the second lossy generation.
Office suites, email clients and print pipelines still expect JPEG. WebP is a web-delivery format, so keep JPEG for interchange.
Encode WebP from the original, not from the JPEG. That is one lossy generation instead of two, and the saving is usually larger.
Compress JPEG shrinks the file and keeps the format every app opens: same engine, same caps.
JPG to AVIF goes further than WebP, often well under half the JPG, for the same look.
WebP to JPG turns it back into a file that every editor, email and phone accepts.
Short answers specific to this page. The tool above settles most of them in a second.
Still have a question?
Ask us. A person reads it.
Page updated
Every route in and out runs on the same engine and the same rules. Each card is its own page.
Freeze the current pixels. Lossless from here, and the right move before editing or archiving.
Roughly half the bytes of WebP on most photos. Slower to encode, worth it at scale.
Keeps the alpha channel and still cuts real weight. The least disruptive way off PNG.
The universal handoff. Anything that opens an image opens this: print, email, old software.
Keeps transparency for editors and pipelines that won't read WebP. Bigger file; quality 100 adds no further loss.
One more step down the size curve for pages already on modern formats. Keep WebP as the fallback.
Every rating counts in the average, low ones too. We remove only spam, abuse and fakes.
Average rating
5.0
15 ratings, 6 written
One tap. No account needed.
Drop it in above. The meter reports the exact saving before you download anything.
Get Pro