DFONT vs PFB: Complete Format Comparison
Comprehensive comparison of DFONT and PFB formats covering Mac-only versus obsolete PostScript, two legacy desktop formats, and why both should be replaced with universal standards
In Simple Terms
Both are legacy desktop formats. DFONT is macOS-only container, PFB is deprecated PostScript Type 1 (Adobe ended support 2023).DFONT works on Mac only. PFB is obsolete everywhere. Convert both to modern OTF or TTF for better cross-platform desktop compatibility.Conversion path: DFONT → TTF, PFB → OTF. Then use OTF/TTF for desktop or convert to WOFF2 for web. Both formats limit modern workflows.
In this article
DFONT (Data Fork Font) and PFB (PostScript Font Binary) represent two legacy desktop font formats from different eras and vendors, with DFONT being Apple's macOS-specific container from the OS X transition (2001) and PFB being Adobe's PostScript Type 1 format that dominated professional publishing (1984-2005). DFONT, created by Apple in 2001 during Mac OS X launch, stores TrueType data in Unix-compatible data fork format for macOS desktop installation exclusively, with zero web compatibility and no support on Windows, Linux, or mobile platforms. PFB, created by Adobe in 1984 as part of the PostScript specification, stores Type 1 font data as binary-encoded cubic Bézier curves in a two-file system (PFB for outlines + PFM/AFM for metrics), designed for PostScript printers and professional typesetting until OpenType unified the industry.
The critical distinction is era and success: DFONT is a platform-specific format that still works on macOS but limits interoperability (Mac-only by design, legacy), while PFB was a successful industry standard that has been completely replaced by OpenType (universal desktop standard, now obsolete). Both contain similar TrueType data in DFONT's case or PostScript data in PFB's case, but neither is suitable for modern workflows. Modern macOS fully supports standard OTF/TTF files making DFONT unnecessary, and PFB has been deprecated by all modern operating systems in favor of OpenType. As of 2025, both formats should be converted to universal standards—OTF/TTF for desktop use and WOFF2/WOFF for web deployment.
This guide compares DFONT and PFB to clarify why both legacy desktop formats should be replaced with modern standards. You'll learn the technical specifications showing DFONT's Mac-only structure versus PFB's PostScript heritage, use cases demonstrating both formats' limitations, platform compatibility showing severe restrictions for both, historical context explaining their creation across two decades, and definitive recommendations to use OTF/TTF for desktop and WOFF2/WOFF for web. Whether managing Mac font libraries or maintaining legacy documents, this guide provides essential knowledge about two desktop formats that represent platform-specific and era-specific limitations.
Format Overview
DFONT (Data Fork Font)
History and Purpose:
- • Created by Apple (2001) for Mac OS X
- • Transition from Classic Mac resource forks
- • Desktop installation only (macOS exclusive)
- • Never intended for web or cross-platform
- • Legacy: Mac-only limitation
Technical Characteristics:
- • Contains TrueType data in data fork
- • Uncompressed binary format
- • File size: ~150-300 KB
- • Extension: .dfont
Current Status (2025):
- • Works on macOS desktop only
- • Legacy format
- • Use case: Legacy Mac systems only
PFB (PostScript Font Binary)
History and Purpose:
- • Created by Adobe (1984) for PostScript
- • Dominated professional publishing 1984-2005
- • PostScript printers and imagesetters
- • Replaced by OpenType (OTF) mid-2000s
- • Obsolete: foundries stopped distribution
Technical Characteristics:
- • PostScript Type 1, cubic Bézier curves
- • Two-file system: PFB + PFM/AFM
- • File size: ~40-120 KB (outline only)
- • Extension: .pfb/.pfa
Current Status (2025):
- • Obsolete desktop format
- • Replaced by OpenType
- • Use case: Legacy documents only
Two Legacy Desktop Formats
- DFONT: Mac-only, still works but limited, use OTF/TTF instead
- PFB: Multi-platform historically, now obsolete, replaced by OTF
- Common issue: Both limit interoperability, both legacy
- Modern solution: OTF/TTF (desktop), WOFF2/WOFF (web)
Technical Differences
Side-by-Side Comparison
| Feature | DFONT | PFB |
|---|---|---|
| Creator | Apple (2001) | Adobe (1984) |
| Era | 2001-present | 1984-2005 |
| Purpose | Desktop (Mac only) | Desktop/print (PostScript) |
| Font Data | TrueType | PostScript Type 1 |
| Curves | Quadratic Bézier | Cubic Bézier |
| File Structure | Single file | Two files (PFB+PFM) |
| Compression | None | None |
| Cross-Platform | No (Mac only) | Was (now deprecated) |
| Status | Legacy (Mac) | Obsolete |
DFONT Limitations
- macOS only: Cannot install on Windows/Linux
- No web support: Browsers don't recognize DFONT
- Data fork structure: macOS-specific file system
- Interoperability: Limited file sharing with non-Mac users
- Modern macOS: Fully supports OTF/TTF, DFONT unnecessary
PFB Obsolescence
- Replaced by OpenType: OTF unified PostScript and TrueType
- OS deprecation: Windows/macOS prefer OTF/TTF
- Two-file complexity: PFB + metrics harder than single OTF
- Limited features: Can't support OpenType GSUB/GPOS
- Industry transition: Foundries stopped distributing by mid-2000s
Use Cases and Context
When You Encounter DFONT:
- • Legacy Mac systems: Old applications from 2001-2010
- • System fonts: Some bundled Apple fonts
- • Archives: Old Mac font collections
- • Action: Convert to OTF/TTF for universal compatibility
When You Encounter PFB:
- • Legacy documents: Old InDesign/QuarkXPress files 1990s-2000s
- • Font archives: Collections from pre-OpenType era
- • Print production: Historical materials from PostScript era
- • Action: Convert PFB to OTF (CFF) to preserve PostScript curves
Modern Alternatives:
- • Desktop: OTF/TTF, works on all platforms
- • Web: WOFF2 (primary) + WOFF (fallback)
- • Result: Universal compatibility, no limitations
Platform Compatibility
Platform Support Matrix
| Platform | DFONT | PFB |
|---|---|---|
| Web Browsers | ✗ | ✗ |
| Windows Desktop | ✗ | ~ |
| macOS Desktop | ✓ | ~ |
| Linux Desktop | ✗ | ~ |
| Mobile | ✗ | ✗ |
~ = Limited/deprecated | ✓ = Supported | ✗ = Not supported
Historical Context
Timeline: Two Decades
- 1984: Adobe creates PostScript, Type 1 (PFB)
- 1984-2005: PFB dominates professional publishing
- 1996: OpenType created to unify formats
- 2000s: Industry transitions from PFB to OTF
- 2001: Apple creates DFONT for Mac OS X transition
- 2025: PFB obsolete, DFONT legacy Mac-only
Why Both Are Legacy
- • DFONT: Mac-only design limits adoption
- • PFB: Replaced by superior OpenType standard
- • Universal standards won: OTF/TTF work everywhere
Modern Recommendations
Use Universal Formats:
- • Desktop: OTF/TTF, all platforms
- • Web: WOFF2 + WOFF, 99%+
- • Result: Universal compatibility
Replace Legacy Formats:
- • DFONT: Convert to OTF/TTF (FontForge)
- • PFB: Convert to OTF (CFF) to preserve curves
- • Action: Use modern standards for new work
Migration Checklist
- ☐ Convert DFONT to OTF/TTF (FontForge)
- ☐ Convert PFB to OTF (CFF) (FontForge/AFDKO)
- ☐ Install OTF/TTF for desktop
- ☐ Convert OTF to WOFF2 + WOFF for web
- ☐ Test all target platforms
- ☐ Archive originals for legacy
Summary: DFONT vs PFB
DFONT and PFB represent two legacy desktop formats from different eras. DFONT (Apple 2001) is Mac-only container with TrueType data, still works on macOS but limits interoperability. PFB (Adobe 1984) is obsolete PostScript Type 1 format, dominated publishing 1984-2005 but replaced by OpenType. Both demonstrate limitations—DFONT platform lock-in, PFB era-specific obsolescence. Use OTF/TTF for desktop (universal compatibility) and WOFF2/WOFF for web (99%+ support). Convert DFONT to OTF/TTF for cross-platform. Convert PFB to OTF (CFF) to preserve PostScript curves. Modern standards eliminate platform and era limitations.
Written & Verified by
Sarah Mitchell
Product Designer, Font Specialist
DFONT vs PFB FAQs
Common questions answered about this font format comparison