Free webp to jpg
Image MIME Reference
FreeHand

Macromedia FreeHand Document

image/x-freehand
VS

T.38 Fax over IP (FoIP)

image/t38
T.38

A complete technical comparison of Macromedia FreeHand Document 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 FreeHand T.38
Transparency (Alpha) Yes ✕ No
Animation Support Yes ✕ No
Progressive Loading ✕ No ✕ No
HDR Support ✕ No ✕ No
EXIF Metadata ✕ No ✕ No
ICC Color Profile Yes ✕ No
Macromedia FreeHand Document
image/x-freehand
Extension
.fh.fh4.fh5.fh7.fh8.fh9.fh10.fh11.ft11
Container Proprietary Binary (Aldus Graphic Document)
Compression Uncompressed / Deflate (in later versions)
Algorithm
NoneDeflate (Optional in later versions)
Color Depth Vector Data (RGB/CMYK)
Developed by Altsys / Aldus / Macromedia
Released 1988
Magic Bytes
41 47 44 31 to 41 47 44 34
Full FreeHand 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 FreeHand T.38
Chrome Chrome
Firefox Firefox
Safari Safari
Edge Edge
IE IE (Legacy)
FreeHand

FreeHand Strengths

  • Historically one of the most powerful and intuitive vector editors on the market, praised for multi-page support long before Adobe Illustrator implemented it
  • Files are generally compact and self-contained
Limitations
  • Completely abandoned proprietary format; Adobe actively blocked native import in modern versions of Illustrator
  • No support in modern web browsers; must be converted to SVG
  • Versioning fragmentation means parsers must account for wildly different binary structures depending on the specific .fhX extension used
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

FreeHand
Use FreeHand when…
  • Legacy Graphic Design Portfolios
  • Historical Desktop Publishing Archival
  • Old Corporate Logo Vectors
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