Add your AVIF file
Drop one or more .avif files onto the converter above, or browse for them. They load into browser memory only — nothing is uploaded, so there is no size-based pricing and no server queue.
Converting a .avif image to .bmp re-encodes the pixels for a different balance of size, quality, and support. Free, private, and validated — the file never leaves your browser.
Batch files can each use a different output. Nothing uploads for local conversions.
Working inputs include camera RAW, browser-local audio/video, PDF, CBZ/CBR comics, office documents, ebooks, markup, 3D models, structured text, images, and archives.Converting a .avif image to .bmp re-encodes the pixels for a different balance of size, quality, and support. An .avif file stores a still image (or sequence) coded with the AV1 video codec inside a HEIF-derived container. It is currently among the most efficient image formats deployed on the web, routinely beating JPEG by half at similar quality while adding HDR, wide gamut, and alpha.
A .bmp file is the Windows bitmap format: raw pixel rows written to disk with a small header and, in the common case, no compression at all. Its brute simplicity makes .bmp trivial to read and write from any programming language, which is why it persists in tooling, embedded systems, and quick debugging dumps. For this route the practical draw is dead-simple structure with no decoding step at all and exactly lossless — what you write is what you read — balanced against no effective compression, so files dwarf PNG equivalents of the same image, which is worth knowing before you commit a large batch.
The practical trigger for this conversion is usually a mismatch: with .avif, encoding is much slower than JPEG or WebP, especially at high effort settings. Switching to .bmp buys you dead-simple structure with no decoding step at all, which is why it is the better fit for quick lossless dumps from code, since a writer takes minutes to implement. Because the conversion runs locally, trying it costs nothing but a few seconds of compute on your own machine.
| Aspect | AVIF image (.avif) | Bitmap image (.bmp) |
|---|---|---|
| Format type | Lossy — discards detail it judges invisible to shrink files | Lossless — every pixel or sample is preserved exactly |
| How it stores data | encodes AV1 intra frames; both lossy and a mathematically lossless mode are defined | pixels are typically stored uncompressed; optional RLE encoding exists only for 4-bit and 8-bit palette images |
| Strongest at | serving hero images and photo galleries where bandwidth savings are significant | quick lossless dumps from code, since a writer takes minutes to implement |
| Weak spot | encoding is much slower than JPEG or WebP, especially at high effort settings | no effective compression, so files dwarf PNG equivalents of the same image |
Drop one or more .avif files onto the converter above, or browse for them. They load into browser memory only — nothing is uploaded, so there is no size-based pricing and no server queue.
Select .bmp in the output menu next to each file. The menu only offers targets this engine can genuinely produce, so if BMP is selectable, the route is real and validated.
Press Convert. Decoding and re-encoding happen on your device using the browser's native image pipeline and hand-tuned encoders.
Each result is signature-checked before the download unlocks, so a failed encode can never masquerade as a valid BMP file. Outputs keep the original filename with the .bmp extension.
No new loss is introduced — since avif is lossy-oriented and bmp is lossless-oriented, everything the .avif file still contains is carried over exactly. What was already discarded by the original lossy encode cannot be recovered, though; converting to .bmp does not "restore" quality.
Yes — the .avif file is processed inside your browser tab and never uploaded. Decoding and re-encoding happen on your device using the browser's native image pipeline and hand-tuned encoders. Close the tab and the file is gone from memory.
Windows treats BMP as a native citizen, and macOS, Linux, and all major browsers open it without complaint. The format's problem is never support but waste: emailing or hosting uncompressed bitmaps burns bandwidth for zero benefit, so converting to PNG is almost always an upgrade.
Larger, sometimes much larger. A lossless .bmp must store every pixel or sample the decoder produced, without the perceptual shortcuts .avif used. Use this route for editing headroom, not for saving space.
In .avif, eXIF and XMP are stored as metadata items in the HEIF container alongside ICC profiles or CICP color signaling, and mainstream encoders preserve them on conversion. Re-encoding through the browser pipeline does not carry embedded metadata into the output, which doubles as a privacy scrub — check the exported file if you specifically need tags preserved.
Yes — the reverse route exists as a separate tool. Bear in mind that round-tripping .avif → .bmp → .avif is not a perfect undo when any lossy step is involved; keep your original if fidelity matters.