Can I compress an AVIF without losing quality?

Not meaningfully — this page produces lossy AVIF, so smaller means less detail. AVIF's advantage is that the detail it discards is considerably harder to notice than in older formats.

How low can I set the quality?

Further than you would expect. AVIF degrades gracefully, so settings around 50 to 60 often remain perfectly acceptable where the same value in a JPG would look obviously damaged. That is where the largest savings live.

Why is compressing so slow?

Because AVIF encoding is slow by design. The codec searches a large space of possible encodings, and that search is exactly what produces the small file. It runs in a Web Worker so the page stays responsive.

Why did quality 82 produce the same size?

Because your source was probably already encoded at around that setting. Re-encoding at a file's existing quality reproduces the same detail and therefore the same size.

Does moving the slider repeatedly degrade the image?

No. Each adjustment re-encodes from your original file rather than the previous result, so there is no generational loss.

Is transparency preserved?

Yes, including partially transparent pixels. AVIF also carries HDR and wide colour gamut, which survive where the source has them.

Is my image uploaded?

No. Decoding and encoding both run in this browser tab. The Uploaded readout beside the result measures the page's own outbound traffic, so a successful run reads 0 B.

Is there a file size limit?

None imposed. Large images take longer to encode rather than being rejected.

Will there be a watermark?

No. Nothing is added to the image and nothing is paywalled.

Should I resize instead of compressing?

Resize first, almost always. File size scales roughly with pixel count, so serving an image at the size it is actually displayed usually saves more than any quality setting.

Compress an AVIF

Shrink an AVIF further, watching the size as you go. Nothing is uploaded, so there's no limit on what you can compress.

ReadyAVIF → AVIF

Uploaded0 B

How do I make an AVIF smaller?

To compress an AVIF, drop it onto this page and lower the quality slider until the size readout shows a figure you can accept. Everything runs in your browser, so nothing is uploaded. AVIF degrades gracefully, so settings that would look damaged in a JPG often remain perfectly usable here.

How to do it

Add your AVIF. Drag it onto the panel or click to choose. The first result appears at the default quality of 82.
Lower the quality slider. Drag it down and release. Go further than you would with a JPG — AVIF holds up at settings that would visibly damage older formats.
Read the size. The readout updates after each re-encode. Keep going until the number is where you need it to be.
Download when it fits. Your original is never modified, so a setting you regret costs nothing but another attempt.

At a glance

Converts	AVIF to AVIF
Transparency	Preserved
Compression	Lossy — quality is adjustable, default 82
Where it runs	In this browser tab. The file is not uploaded
File size limit	None imposed — your device memory is the ceiling
Cost	Free
Account needed	No
Watermark	None
Works offline	Usually after first use, but not guaranteed — there is no offline app

Compressing the most compressed format

AVIF is already the most aggressive compression in common use, so the first question is whether anything is left to take.

Often there is — because AVIF degrades unusually gracefully. Quality settings that would leave a JPG visibly blocky frequently leave an AVIF looking fine. That means the useful range extends much lower than habit suggests, and habit is calibrated on JPG.

If you normally stop at 80, try 60 here and look at the result before assuming it is too far.

Why quality 82 may change nothing

If your source was already encoded at around 82, re-encoding at 82 reproduces the same amount of detail and therefore roughly the same size.

That is the encoder working correctly rather than failing. To get smaller you have to go below whatever the source used — and since you generally cannot tell what that was, the size readout is the only reliable guide.

Resize before you compress

Worth saying because it is the larger lever and it is routinely skipped.

File size scales roughly with pixel count. An image displayed in a 600-pixel column does not need to be 3000 pixels wide, and serving it that way wastes far more bytes than any quality setting can recover.

Resize it first, then compress. In that order.

Expect it to be slow

AVIF encoding is the slowest operation on this site, and compressing means encoding again.

The slowness is the mechanism working: the codec is searching for an efficient encoding, and that search is what produces the small file. It runs in a Web Worker, so the interface stays responsive while it works.

For a handful of images that is a fine trade. For hundreds, consider WebP instead — larger files, but a fraction of the encoding time.

Questions

Can I compress an AVIF without losing quality?: Not meaningfully — this page produces lossy AVIF, so smaller means less detail. AVIF's advantage is that the detail it discards is considerably harder to notice than in older formats.
How low can I set the quality?: Further than you would expect. AVIF degrades gracefully, so settings around 50 to 60 often remain perfectly acceptable where the same value in a JPG would look obviously damaged. That is where the largest savings live.
Why is compressing so slow?: Because AVIF encoding is slow by design. The codec searches a large space of possible encodings, and that search is exactly what produces the small file. It runs in a Web Worker so the page stays responsive.
Why did quality 82 produce the same size?: Because your source was probably already encoded at around that setting. Re-encoding at a file's existing quality reproduces the same detail and therefore the same size.
Does moving the slider repeatedly degrade the image?: No. Each adjustment re-encodes from your original file rather than the previous result, so there is no generational loss.
Is transparency preserved?: Yes, including partially transparent pixels. AVIF also carries HDR and wide colour gamut, which survive where the source has them.
Is my image uploaded?: No. Decoding and encoding both run in this browser tab. The Uploaded readout beside the result measures the page's own outbound traffic, so a successful run reads 0 B.
Is there a file size limit?: None imposed. Large images take longer to encode rather than being rejected.
Will there be a watermark?: No. Nothing is added to the image and nothing is paywalled.
Should I resize instead of compressing?: Resize first, almost always. File size scales roughly with pixel count, so serving an image at the size it is actually displayed usually saves more than any quality setting.