Free webp to jpg
Image MIME Reference
AOL-ART

AOL ART Image

image/x-jg
VS

T.38 Fax over IP (FoIP)

image/t38
T.38

A complete technical comparison of AOL ART 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 AOL-ART T.38
Transparency (Alpha) ✕ No ✕ No
Animation Support ✕ No ✕ No
Progressive Loading Yes ✕ No
HDR Support ✕ No ✕ No
EXIF Metadata ✕ No ✕ No
ICC Color Profile ✕ No ✕ No
AOL ART Image
image/x-jg
Extension
.art
Container Johnson-Grace Proprietary
Compression Proprietary Wavelet (Photos) / Proprietary Palette-based (Graphics)
Algorithm
Wavelet (similar to early JPEG 2000 concepts)Lossy DCT
Color Depth 8-bit (Indexed), 24-bit (RGB)
Developed by Johnson-Grace Company (Acquired by AOL)
Released 1994
Magic Bytes
4A 47 03 00 or 4A 47 04 00
Full AOL-ART 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 AOL-ART T.38
Chrome Chrome
Firefox Firefox
Safari Safari
Edge Edge
IE IE (Legacy)
AOL-ART

AOL-ART Strengths

  • Historically provided massive file size reductions (up to 3x smaller than JPEGs of the era) and highly optimized progressive rendering for 14.4k modems
  • Enabled faster web browsing on the AOL network during the early days of the commercial internet
Limitations
  • Completely proprietary, heavily patent-encumbered, and never officially reverse-engineered for the open-source community
  • On-the-fly proxy compression ruined the visual fidelity of many 1990s websites for AOL users
  • Virtually impossible to open on modern operating systems without installing niche, legacy 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

AOL-ART
Use AOL-ART when…
  • Historical AOL Dial-up Web Browsing
  • Legacy America Online Client Assets
  • 1990s Internet 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