image/bmp BMP Common
Identifies BMP bitmap images — an old, largely uncompressed Windows-native image format.
What it's for
image/bmp identifies BMP (Bitmap) images — an old Windows-native raster image format storing pixel data with little to no compression, resulting in file sizes dramatically larger than modern formats for equivalent visual content. It predates virtually every other common image format still in use today, and its main relevance in modern development is legacy compatibility and specific Windows-ecosystem tooling, rather than anything you'd deliberately choose for web delivery or general-purpose image storage.
Format & syntax
Content-Type: image/bmp
No parameters. BMP's internal structure is relatively simple (a header followed by raw or minimally-compressed pixel data), which is part of why it was historically easy for many tools to support, but that same simplicity means it lacks the sophisticated compression algorithms that make modern formats so much more space-efficient.
How it's used in practice
- Legacy Windows applications and screenshots — some older Windows tools and workflows still default to or support BMP, largely due to historical inertia from an era when it was the native, built-in format for Windows' Paint application and clipboard image handling.
- Certain embedded/hardware contexts — some embedded systems, older printer/scanner software, or specific hardware tooling still use BMP due to its simple, easy-to-implement structure requiring minimal decoding complexity.
- Icon/cursor file internals (historically) — some older Windows icon and cursor formats have structural roots related to BMP's simple bitmap approach, though modern icon formats have largely moved beyond this.
- Uncompressed intermediate format in some processing pipelines — occasionally used as a lossless intermediate format in specific image-processing workflows where avoiding any compression artifacts at an intermediate step matters more than file size.
Common mistakes & gotchas
- Using BMP for web content and getting unnecessarily huge file sizes — BMP's lack of meaningful compression means web images served as BMP are dramatically larger than the same content would be as PNG, JPEG, or WebP — there's essentially never a good reason to serve BMP images to end users over the web.
- Assuming BMP is a "safe, universal" choice like PNG — while technically supported by many image viewers, BMP isn't the practical universal default it might seem given its age; modern formats have far better tooling, compression, and are the expected default across web and most application contexts today.
- Not converting user-uploaded BMP files to a more efficient format — if your application accepts image uploads and a user happens to upload a BMP (from an older tool or workflow), converting it to PNG or JPEG on ingest avoids storing and serving unnecessarily bloated files going forward.
Comparison & FAQ
| Type | Purpose | Key difference from image/bmp |
|---|---|---|
| image/png | Lossless compression | Dramatically smaller file sizes than BMP for equivalent lossless quality |
| image/jpeg | Lossy photo compression | Much smaller files for photographic content than BMP's essentially uncompressed approach |
Should I ever use BMP for web images?
No — there's essentially never a good reason to serve BMP over the web given its lack of meaningful compression; PNG, JPEG, or WebP will always produce dramatically smaller files for equivalent visual content.
Why is my BMP file so much larger than expected?
BMP uses little to no compression by design, storing pixel data close to raw — this is expected behavior for the format, not a bug, and is exactly why it's rarely chosen deliberately for anything beyond specific legacy or embedded use cases.
Is BMP still relevant in any modern context?
Mainly in legacy Windows tooling, certain embedded/hardware systems, or specific processing pipelines wanting an uncompressed intermediate format — it's not a format you'd choose for general modern image storage or web delivery.
Should I convert user-uploaded BMP images to another format?
Generally yes — converting to PNG or JPEG on ingest avoids storing and repeatedly serving unnecessarily large files, since there's rarely a reason to preserve the BMP format itself once the image is in your system.