DFONT (Apple Data Fork Font)
The font format Apple invented to rescue Mac typefaces when Mac OS X dropped support for resource forks.
| Full name | Apple Data Fork Font |
| Extension | .dfont |
| MIME type | application/x-dfont |
| Developer | Apple Inc. |
| Released | 2001 (with Mac OS X 10.0) |
| Type | TrueType font in data-fork container |
| Based on | TrueType / SFNT resource format |
| Deprecated | Mac OS X 10.6 Snow Leopard (2009) — replaced by .ttf and .ttc |
What is a DFONT file?
DFONT is a font format created by Apple for Mac OS X, released in 2001. It stores TrueType font data entirely in a file's data fork, instead of the resource fork that Classic Mac OS fonts relied on. Apple shipped system fonts like Courier, Helvetica, Monaco, and Times as DFONT files for the first several versions of Mac OS X.
A DFONT file is a TrueType font wrapped in a data-fork resource container. Classic Mac OS stored font data in the resource fork of a file, a Mac-specific metadata section that other operating systems could not read. Mac OS X dropped support for resource-fork-only storage, so Apple moved the font data into the main data section of the file while keeping the internal SFNT resource structure intact. The result looks nearly identical to a resource-fork font on the inside, except the first 16 bytes of the map table are zeros instead of a copy of the file header. Only SFNT and FOND resource types have ever appeared inside a DFONT file.
History
Apple introduced DFONT with the launch of Mac OS X 10.0 in March 2001. The format solved a specific transition problem: Mac OS X was built on a Unix foundation that did not understand the two-fork file system of Classic Mac OS, so existing system fonts needed a new home for their data. Apple used DFONT for core system typefaces through Mac OS X 10.5 Leopard. Starting with Mac OS X 10.6 Snow Leopard in 2009, Apple replaced most DFONT system fonts with standard TrueType (.ttf) and TrueType Collection (.ttc) files, leaving only a handful of DFONT files behind. By the early 2010s the format was effectively a legacy artifact.
How it works
Internally, a DFONT file follows the Macintosh resource file format, but the resource data sits in the data fork rather than a separate resource fork. The file begins with a resource header pointing to the resource data and the resource map. The map table starts with 16 null bytes where a resource-fork file would copy the first 16 bytes of the header. Font outlines and metrics are stored inside SFNT resources, the same container format that TrueType uses on other platforms. A single DFONT file can hold multiple fonts at different sizes or weights, all packed as separate resources within the same container.
What it is used for
- Installing legacy Mac system fonts (Courier, Helvetica, Monaco, Times) on older macOS versions
- Recovering or converting classic Apple fonts from pre-Snow Leopard Mac installations
- Working with vintage Mac software or design projects that shipped with DFONT system typefaces
- Converting DFONT files to TTF or OTF so they work on Windows, Linux, or modern macOS tools
How to open it
On macOS, Font Book opens DFONT files directly by double-clicking them. To convert a DFONT to a cross-platform format like TTF, use an online converter or a tool like FontForge, which reads DFONT files and can export to any standard font format.
Pros and cons
Strengths
- Preserved TrueType font quality and hinting from Classic Mac OS with no data loss
- Single file holds multiple font weights or sizes as separate internal resources
- Internally identical to the resource-fork format, so existing font tools needed minimal changes to support it
- Worked transparently with all Mac OS X applications that called Apple's font APIs
Trade-offs
- Not supported on Windows or Linux without conversion — purely a Mac format
- Deprecated since 2009; modern macOS tools and apps prefer TTF, OTF, or TTC
- Can cause naming conflicts with PostScript or TrueType fonts sharing the same family name
- Limited tooling outside the Mac ecosystem; few cross-platform editors handle DFONT natively
Convert DFONT files
Free, in your browser, no signup. Start at the DFONT converter, or jump straight to a popular conversion below.
Curious how fast and how small? See our measured conversion benchmarks.
DFONT FAQ
Can I use a DFONT file on Windows?
No. Windows does not recognize the DFONT container. You need to convert the file to TTF or OTF first. Once converted, the font installs and works normally on any platform.
Is DFONT the same as TrueType?
DFONT contains TrueType font data, but the outer container is different. A standard TTF file stores everything in a flat binary structure. A DFONT wraps the same TrueType data inside a Mac resource container placed in the file's data fork. The outlines and metrics are identical; only the packaging differs.
Why did Apple stop using DFONT?
Apple switched most system fonts to TTF and TTC format with Mac OS X 10.6 Snow Leopard in 2009. Standard TrueType and OpenType fonts are cross-platform, better supported by third-party tools, and do not require Apple-specific resource handling. There was no longer a reason to maintain a proprietary container.
Can a DFONT file contain more than one font?
Yes. The resource container inside a DFONT file can hold multiple SFNT resources, each representing a separate font face. This is similar to how a TrueType Collection (.ttc) file bundles multiple fonts, and it was how Apple packaged font families like Helvetica in early Mac OS X.