saveas.now

JPG to AVIF for the lightest image pages

Roughly half the bytes of the JPG at matching visible quality. Worth it where load time is money.

Runs in your browser. Your file never leaves your computer.

Drop files hereor click to choose, or paste

Where WebP shaves a quarter off a JPG, AVIF tends to cut closer to half, and on some photographs more. For sites where images dominate the transfer and conversion time is not precious, migrating JPGs to AVIF is the strongest single optimisation available. As a lossy-to-lossy conversion it works best from good-quality sources rather than already-crunched thumbnails. Encoding runs in your browser and takes its time; large images may want patience.

IdenticalNoticeably degradedWhat most listeners or viewers notice
At half the size of the source JPG, AVIF output typically sits indistinguishably close on this scale; aggressive settings move it right.

Questions

Is re-encoding my JPGs going to look worse?

Marginally in theory, invisibly in practice at the default quality. Encoding from original masters, where they exist, sidesteps even the theory.

Should I keep JPG fallbacks?

For a general audience, serve AVIF via the picture element with a JPG or WebP fallback; old browsers pick the fallback automatically.

Why so slow to encode?

AVIF spends computation to earn its compression. It is a one-time cost per image, paid on your machine, not a server's.

All images conversions

Part of convert images in your browser. Every other conversion is on the conversions index.