Free webp to jpg
Image MIME Reference
Sony-SRF

Sony SRF Raw Image

image/x-sony-srf
VS

T.38 Fax over IP (FoIP)

image/t38
T.38

A complete technical comparison of Sony SRF Raw 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 Sony-SRF T.38
Transparency (Alpha) ✕ No ✕ No
Animation Support ✕ No ✕ No
Progressive Loading ✕ No ✕ No
HDR Support Yes ✕ No
EXIF Metadata Yes ✕ No
ICC Color Profile Yes ✕ No
Sony SRF Raw Image
image/x-sony-srf
Extension
.srf
Container TIFF-based (Proprietary)
Compression Uncompressed
Algorithm
None
Color Depth 12-bit (Per Channel)
Developed by Sony Corporation
Released 2003
Magic Bytes
49 49 2A 00
Full Sony-SRF 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 Sony-SRF T.38
Chrome Chrome
Firefox Firefox
Safari Safari
Edge Edge
IE IE (Legacy)
Sony-SRF

Sony-SRF Strengths

  • Retains perfectly raw, unprocessed sensor data from legacy early-2000s cameras, allowing modern raw processors to extract much better dynamic range and color than the camera's original internal JPEG engine could
  • Utilizes a standard TIFF container structure, ensuring broad compatibility with community-maintained open-source decoding libraries like LibRaw
Limitations
  • Completely obsolete format that has long been abandoned in favor of ARW
  • MIME detection via magic bytes is unreliable due to TIFF header spoofing, requiring deeper EXIF inspection for accurate routing
  • Cannot be natively viewed in web browsers or standard operating system image viewers without specialized decoders
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

Sony-SRF
Use Sony-SRF when…
  • Legacy Sony Cyber-shot Photography
  • Non-destructive Image Post-Processing
  • Early 2000s Raw Imaging Archival
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