How to svg fonts vs modern formats: how we got here
- Step 1Recognise the era — SVG Fonts were spec'd around 2003 and saw experimental browser support 2008–2014. The peak was iOS Safari, where they powered some retina-era web typography hacks before WOFF and WOFF2 arrived.
- Step 2Track the deprecation — Chrome dropped SVG Font support in 2017. Firefox never properly implemented it. Edge inherited Chrome's stance. Safari kept partial support longest but is functionally inert in 2026.
- Step 3Find the surviving consumers — PrinceXML, WeasyPrint, and similar HTML-to-PDF libraries still consume SVG Fonts in some pipelines. Some Kindle and Kobo e-reader engines accept them. Specialty renderers occasionally lean on them. For all other use cases, WOFF2 is correct.
Frequently asked questions
Was SVG Font support ever good?+
In Safari, briefly. Other browsers either omitted it or implemented partial subsets that didn't render all features. The fragmented support is what doomed it commercially — designers couldn't rely on consistent rendering.
Why didn't WOFF supersede SVG Font earlier?+
Specs ran in parallel. SVG Font shipped first (early 2000s) but WOFF (2010) had the W3C blessing and unified browser support. By 2013, WOFF was clearly the winner; SVG Font lingered as a fallback for two more years before deprecation.
Is there any modern niche?+
PDF generation pipelines (Prince, WeasyPrint), some Linux GUI engines that predate Pango's WOFF2 support, and a handful of game engines that consume SVG-derived fonts. Always confirm the target consumer needs SVG Font before producing one.
Privacy first
Every JAD Font tool runs entirely in your browser using opentype.js and the wawoff2 WASM Brotli encoder. Your fonts never leave your device — verified by zero outbound network requests during processing.