Convert image formats
Pick a target format, then add images. Converting to a heavier format can grow the file; the result view reports the byte change either way.
- Up to 50 files
- 40 MB each
- Deleted after 2 hours
What changes between JPG and WebP
Both formats are lossy and both target photographs, but WebP's newer compression predicts image content more effectively, so it reaches the same visual quality with less data. Savings vary by image — smooth portraits compress differently from busy landscapes — which is why per-file byte reporting matters more than headline percentages.
One honest caveat: converting a JPG re-encodes pixels that were already lossily encoded once. At sensible quality settings the added loss is rarely visible, but always convert from the best source you have, never from a copy of a copy.
Compatibility in 2026
Every modern browser, including Safari, has shipped WebP support for years. The stragglers are elsewhere: some older email clients, desktop software, and enterprise systems still want JPG. Serve WebP on the web, and keep JPG copies for channels that require them.
A sensible batch workflow
Gather your originals, convert up to 50 at a time, and compare a handful of results at 100% zoom before rolling the change across a site. Files upload privately and are permanently deleted after two hours, so download the results you want to keep. If a specific image comes out larger — rare, but possible with already-tiny JPGs — the tool says so plainly.