BMP → AVIF, from heaviest to lightest
The two extremes of image storage meet: raw bitmaps become the smallest files modern browsers decode.
Runs in your browser. Your file never leaves your computer.
- RatioOften 100:1 from raw source
- InputClean pixels, ideal for encoding
- EncodeTakes real time; local
- LimitModern software only
Nothing showcases twenty-five years of compression research like feeding a raw bitmap to AVIF: a file storing every pixel byte-by-byte becomes one a hundredth the size that looks the same on screen. The clean, uncompressed source is actually ideal encoder input, no inherited artifacts to preserve. Encoding takes its time and current-software support is the known limit. For publishing old bitmap archives on the modern web, this is the direct route.
Questions
Is uncompressed source really better for AVIF?
Yes: the encoder shapes its loss around real image content instead of around another codec's artifacts. BMPs give it the cleanest possible start.
What is the practical catch?
Encoding speed, and software older than a few years drawing a blank on the files. For web publishing, neither usually matters.
Uploaded anywhere?
No, the encode is in-browser.
Related conversions
- BMP to PNGIdentical pixels at a fraction of the bytes. The default correct destination for any bitmap file.
- BMP to JPGPhotographic bitmaps drop from absurd to ordinary: a 24 MB file becomes a 1 MB JPG that mails and uploads.
- BMP to WebPLossless for graphics, quality 82 for photos, chosen automatically, always a fraction of the bitmap.
- BMP to PDFFaxes, scans and legacy exports live as BMPs; filing systems want PDFs. One page, assembled locally.
- PNG to AVIFAVIF pushes past WebP for photographic content, at the cost of slower encoding and older-software support.
- JPG to AVIFRoughly half the bytes of the JPG at matching visible quality. Worth it where load time is money.
Part of convert images in your browser. Every other conversion is on the conversions index.