Free webp to jpg
Image MIME Reference
Apple-ICNS

Apple Icon Image

image/x-icns
VS

T.38 Fax over IP (FoIP)

image/t38
T.38

A complete technical comparison of Apple Icon Image and T.38 Fax over IP (FoIP) — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.

Equal browser support

Feature Support

Feature Apple-ICNS T.38
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
Apple Icon Image
image/x-icns
Extension
.icns
Container Chunk-based (OSType Header)
Compression Uncompressed (Legacy) / PNG (Modern) / JPEG 2000 (Modern)
Algorithm
NoneDeflate (via embedded PNG)Wavelet (via embedded JP2)
Color Depth 1-bit (Monochrome), 4-bit, 8-bit, 24-bit (RGB), 32-bit (RGBA)
Developed by Apple Inc.
Released 2001
Magic Bytes
69 63 6E 73
Full Apple-ICNS reference →
T.38 Fax over IP (FoIP)
image/t38
Extension
.t38
Container UDPTL or TCP (Network Transport)
Compression Lossless (MH, MR, MMR / T.4, T.6)
Algorithm
MH (Modified Huffman)MR (Modified Read)MMR (Modified Modified Read)
Color Depth 1-bit (Monochrome B&W)
Developed by ITU-T (International Telecommunication Union)
Released 1998
Magic Bytes
None (Network Stream)
Full T.38 reference →

Browser Support Comparison

Browser Apple-ICNS T.38
Chrome Chrome
Firefox Firefox
Safari Safari
Edge Edge
IE IE (Legacy)
Apple-ICNS

Apple-ICNS Strengths

  • Seamlessly handles multi-resolution scaling on macOS, perfectly serving both standard and high-DPI (Retina) displays from a single asset
  • Modern versions efficiently embed standard PNG files, making it much easier to parse the high-resolution layers than the legacy raw pixel formats
Limitations
  • Strictly bound to the Apple ecosystem; completely useless natively on Windows, Linux, or the Web
  • The internal chunking structure is notoriously messy, utilizing dozens of different undocumented, legacy OSType tags spanning 20+ years of Apple history
T.38

T.38 Strengths

  • Designed specifically to overcome the timing and packet-loss issues that plague traditional fax over standard VoIP audio codecs (like G.711)
  • Reduces bandwidth requirements by transmitting fax protocol data rather than uncompressed audio tones
  • Universally supported by enterprise SIP trunks and Session Border Controllers (SBCs) for FoIP
Limitations
  • Not an actual image file format, causing confusion due to its 'image/' MIME classification
  • Extremely complex to implement correctly over lossy UDP networks (relies on UDPTL redundancy mechanisms)
  • Zero support in web browsers or standard image viewing software

When to choose which format

Apple-ICNS
Use Apple-ICNS when…
  • macOS Application Bundles (.app)
  • macOS Folder Customization
  • Apple Disk Image (.dmg) Styling
T.38
Use T.38 when…
  • Fax over IP (FoIP) Transmissions
  • SIP/SDP Media Negotiation
  • VoIP Gateways and PBX Systems
  • Enterprise Fax Servers
Share this comparison