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
Why the savings are so large
JPEG's compression model dates from 1992; AVIF's arrived nearly three decades later with far better prediction of photographic content. At matched visual quality AVIF files are typically a small fraction of their JPG equivalents, and the gap widens on images with smooth gradients and soft focus, where JPEG artifacts appear earliest.
As with any lossy-to-lossy conversion, the source has already lost information once. Convert from your best available original, and judge results by looking at them — the result view gives exact byte numbers per file for the size half of the decision.
Where AVIF fits in a fallback chain
Current browsers handle AVIF, but long-tail devices, older operating systems, and much desktop software do not. The standard pattern is a picture element offering AVIF first, WebP second, and JPG last. That ships the smallest file each visitor can decode while abandoning nobody.
Encoding AVIF is slower than encoding JPG — that cost lands on this tool rather than your visitors, but budget for it in large batch runs.
Practical notes
Batches accept up to 50 JPGs at 40 MB each. Files upload privately, results expire after two hours, and if any single conversion comes out larger than its source, it is reported as an increase, never as a win.