Free webp to jpg
Image MIME Reference
AVIF

AV1 Image File Format

image/avif
VS

T.38 Fax over IP (FoIP)

image/t38
T.38

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

AVIF wins on browser support

Feature Support

Feature AVIF T.38
Transparency (Alpha) Yes ✕ No
Animation Support Yes ✕ No
Progressive Loading ✕ No ✕ No
HDR Support Yes ✕ No
EXIF Metadata Yes ✕ No
ICC Color Profile Yes ✕ No
AV1 Image File Format
image/avif
Extension
.avif
Container HEIF / ISOBMFF
Compression AV1 Lossy / AV1 Lossless
Algorithm
AV1
Color Depth 8-bit, 10-bit, 12-bit
Developed by Alliance for Open Media (AOMedia)
Released 2019
Magic Bytes
XX XX XX XX 66 74 79 70 61 76 69 66
Full AVIF 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 AVIF T.38
Chrome Chrome
✓ 85+
Firefox Firefox
✓ 93+
Safari Safari
✓ 16+
Edge Edge
✓ 121+
IE IE (Legacy)
AVIF

AVIF Strengths

  • Best-in-class compression — typically 20–50% smaller than WebP at equivalent quality
  • Native HDR and wide color gamut (BT.2020) support
  • Supports 8, 10, and 12-bit color depth
Limitations
  • Encoding is highly CPU-intensive — significantly slower than JPEG or WebP
  • Requires Edge 121+ (not supported in earlier Edge versions)
  • Limited support in native desktop image viewers
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

AVIF
Use AVIF when…
  • Next-Gen Websites
  • HDR Photography
  • High-Quality Web Images
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