Free webp to jpg
Image MIME Reference
CNS-INF2

Comverse Network Systems INF2 Image

image/vnd.cns.inf2
VS

Tencent TAP Image

image/vnd.tencent.tap
Tencent-TAP

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

Equal browser support

Feature Support

Feature CNS-INF2 Tencent-TAP
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 →
Tencent TAP Image
image/vnd.tencent.tap
Extension
.tap
Container Proprietary Tencent Container
Compression Unknown (Proprietary)
Algorithm
Unknown
Color Depth Unknown
Developed by Tencent (Registered by Ni Hui)
Released 2014
Magic Bytes
Unknown (Proprietary)
Full Tencent-TAP reference →

Browser Support Comparison

Browser CNS-INF2 Tencent-TAP
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
Tencent-TAP

Tencent-TAP Strengths

  • Officially registered with IANA, ensuring a unique MIME type identifier for internal Tencent network routing and content negotiation
Limitations
  • Completely undocumented and closed-source, making it impossible to decode or parse outside of Tencent's software
  • Shares its file extension (.tap) with numerous other established legacy formats, leading to frequent automated file misidentification by Node/Python libraries

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
Tencent-TAP
Use Tencent-TAP when…
  • Internal Tencent Ecosystem Applications
  • Proprietary Mobile or Gaming Assets
Share this comparison