Free webp to jpg
Image MIME Reference
QTIF

QuickTime Image Format

image/x-quicktime
VS

T.38 Fax over IP (FoIP)

image/t38
T.38

A complete technical comparison of QuickTime Image Format 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 QTIF 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 ✕ No ✕ No
QuickTime Image Format
image/x-quicktime
Extension
.qtif.qti.qif
Container QuickTime Atom Container
Compression Varies (JPEG, SMC, Apple Video, Cinepak, Uncompressed)
Algorithm
QuickTime Image Compression Manager (ICM) Codecs
Color Depth 1-bit to 32-bit (Varies depending on the enclosed codec)
Developed by Apple Computer, Inc.
Released 1991
Magic Bytes
Varies (Typically begins with a 32-bit size integer followed by 69 64 73 63 ('idsc'))
Full QTIF 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 QTIF T.38
Chrome Chrome
Firefox Firefox
Safari Safari
Edge Edge
IE IE (Legacy)
QTIF

QTIF Strengths

  • Extremely flexible architecture allowing it to encapsulate virtually any image compression algorithm available on the host machine
  • Supported 32-bit images with alpha channels (transparency) long before PNG became an established standard
Limitations
  • Fundamentally tied to Apple's deprecated QuickTime architecture, rendering the files almost entirely unreadable on modern systems without specialized legacy software or FFmpeg
  • The 'wrapper' nature of the format means that even if a parser can read the QTIF container, it may fail to render the image if it lacks the specific proprietary codec (like Apple SMC) used to compress the pixel data
  • Zero native support in modern web browsers
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

QTIF
Use QTIF when…
  • Classic Mac OS Applications and Backgrounds
  • QuickTime VR Panorama Textures
  • 1990s CD-ROM Multimedia Assets
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