Free webp to jpg
EN
Image MIME Reference
BMP

Windows Bitmap (Legacy Windows MIME Alias)

image/x-windows-bmp
VS

BlockFact Image

image/vnd.blockfact.facti
FACTI

A complete technical comparison of Windows Bitmap (Legacy Windows MIME Alias) and BlockFact Image — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.

BMP wins on browser support

Feature Support

Feature BMP FACTI
Transparency (Alpha) Yes Yes
Animation Support ✕ No ✕ No
Progressive Loading ✕ No ✕ No
HDR Support ✕ No Yes
EXIF Metadata ✕ No Yes
ICC Color Profile Yes Yes
Windows Bitmap (Legacy Windows MIME Alias)
image/x-windows-bmp
Extension
.bmp.dib
Container DIB (Device-Independent Bitmap)
Compression Uncompressed / Run-Length Encoding (RLE)
Algorithm
NoneRLE4RLE8
Color Depth 1-bit (Monochrome), 4-bit (16 colors), 8-bit (256 colors), 16-bit (High Color), 24-bit (True Color), 32-bit (True Color with Alpha)
Developed by Microsoft Corporation
Released 1985
Magic Bytes
42 4D
Full BMP reference →
BlockFact Image
image/vnd.blockfact.facti
Extension
.facti
Container BlockFact Authenticated Container
Compression Container (Inherits payload compression, e.g., JPEG/PNG)
Algorithm
None (Pass-through to embedded payload)
Color Depth Inherited from payload
Developed by BlockFact
Released 2025
Magic Bytes
Unknown (Proprietary Container)
Full FACTI reference →

Browser Support Comparison

Browser BMP FACTI
Chrome Chrome
✓ 1
 ✕
Firefox Firefox
✓ 1
 ✕
Safari Safari
✓ 1
 ✕
Edge Edge
✓ 12
 ✕
IE IE (Legacy)
✓
 ✕
BMP

BMP Strengths

  • Universally supported by all major operating systems and modern web browsers
  • Maintains perfect, lossless fidelity because pixel data is stored without lossy compression artifacts
Limitations
  • Massive file size overhead due to a lack of modern compression algorithms
  • Legacy MIME strings like 'image/x-windows-bmp' can trigger validation warnings in strict security or API environments if unhandled
FACTI

FACTI Strengths

  • Provides undeniable, mathematically verifiable proof of a photo's origin (time, location, and device) via the StarkNet blockchain [1.3.1]
  • Privacy-first design utilizes zero-knowledge proofs (Groth16), meaning the actual image is never uploaded to a central server or blockchain
  • Invisible watermarking ensures that even if the image is screenshotted or cropped, tampering can be detected
Limitations
  • Lacks native rendering support in web browsers and standard image viewers, requiring specialized software to view
  • Requires blockchain registration at the moment of capture, making it incompatible with existing legacy photos
  • The proprietary nature of the container limits integration to environments supporting the BlockFact SDK

When to choose which format

BMP
Use BMP when…
  • Legacy Windows Desktop Registry Associations
  • Older Enterprise Intranet Applications
  • Windows Graphics Archival
FACTI
Use FACTI when…
  • Journalism and Media Authentication
  • Legal and Insurance Evidence
  • AI Deepfake Prevention
  • Content Provenance and Authorship

More comparisons

BMP vs ACES → FACTI vs ACES → BMP vs APNG → FACTI vs APNG → BMP vs AVCI → FACTI vs AVCI → BMP vs AVCS → FACTI vs AVCS → BMP vs AVIF → FACTI vs AVIF → All comparisons →
Share this comparison