Free webp to jpg
EN
Image MIME Reference
BMP

Windows Bitmap (Legacy Windows MIME Alias)

image/x-windows-bmp
VS

Comverse Network Systems INF2 Image

image/vnd.cns.inf2
CNS-INF2

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

BMP wins on browser support

Feature Support

Feature BMP CNS-INF2
Transparency (Alpha) Yes ✕ No
Animation Support ✕ No ✕ No
Progressive Loading ✕ No ✕ No
HDR Support ✕ No ✕ No
EXIF Metadata ✕ No ✕ No
ICC Color Profile Yes ✕ No
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 →
Comverse Network Systems INF2 Image
image/vnd.cns.inf2
Extension
.inf2
Container Proprietary Comverse Container
Compression Proprietary
Algorithm
Unknown (Proprietary Telecom Encoding)
Color Depth Unknown
Developed by Comverse Network Systems (Ann McLaughlin)
Released 1999
Magic Bytes
Unknown (Proprietary)
Full CNS-INF2 reference →

Browser Support Comparison

Browser BMP CNS-INF2
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
CNS-INF2

CNS-INF2 Strengths

  • Historically allowed Comverse to standardize media transmission internally across their global telecom messaging platforms
Limitations
  • Completely obsolete and non-functional outside of decommissioned telecom infrastructure
  • Undocumented, closed-source binary structure
  • Zero support in modern image processing libraries like ImageMagick, libvips, or FFmpeg

When to choose which format

BMP
Use BMP when…
  • Legacy Windows Desktop Registry Associations
  • Older Enterprise Intranet Applications
  • Windows Graphics Archival
CNS-INF2
Use CNS-INF2 when…
  • Legacy Telecom Infrastructure
  • Historical Comverse Unified Messaging Systems
  • Proprietary Server-to-Server Media Exchange

More comparisons

BMP vs ACES → CNS-INF2 vs ACES → BMP vs APNG → CNS-INF2 vs APNG → BMP vs AVCI → CNS-INF2 vs AVCI → BMP vs AVCS → CNS-INF2 vs AVCS → BMP vs AVIF → CNS-INF2 vs AVIF → All comparisons →
Share this comparison