WOFF vs PFB: Complete Format Comparison
Comprehensive comparison of WOFF and PFB formats covering modern web standard versus legacy PostScript, the evolution from desktop publishing to universal web fonts, and migration from Type 1 to OpenType
In Simple Terms
PFB is deprecated legacy desktop format (Adobe ended support 2023). WOFF is web font standard. Different eras and purposes—not comparable.Convert PFB to OTF first (desktop use), then OTF to WOFF2 (web use). WOFF is for browsers only, cannot install on desktop.Modern workflow: Use OTF for desktop, WOFF2 for web. PFB has no place in 2025 workflows—migrate immediately to avoid compatibility issues.
In this article
WOFF (Web Open Font Format) and PFB (PostScript Font Binary) represent two generations of typography technology from completely different eras, with WOFF being the modern web font standard (2009-2012) and PFB being the legacy PostScript Type 1 desktop format that dominated professional publishing from 1984 to the early 2000s. WOFF, created collaboratively by Mozilla, Opera, and Microsoft and standardized by W3C in 2012, uses zlib compression on OpenType/TrueType font data to deliver fonts efficiently over HTTP with universal browser support. PFB, created by Adobe as part of the PostScript specification in 1984, stores PostScript 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.
The fundamental distinction is era, purpose, and platform: WOFF is the active web font standard for 2025 with 99%+ browser support globally, while PFB is an obsolete desktop format that modern operating systems have deprecated in favor of OpenType. WOFF wraps either TrueType or PostScript/CFF outlines (WOFF can contain the same cubic Bézier curves as PFB) and adds web-specific features like metadata and compression. PFB represents the original PostScript Type 1 technology that OpenType replaced—most foundries stopped distributing PFB files in the mid-2000s when the industry transitioned to OpenType (OTF/TTF). WOFF cannot be installed as a desktop font, and PFB cannot be used directly on the web without conversion.
This comprehensive guide compares WOFF and PFB to clarify their relationship across typography's evolution from desktop publishing to universal web delivery. You'll learn the technical specifications showing WOFF's web optimization versus PFB's PostScript printing heritage, platform compatibility demonstrating WOFF's universal browser support versus PFB's declining desktop support, historical context of how OpenType unified PostScript and TrueType technologies, migration paths from legacy PFB to modern OTF then WOFF2 for web, and recommendations for managing fonts across both desktop and web contexts. Whether maintaining legacy documents or modernizing font workflows, this guide provides essential knowledge.
Format Overview
WOFF (Web Open Font Format)
History and Purpose:
- • Created by Mozilla, Opera, Microsoft (2009)
- • W3C Recommendation (2012)
- • Designed for universal web font delivery
- • Replaced proprietary web formats (EOT, SVG)
- • Industry standard since 2013
Technical Characteristics:
- • Wraps OpenType/TrueType data
- • Can contain TrueType or PostScript/CFF outlines
- • zlib compression (40-50% reduction)
- • Metadata for licensing information
- • Extension: .woff
Current Status (2025):
- • Universal browser support (99%+)
- • Active web standard
- • File size: ~90 KB (typical Latin font)
- • Use case: Web font delivery
PFB (PostScript Font Binary)
History and Purpose:
- • Created by Adobe (1984) as part of PostScript
- • Dominated professional publishing 1984-2005
- • Designed for PostScript printers and RIPs
- • Replaced by OpenType (OTF) in mid-2000s
- • Legacy format, no longer distributed
Technical Characteristics:
- • PostScript Type 1 format
- • Cubic Bézier curves (3 control points)
- • Two-file system: PFB + PFM/AFM
- • Binary-encoded PostScript commands
- • Extension: .pfb (binary) or .pfa (ASCII)
Current Status (2025):
- • Obsolete desktop format
- • Deprecated by modern operating systems
- • File size: ~40-120 KB (outline data only)
- • Use case: Legacy document support only
Different Eras, Different Purposes
WOFF and PFB represent typography's evolution:
- PFB (1984-2005): Desktop publishing era, PostScript dominance
- OpenType (1996-present): Unified desktop standard, replaced PFB
- WOFF (2009-present): Web fonts era, universal browser delivery
- Relationship: WOFF can wrap PostScript data (same curves as PFB)
- Modern path: PFB → OTF (desktop) → WOFF2/WOFF (web)
Technical Differences
Comprehensive Comparison
| Feature | WOFF | PFB |
|---|---|---|
| Era | 2009-present (web fonts) | 1984-2005 (desktop) |
| Purpose | Web font delivery | Desktop/print PostScript |
| Platform | All browsers, all OS | Desktop only |
| Compression | zlib (40-50%) | None |
| File Structure | Single unified file | Two files (PFB + PFM/AFM) |
| Curves | TrueType or PostScript | PostScript (cubic Bézier) |
| OpenType Features | Full support | Limited/basic |
| Web Use | Yes (designed for it) | No (never supported) |
| Status | Active standard | Obsolete |
WOFF Can Contain PostScript Data
WOFF is a wrapper that can contain the same curves as PFB:
- WOFF with TrueType: Contains quadratic Bézier curves
- WOFF with PostScript/CFF: Contains cubic Bézier curves (same as PFB)
- Conversion: PFB → OTF (CFF) → WOFF preserves PostScript curves
- Result: Same font quality, modern delivery format
File Size Comparison
Example: Roboto Regular font (Latin character set)
| Format | File Size | Use Case |
|---|---|---|
| PFB | ~80 KB | Legacy desktop (obsolete) |
| OTF (CFF) | 168 KB | Modern desktop |
| WOFF | 90 KB | Web delivery |
| WOFF2 | 53 KB | Modern web (best) |
Why PFB is Obsolete
- Replaced by OpenType: OTF unified PostScript and TrueType (1996)
- Industry transition: Foundries stopped distributing PFB in mid-2000s
- OS deprecation: Modern Windows/macOS prefer OTF/TTF
- No web support: Cannot use PFB directly on web
- Two-file complexity: PFB + PFM/AFM harder than single OTF
- Limited features: Can't support advanced OpenType capabilities
Platform Compatibility
Platform Support Matrix
| Platform | WOFF | PFB |
|---|---|---|
| Web Browsers (All) | ✓ | ✗ |
| Windows 11/10 | ~ | ~ |
| macOS (Modern) | ~ | ~ |
| Linux | ~ | ~ |
| Mobile (iOS/Android) | ✓ | ✗ |
~ = Limited/deprecated desktop support; prefer OTF/TTF
✓ = Full web browser support
✗ = No support
WOFF Universal Web Support
- • All browsers: Chrome, Firefox, Safari, Edge (99%+)
- • All platforms: Windows, macOS, Linux, mobile
- • Designed for web: HTTP delivery, @font-face support
- • Active standard: W3C Recommendation, widely deployed
- • Future-proof: Led to WOFF2 with better compression
PFB Limited Desktop Support
- • Modern Windows: Limited support, requires ATM (discontinued 2013)
- • Modern macOS: Deprecated PostScript Type 1 fonts
- • Adobe CC: Still supports but recommends converting to OTF
- • Web: Zero support, cannot use directly
- • Mobile: No support on iOS or Android
Historical Context
Typography Evolution Timeline
- 1984: Adobe creates PostScript and Type 1 fonts (PFB)
- 1984-1996: PFB dominates professional publishing
- 1991: Apple/Microsoft introduce TrueType as alternative
- 1996: Adobe + Microsoft create OpenType to unify formats
- 2000s: Industry transitions from PFB to OTF
- 2009: WOFF created for web font delivery
- 2012: WOFF becomes W3C standard
- 2025: WOFF/WOFF2 universal, PFB obsolete
Why OpenType Replaced PFB
- Format unification: One format supporting both TrueType and PostScript
- Single file: Simpler than PFB + PFM/AFM two-file system
- Cross-platform: Works identically on Windows, Mac, Linux
- Advanced features: GSUB/GPOS tables PFB couldn't support
- Industry consensus: Adobe endorsed OpenType over its own Type 1
Why WOFF Succeeded for Web
- • Web-optimized: Compressed for HTTP delivery
- • Universal support: All browsers adopted by 2013
- • Open standard: W3C specification enabled trust
- • Metadata support: Licensing information embedded
- • Modern foundation: Led to WOFF2 with Brotli compression
Migration Path
Complete Migration Workflow
- Identify PFB fonts: Locate legacy PostScript Type 1 fonts
- Check licensing: Verify conversion rights
- PFB → OTF (CFF): Convert to OpenType with PostScript outlines
- Install OTF: Use for desktop applications
- OTF → WOFF2: Convert to modern web format (primary)
- OTF → WOFF: Convert to web fallback format
- Implement @font-face: Deploy on website
- Archive PFB: Keep for legacy document support
Conversion Tools and Methods
PFB to OTF Conversion:
- • FontForge: Open source, preserves PostScript curves
- • AFDKO: Adobe Font Development Kit (pip install afdko)
- • Online converters: font-converters.com
OTF to WOFF/WOFF2:
- • FontTools: pip install fonttools brotli
- • Online converters: font-converters.com
- • Build tools: Webpack, Gulp font plugins
Modern Web Font Implementation
/* Modern web font stack (no PFB) */
@font-face {
font-family: 'MyFont';
src: url('/fonts/font.woff2') format('woff2'),
url('/fonts/font.woff') format('woff');
font-weight: 400;
font-style: normal;
font-display: swap;
}
/* Migration path:
1. PFB (legacy) → FontForge → OTF (CFF)
2. OTF → FontTools → WOFF2 + WOFF
3. Deploy web fonts
4. Archive PFB for legacy documents */Modern Recommendations
Use WOFF/WOFF2 For Web:
- • Primary: WOFF2 (97%+ browsers, best compression)
- • Fallback: WOFF (99%+ browsers)
- • Universal: Works on all platforms and devices
- • Optimized: Designed for web delivery
- • Standard: W3C Recommendation, industry best practice
When You Encounter PFB:
- • Legacy documents: Old InDesign/QuarkXPress files
- • Font archives: Collections from 1990s-2000s
- • Print production: Historical materials
Action: Convert PFB to OTF (CFF) for desktop, then WOFF2/WOFF for web.
Never Use PFB For:
- • New projects: Use OTF/TTF for desktop
- • Web fonts: Zero browser support, won't work
- • Modern workflows: Deprecated by operating systems
- • Cross-platform: Limited compatibility
Complete Font Strategy
- ☐ Convert legacy PFB to OTF (CFF)
- ☐ Use OTF/TTF for desktop work
- ☐ Convert OTF to WOFF2 + WOFF for web
- ☐ Never use PFB for new projects
- ☐ Archive PFB only for legacy documents
- ☐ Test converted fonts in applications
- ☐ Verify web fonts in browsers
- ☐ Document font sources and licenses
Summary: WOFF vs PFB
WOFF and PFB represent different eras in typography: WOFF is the modern web font standard (W3C 2012) with universal browser support, while PFB is the obsolete PostScript Type 1 desktop format (Adobe 1984) that dominated professional publishing but was replaced by OpenType in the mid-2000s. WOFF uses zlib compression on OpenType/TrueType data for efficient web delivery at ~90 KB per font. PFB stores uncompressed PostScript Type 1 data in a two-file system (PFB + PFM/AFM) at ~80 KB for outline data only.
Use WOFF2 (primary) and WOFF (fallback) for all web font delivery. Never use PFB for new work—it's obsolete with deprecated OS support and zero web compatibility. Convert legacy PFB to OTF (CFF) to preserve PostScript curves for desktop use, then convert OTF to WOFF2/WOFF for web deployment. WOFF can contain the same cubic Bézier curves as PFB through PostScript/CFF outlines. Modern path: PFB (1984-2005) → OTF (1996-present desktop) → WOFF/WOFF2 (2009-present web). Typography has evolved from desktop-only PostScript to universal web delivery.
Written & Verified by
Sarah Mitchell
Product Designer, Font Specialist
WOFF vs PFB FAQs
Common questions answered about this font format comparison