Free webp to jpg
Image MIME Reference
CNS-INF2

Comverse Network Systems INF2 Image

image/vnd.cns.inf2
VS

Extended Image File Format

image/vnd.xiff
XIFF

A complete technical comparison of Comverse Network Systems INF2 Image and Extended Image File Format — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.

Equal browser support

Feature Support

Feature CNS-INF2 XIFF
Transparency (Alpha) ✕ No ✕ No
Animation Support ✕ No ✕ No
Progressive Loading ✕ No ✕ No
HDR Support ✕ No ✕ No
EXIF Metadata ✕ No ✕ No
ICC Color Profile ✕ No ✕ No
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 →
Extended Image File Format
image/vnd.xiff
Extension
.xif
Container TIFF-based Proprietary Container
Compression CCITT Group 3 / Group 4 / LZW / Uncompressed
Algorithm
CCITT Group 4LZWNone
Color Depth 1-bit (Monochrome), 8-bit (Grayscale), 24-bit (RGB)
Developed by Keyfile Corporation
Released 1994
Magic Bytes
49 49 2A 00 or 4D 4D 00 2A
Full XIFF reference →

Browser Support Comparison

Browser CNS-INF2 XIFF
Chrome Chrome
Firefox Firefox
Safari Safari
Edge Edge
IE IE (Legacy)
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
XIFF

XIFF Strengths

  • Pioneered early enterprise document workflow integration by binding administrative routing data directly to the document image file
  • Leveraged efficient fax compression standards to keep storage requirements low on 1990s server infrastructure
Limitations
  • Completely proprietary and obsolete; Keyfile Corporation's software ecosystem no longer exists
  • Causes widespread MIME type identification conflicts due to sharing the exact same binary header signature as standard TIFF files
  • Zero support in modern operating systems or web browsers

When to choose which format

CNS-INF2
Use CNS-INF2 when…
  • Legacy Telecom Infrastructure
  • Historical Comverse Unified Messaging Systems
  • Proprietary Server-to-Server Media Exchange
XIFF
Use XIFF when…
  • Keyfile Enterprise Document Management
  • Legacy Corporate Workflow Archival
  • Scanned Multi-page Document Routing
Share this comparison