Make your AVIF files smaller without changing format. Blinkimg re-encodes AVIF to cut file size while keeping the sharp quality the format is known for. Free, online, no signup. Part of the image compressor.
Output format
– / –
Drop images or browse
JPEG · PNG · WEBP · AVIF · HEIC · up to 50 at once · max 30 MB each
A real result from this exact operation: 215.5 KB in, 46.9 KB out. Drop your own file and the meter reports yours.
Why is my AVIF bigger than my JPEG?
A quality-scale mismatch, usually. The question brings most people here, and it has a measurable answer. AVIF’s quality numbers are not JPEG’s: our Auto uses 50 for a photo, where JPEG gets 78. On our reference photo, AVIF at quality 80 measured 337.3 KB while quality 60 measured 178.3 KB: quality 80 cost 89% more. JPEG at the same quality 80 measured 293.6 KB, so the AVIF came out bigger. People encode AVIF at 85 “to be safe”, produce a file bigger than their JPEG, and conclude the format is broken. It isn’t; the dial is different. Two rarer causes: an encoder set to its very fastest effort, and re-encoding a source that was already heavily compressed. Effort matters far less than quality: across our own corpus a step of effort moves size by a few percent, where a step of quality moves it by tens.
AVIF against JPEG and WebP, each at its default
Image
AVIF
WebP
JPEG
Camera photo, 4964 × 2782
288 KB
329 KB
605.5 KB
Reference photo, 1920 × 1280
123.9 KB
218.9 KB
273.9 KB
Each format at Auto: AVIF 50, WebP 75 and JPEG 78 for a photo. These are the defaults, not matched looks.
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.
Is your AVIF already optimal? We'll tell you
Two honest outcomes, both automated. Many AVIFs have headroom because a CMS or an exporter encoded them at conservative quality. We measured a real example: the 363 KB reference re-compressed to 123.2 KB on Auto. But when a file is already at the efficient frontier, re-encoding would grow it. In that case our never-larger guard hands back your original untouched and says so, instead of shipping a bigger file labelled "compressed". If the result says your file was already optimal, the next lever is dimensions, not quality: resize the image.
What AVIF can carry, and what we output
The specification supports full alpha transparency, animation, 10/12-bit depth, HDR and wide colour gamut. What our compressor does with each, stated plainly: we preserve alpha (check edges against the checkerboard in the compare slider); we decline animated AVIF rather than silently flatten it to frame one; we output 8-bit sRGB for maximum compatibility, so extreme HDR highlights tone-map the same way they would in any JPEG or WebP workflow. If HDR delivery matters to you, keep the original and serve it to the audiences that can render it.
When not to re-compress an AVIF
The tool says it was already optimal?
Believe it. Re-encoding lossy-to-lossy has a cost, and dimensions are the honest next lever.
It is your only copy?
Every AVIF here is already lossy; compress a copy for delivery and keep the source you made it from.
You need HDR or animation preserved?
Our output is 8-bit sRGB stills. Keep the original for those pipelines.
Questions, answered
Short answers specific to this page. The tool above settles most of them in a second.
Q:Does compressing an AVIF keep it an AVIF?
Yes. The file goes in as an AVIF and comes out as one, re-encoded at the quality our tests found clean on AVIF’s own scale, and never larger than it came in. AVIF is built on the AV1 video codec and already stores a photo in fewer bytes than JPEG, so there is rarely a reason to leave it.
Q:Why is my AVIF file bigger than my JPEG?
Usually a quality-scale mismatch. AVIF's quality numbers are not JPEG's. On our reference photo AVIF at quality 80 measured 337.3 KB and quality 60 measured 178.3 KB: quality 80 cost 89% more. Our Auto uses 50 for photos and 60 for graphics. Encoding AVIF at the 80 to 90 you learned from JPEG mostly buys bytes.
Q:What quality setting should I use for AVIF?
Start between 50 and 65. Our Auto picks 50 for a photo and 60 for a graphic, values we chose by eye on our own test images. AVIF's quality scale is its own, so a number from JPEG or WebP does not carry over. Compare the result at 100% in the slider before you go higher.
Q:Can I compress an AVIF that is already AVIF?
Often, yes. Many AVIFs in the wild were encoded conservatively. Our 363 KB reference re-compressed to 123.2 KB on Auto. And if re-encoding would grow your file, our never-larger guard returns the original untouched instead of shipping a bigger "compressed" file.
Q:How much smaller is AVIF than JPEG and WebP?
It depends on the picture. At each format's default, our camera photo measured 288 KB as AVIF, 329 KB as WebP and 605.5 KB as JPEG. Our reference photo measured 123.9 KB as AVIF, 218.9 KB as WebP and 273.9 KB as JPEG. AVIF was smallest on both, by a different margin. Your own number appears the moment you compress.
Q:Does the encoder effort setting change file size?
Yes, but less than people expect. AV1 encoders trade time for bytes, and we measured our own: moving one step faster costs about 3% in size on a real iPhone photo, or about a fifth of a quality step if you hold the size instead. We run a fixed effort one step below sharp’s default, so results stay consistent and reproducible, and a photo encodes in well under a second rather than several.
Q:Can AVIF be compressed losslessly?
Yes, in theory: the format supports a true lossless mode. It usually defeats the purpose, though, because lossless AVIF is often larger than an optimised PNG. Our compressor is perceptually lossy by design. For pixel-exact archives, keep your source file and treat AVIF as the delivery format.
Q:Does AVIF support transparency, animation and HDR?
Yes, all three in the specification: full alpha transparency (preserved here), animated AVIF, and 10-bit HDR with wide colour gamut. Our pipeline outputs 8-bit sRGB stills for maximum compatibility, keeps alpha, and declines animated inputs rather than flattening them silently.
Q:Is AVIF supported in all browsers in 2026?
About 95% globally: Chrome 85+, Firefox 93+, Safari 16.1+, Edge 121+. For the remainder, serve a picture element with a WebP or JPEG fallback. Outside browsers: Windows 11 needs the free AV1 extension, macOS Preview works from Ventura, Photoshop needs a plugin.
Q:Why is my AVIF slow to decode on some phones?
AV1 decoding costs more CPU than JPEG, and low-end mobiles without hardware decode feel it on very large images. The fix is the same as good practice anyway: serve sensibly-sized images (not 8000px originals), and the decode cost disappears into the noise.
Q:Can I compress many AVIF files at once?
Yes: up to 50 per batch, 30 MB each, one ZIP download with filenames preserved. Free, no signup, a 300-image daily allowance. Each row reports its measured before/after size, so you can see which files had headroom and which were already at the efficient frontier.
Q:What happens to my files after compressing?
We keep nothing: we process your files and wipe them automatically, never archive them, never share them, never use them for anything else. We strip metadata from outputs by default, and you need no account, so no profile collects your files, and after a day no record names them.
