SVG vs PFB: Complete Format Comparison
Comprehensive comparison of SVG and PFB formats covering failed web experiment versus obsolete PostScript, two eras of typography failure, and why both are obsolete
In Simple Terms
Both SVG fonts and PFB are completely obsolete. SVG fonts (0% browser support, removed 2018), PFB (deprecated, Adobe ended support 2023).SVG failed due to XML bloat (289% larger than WOFF). PFB succeeded for 20 years but was replaced by superior OpenType format.Convert both to modern formats immediately: PFB to OTF for desktop, then OTF to WOFF2 for web. Never use SVG or PFB in new projects.
In this article
SVG fonts and PFB (PostScript Font Binary) represent two failed font technologies from different eras separated by nearly two decades, with SVG fonts being a catastrophic web font experiment using XML text encoding (2001-2018, 0% support now) and PFB being Adobe's PostScript Type 1 desktop format that dominated professional publishing (1984-2005) before being replaced by OpenType. SVG fonts, introduced in SVG 1.1 specification (2001), encode glyphs as verbose XML text producing files 289% larger than WOFF (350 KB vs 90 KB) with slow XML parsing, no hinting support, and complete industry rejection—Chrome removed support in 2013, Safari iOS in 2018. 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 failure mode: SVG fonts attempted web delivery but failed due to catastrophic technical incompetence (XML bloat destroying performance), while PFB succeeded as desktop publishing standard for 20 years but was eventually replaced by the superior OpenType format. As of 2025, both have 0% web support and declining desktop support. SVG fonts have been completely removed from all browsers. PFB is deprecated by modern operating systems—Windows requires discontinued Adobe Type Manager, macOS prefers OTF, foundries stopped distributing PFB files by mid-2000s. Both demonstrate different paths to obsolescence: SVG fonts failed immediately due to terrible design, PFB succeeded temporarily but was replaced by a better open standard.
This guide compares SVG fonts and PFB to understand how formats from different eras both became obsolete. You'll learn the technical specifications showing SVG's XML disaster versus PFB's PostScript heritage, platform compatibility demonstrating both formats' current limitations, historical context spanning 40 years of typography evolution from desktop PostScript to failed web experiments, complete migration paths from both legacy formats to modern standards, and definitive recommendations to use WOFF2/WOFF for web and OTF for desktop. Whether maintaining legacy documents or understanding font format history, this guide provides essential knowledge about two obsolete formats that represent technical failure and industry evolution.
Format Overview
SVG Font Format
History and Purpose:
- • SVG 1.1 specification (2001)
- • Experimental web font using XML
- • Brief Safari iOS use (2008-2018)
- • Never mainstream, industry rejected
- • Obsolete: 0% browser support
Technical Characteristics:
- • XML text, verbose markup
- • 289% larger than WOFF (350 KB vs 90 KB)
- • Slow XML + SVG rendering
- • No hinting
- • Extension: .svg
Current Status (2025):
- • Zero support (removed)
- • Failed: technical incompetence
- • Use case: None
PFB (PostScript Font Binary)
History and Purpose:
- • Adobe PostScript (1984)
- • Dominated publishing 1984-2005
- • PostScript printers/RIPs
- • Replaced by OpenType mid-2000s
- • Obsolete: foundries stopped distribution
Technical Characteristics:
- • PostScript Type 1, cubic Bézier
- • Two files: PFB + PFM/AFM
- • Binary-encoded PostScript
- • File size: ~40-120 KB
- • Extension: .pfb/.pfa
Current Status (2025):
- • Obsolete desktop format
- • Replaced by OpenType
- • Use case: Legacy documents only
Two Eras, Both Obsolete
- SVG (2001-2018): Failed web font, XML bloat, 0% support
- PFB (1984-2005): Successful desktop, replaced by OpenType
- Different failures: SVG immediate technical failure, PFB eventual replacement
- Modern replacements: WOFF2/WOFF (web), OTF/TTF (desktop)
Technical Differences
Comprehensive Comparison
| Feature | SVG | PFB |
|---|---|---|
| Creator | W3C (2001) | Adobe (1984) |
| Era | 2001-2018 (web) | 1984-2005 (desktop) |
| Purpose | Web font delivery | Desktop/print PostScript |
| Data Format | XML/Text (bloat) | Binary (PostScript) |
| Compression | None | None |
| File Size | ~350 KB (massive) | ~80 KB |
| Curves | SVG paths | Cubic Bézier |
| Web Support | Was (0% now) | Never |
| Status | Obsolete (0%) | Obsolete |
SVG Fonts' Fatal Technical Flaws
- XML bloat: 350 KB vs 80 KB PFB (338% larger)
- Overhead: Tags/attributes add 100-200% size
- Slow parsing: XML slower than binary
- No hinting: Poor quality at small sizes
- Complete rejection: Chrome removed 2013, Safari 2018
PFB's Obsolescence Path
- 20-year success: Industry standard 1984-2005
- OpenType replaced: Unified format better than Type 1
- 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
Platform Compatibility
Platform Support Matrix
| Platform | SVG | PFB |
|---|---|---|
| Web Browsers | ✗ (0%) | ✗ |
| Windows Desktop | ✗ | ~ |
| macOS Desktop | ✗ | ~ |
| Linux Desktop | ✗ | ~ |
| Mobile | ✗ | ✗ |
~ = Limited/deprecated
✗ = No support
Historical Context
40-Year Timeline
- 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: SVG 1.1 introduces SVG fonts
- 2009: WOFF created as proper web standard
- 2013: Chrome removes SVG fonts
- 2018: Safari removes SVG fonts, WOFF2 standard
- 2025: Both SVG and PFB obsolete
Why Both Failed
- • SVG: Technical incompetence, XML bloat catastrophic
- • PFB: Superseded by superior OpenType standard
- • Open standards won: WOFF/OTF succeeded through collaboration
Migration Strategy
Complete Migration Path
From SVG (Web):
- Remove all SVG font references from CSS
- Delete .svg font files
- Obtain OTF/TTF source fonts
- Convert to WOFF2 + WOFF
- Implement modern @font-face
From PFB (Desktop):
- Identify PFB fonts
- Convert PFB → OTF (CFF) using FontForge/AFDKO
- Install OTF for desktop
- Convert OTF → WOFF2 + WOFF for web
- Archive PFB for legacy documents
Modern Implementation
/* Modern web font stack */
@font-face {
font-family: 'MyFont';
src: url('/fonts/font.woff2') format('woff2'),
url('/fonts/font.woff') format('woff');
font-display: swap;
}
/* No SVG: 0% support, obsolete */
/* No PFB: Desktop only, obsolete */
/* WOFF2: 97%+, 53 KB (primary) */
/* WOFF: 99%+, 90 KB (fallback) */Modern Recommendations
Use Modern Standards:
- • Web: WOFF2 + WOFF, 99%+ coverage
- • Desktop: OTF/TTF, universal
- • Result: Optimal performance, universal compatibility
Never Use SVG or PFB:
- • SVG: 0% support, completely obsolete
- • PFB: Deprecated, replaced by OTF
- • Action: Remove/convert immediately
Migration Checklist
- ☐ Remove all SVG font references
- ☐ Delete .svg files
- ☐ Convert PFB to OTF (CFF)
- ☐ Convert OTF to WOFF2 + WOFF for web
- ☐ Test all target platforms
- ☐ Archive originals for legacy
Summary: SVG vs PFB
SVG fonts and PFB represent failed technologies from different eras. SVG fonts (W3C 2001) failed as web format due to catastrophic XML bloat—350 KB files (289% larger than WOFF), slow parsing, no hinting, resulting in 0% browser support. PFB (Adobe 1984) succeeded as desktop publishing standard for 20 years but was replaced by OpenType in mid-2000s. Both demonstrate different obsolescence paths—SVG immediate technical failure, PFB eventual replacement by superior standard. Use WOFF2/WOFF for web (99%+) and OTF/TTF for desktop (universal). Remove all SVG references immediately. Convert PFB to OTF for desktop, then to WOFF2/WOFF for web.
Written & Verified by
Sarah Mitchell
Product Designer, Font Specialist
SVG vs PFB FAQs
Common questions answered about this font format comparison