Free webp to jpg
Image MIME Reference
MacPaint

MacPaint Image

image/x-macpaint
VS

T.38 Fax over IP (FoIP)

image/t38
T.38

A complete technical comparison of MacPaint 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 MacPaint T.38
Transparency (Alpha) ✕ No ✕ No
Animation Support ✕ No ✕ No
Progressive Loading ✕ No ✕ No
HDR Support ✕ No ✕ No
EXIF Metadata ✕ No ✕ No
ICC Color Profile ✕ No ✕ No
MacPaint Image
image/x-macpaint
Extension
.mac.pntg.pnt.macp
Container Raw pixel payload with a 512-byte pattern header
Compression PackBits (Run-Length Encoding)
Algorithm
PackBits (Apple RLE)
Color Depth 1-bit (Monochrome)
Developed by Apple Computer, Inc. (Bill Atkinson)
Released 1984
Magic Bytes
None (Relies on classic Mac OS 'PNTG' OSType)
Full MacPaint 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 MacPaint T.38
Chrome Chrome
Firefox Firefox
Safari Safari
Edge Edge
IE IE (Legacy)
MacPaint

MacPaint Strengths

  • Profoundly historically significant as the format that introduced millions to the concept of bitmap digital painting
  • Extremely simple PackBits compression makes it easy for emulator developers or archivists to write parsers from scratch in under an hour
Limitations
  • Severely limited: strictly black and white, and hard-locked to exactly 576 x 720 pixels
  • Lack of standard magic bytes makes programmatic file sniffing unreliable on modern filesystems without relying on the file extension
  • Completely obsolete and unsupported by modern web browsers or consumer 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

MacPaint
Use MacPaint when…
  • Historical Apple Macintosh Archival
  • Early 1980s Digital Art Preservation
  • Retro UI/UX Academic Research
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