Free webp to jpg
Image MIME Reference
Net-FPX

Network FlashPix

image/vnd.net-fpx
VS

T.38 Fax over IP (FoIP)

image/t38
T.38

A complete technical comparison of Network FlashPix 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 Net-FPX T.38
Transparency (Alpha) Yes ✕ No
Animation Support ✕ No ✕ No
Progressive Loading Yes ✕ No
HDR Support ✕ No ✕ No
EXIF Metadata Yes ✕ No
ICC Color Profile Yes ✕ No
Network FlashPix
image/vnd.net-fpx
Extension
.fpx
Container Microsoft OLE Structured Storage (COM)
Compression JPEG (Lossy) / Uncompressed / Single-color (Solid)
Algorithm
JPEGNone
Color Depth 8-bit (Grayscale/Indexed), 24-bit (RGB), 32-bit (CMYK/RGBA)
Developed by Digital Imaging Group (Kodak, HP, Live Picture, Microsoft)
Released 1996
Magic Bytes
D0 CF 11 E0 A1 B1 1A E1
Full Net-FPX 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 Net-FPX T.38
Chrome Chrome
Firefox Firefox
Safari Safari
Edge Edge
IE IE (Legacy)
Net-FPX

Net-FPX Strengths

  • Revolutionized web imaging in the late 1990s by proving that massive gigapixel images could be navigated seamlessly over 56k dial-up modems
  • Pioneered the tile-based, multi-resolution pyramid concepts that eventually evolved into modern standards like IIIF (International Image Interoperability Framework)
Limitations
  • Completely obsolete, having been replaced by standard JPEG servers and modern tiling formats like Deep Zoom or JPEG 2000/XR
  • Relied on proprietary Java applets or ActiveX controls to render the tiles dynamically in a web browser
  • Extremely complex to parse server-side due to the heavy OLE filesystem container
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

Net-FPX
Use Net-FPX when…
  • Historical Internet Imaging Protocol (IIP) Streaming
  • Early E-Commerce Deep Zoom Implementations
  • Legacy High-Resolution Image Servers
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