Is AVIF or BMP better? Which formats perform better than the other? Let's find out.
For those looking for a file format for their image delivery needs, two key contenders are vying for your attention: BMP and AVIF. Developed by Microsoft to store bitmap raster graphics on Windows independently of a system's graphics adapter, BMP (or Bitmap) is the format used for most graphics on Windows. Most BMP images tend to be uncompressed.
In the other corner, we have AVIF (AV1 Image File Format). First released in 2019, this relatively young image format is derived from the frames of the AV1 video codec.
AVIF was designed for efficient lossy compression and boasts a rich feature set. Its developers, the Alliance for Open Media (AOM), hope the AVIF standard will become the dominant image format for web delivery.
Here's how these two image formats compare in feature-set, performance, and efficiency.
Limits and Quality
AVIF is derived from a video codec, and it shares some similar limitations to the AV1 video format. AVIF boasts a maximum resolution of 65536 x 65536 pixels.
The limit for AVIFs image size is around 8000 pixels, but it is possible to produce larger AVIF images than this maximum resolution by independently encoding tiles and tiling them to create a larger image. However, using this method introduces some artifacts at the borders of these individual frames, making AVIF unsuitable for large print images.
As for BMP, the maximum resolution is up to debate and depends on which software you use to export the image. There is a consensus a realistic full resolution for BMP is 32,000 x 32,000 pixels. However, once we cover compression, it will become apparent it is impractical to create BMP images as large as this.
An AVIF image supports a wide color gamut, including HDR (high dynamic range). This is a feature BMP does not support. AVIF can support a max bit depth of 12-bits, whereas BMP images are limited to 8-bit precision.
When BMP was first released with Windows 1, it did not support any compression, and all bitmap images were uncompressed. Microsoft eventually included a lossless compression method in the subsequent version of Windows in the form of RLE (or run-length encoding). However, most BMP images remain uncompressed.
However, the compression algorithm used in BMP encoding is much less efficient than more modern forms of lossless compression. This leads to BMP images having larger file sizes than other image formats, even when compression is used.
AVIF supports both lossy and lossless compression. AVIF's lossless compression is much more efficient than BMP's, leading to great-looking graphics and lossless photos.
However, where AVIF shines the most is with low-fidelity lossy compression. AVIF retains detail and appeals much better than other image formats like JPEG with compressed images. The appeal is the absence of compression artifacts like color banding and blockiness. This property makes AVIF a popular choice for web delivery due to the file format's small file size to quality ratio.
BMP doesn't support lossy compression, and therefore any bitmap file will have a drastically larger file size. For example, a 53.7MB BMP file can be converted using AVIF.io to become a 4.66MB file and retain its quality. That's a whopping 92% reduction for a photo file.
The extortionate file sizes of BMP images, uncompressed and compressed with lossless compression, make the file format unsuitable for web use. AVIF features great lossless compression yielding images with much smaller file sizes for those unwilling to use lossy methods. However, AVIF's fantastic lossy compression algorithm means the format is perfect for web delivery and storage efficiency.
As most BMP images are uncompressed, the format boasts great encode speeds. Those working with BMP can easily save large batches of images without too much strain on their machines or time. Even for compressed BMP files, decode speeds are excellent, and most modern systems won't struggle with decoding even large bitmap images.
AVIF, on the other hand, is notoriously slow when it comes to single-core speeds, and slower hardware may struggle when decoding these images. AVIF does, however, support parallelization. This allows the image coder to use multi-threaded hardware and more than one CPU core to decode and encode AVIF images. As computer hardware tends towards higher core and thread counts, we expect AVIF's slow speeds to improve.
BMP is a much faster image format. However, this may not translate to being faster for end-users. With much larger file sizes, bitmaps take longer to transfer across the web and locally.
AVIF is efficient for animated images. Given the format's relation to the AV1 video codec, sequenced AVIF images benefit from interframe compression, allowing smaller file sizes for animated AVIFs.
AVIF also supports overlays and depth maps. Overlays enable layers to help maintain the clarity of text and graphics over compressed photo backgrounds. Depth maps allow users to add effects to foregrounds and backgrounds.
Animation, overlays, and depth map support are missing features with the BMP image format.
Both AVIF and BMP support alpha transparency, allowing both formats for transparent text and graphics.
With BMP's uncompressed nature and large file sizes, it's no surprise that web use is minimal. No major browser supports viewing BMP images.
All major operating systems widely support the format, so downloaded or transferred BMP files will be viewable locally. But BMP's limited use means browsers have been unwilling to incorporate support for the image format.
Despite its young age, being released in 2019, AVIF's market uptake has been fast and impressive. Google Chrome introduced full support for the image format in 2020, with Opera following shortly after. Firefox is close to providing full support. Users can enable AVIF in the browser's config settings (although Firefox is yet to support sequenced AVIF images).
Safari and Microsoft Edge do not yet support AVIF. However, we expect that once Chromium packs full support into its open-source code, Edge Chromium will follow. On mobile, Samsung Internet, Chrome for Mobile, and the Android Browser all support AVIF. Safari is the major mobile browser yet to support AVIF.
Conclusion for Nerds
BMP is a file format as old as Windows itself. Many image professionals can appreciate how integral the format allowed graphics to be used on the Windows GUI independently of a system's graphics adapter.
However, its limited feature set and lossy compression make BMP a poor contender for an all-purpose image format. Even with its rudimentary lossless data compression algorithm, BMP is inefficient, leading to large file sizes.
AVIF is a great all-rounder, boasting impressive features like good animation support, HDR, and wide gamut support, support for 4:4:4 (lossy). AVIF still has some way to get a whole house of web browser support, but we expect the meteoric rise in market uptake will continue.
We believe AVIF is destined to replace JPEG to become the dominant image format. BMP, however, has no further use outside of icons on Windows. We wouldn't be surprised if Microsoft replaced BMP in favor of a modern lossless format to cut down on the OS size in a future Windows update.
Conclusion for Marketeers
The winner for the average user is straightforward: AVIF is a solid contender to become the dominant image format. We expect it will go all the way to replace JPEG.
AVIF offers similar quality images using its excellent lossy compression algorithm as the uncompressed BMP file format offers. Most users won't distinguish between lossy AVIF and uncompressed bitmap image data, thanks to the high appeal of low-fidelity lossy AVIF images. Every day users will appreciate the excellent file size efficiency of AVIF resulting in way smaller file size than BMP, allowing them to store more photos and improve page load times for web delivery.
We expect in the coming years, AVIF will go from strength to strength. In the coming years, we expect AVIF to go from strength to strength. AVIF is perfectly placed to become the definitive image format for image delivery.