Free webp to jpg
Image MIME Reference
FreeHand

Macromedia FreeHand Document

image/x-freehand
VS

PTI Image (Personal/Vanity Tree)

image/prs.pti
PTI

A complete technical comparison of Macromedia FreeHand Document and PTI Image (Personal/Vanity Tree) — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.

Equal browser support

Feature Support

Feature FreeHand PTI
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 →
PTI Image (Personal/Vanity Tree)
image/prs.pti
Extension
.pti
Container Proprietary
Compression Unknown / Proprietary
Algorithm
Unknown
Color Depth Unknown
Developed by Jürn Laun
Released 1999
Magic Bytes
Unknown
Full PTI reference →

Browser Support Comparison

Browser FreeHand PTI
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
PTI

PTI Strengths

  • Provided a registered MIME type namespace for a specific application's proprietary image format without conflicting with standard web types
Limitations
  • Completely undocumented and unsupported in modern ecosystems
  • Zero web browser compatibility
  • Falls into the 'vanity' tree, making it irrelevant for standard cross-platform data exchange

When to choose which format

FreeHand
Use FreeHand when…
  • Legacy Graphic Design Portfolios
  • Historical Desktop Publishing Archival
  • Old Corporate Logo Vectors
PTI
Use PTI when…
  • Legacy Application Specific Workflows
  • Proprietary Image Storage
Share this comparison