What is the DFONT file format?
A .dfont file is a Mac OS X font container that stores TrueType or OpenType font data in a file's regular data fork rather than in the HFS+ resource fork. Apple introduced the format with Mac OS X 10.0 (March 2001) to solve a cross-platform compatibility problem: Classic Mac OS fonts stored glyph data exclusively in HFS resource forks, which were silently stripped when files were copied to FAT, SMB, or other non-HFS volumes.
The solution was to replicate the resource fork layout byte-for-byte into the data fork and mandate the .dfont extension. The file begins with 16 zero bytes where a resource fork header would normally sit, then continues with a standard resource map and resource data sections containing sfnt blobs (the actual TrueType or OpenType outlines) and optional FOND family records. Multiple font faces - Regular, Bold, Italic, Bold Italic - can be bundled into a single .dfont suitcase.
By macOS 10.6 Snow Leopard (2009), Apple migrated most system fonts to plain .ttf and .otf files. A small set of legacy .dfont files remains in /System/Library/Fonts/ for backward compatibility. The sfnt records inside a .dfont are fully valid TrueType or OpenType data - tools such as FontForge and DfontSplitter can extract them as standard .ttf files usable on any platform.
macOS Font Book opens .dfont files natively. On Windows the format is not recognized by the OS; third-party extraction tools are required.
Security & safety
RISK: LOWFont files are read by the OS font renderer; malformed fonts have historically caused kernel panics on macOS (rare). Only install .dfont files from trusted sources.
Format details
in a nutshellPrograms that open DFONT files
Technical details
deep spec| Byte order | Big-endian (matches Classic Mac OS resource fork convention) |
| File header | 16 zero bytes at offset 0 - resource fork placeholder; signals that the resource map follows immediately after |
| Internal container | Mac OS resource fork structure (resource map + resource data sections) stored verbatim in the data fork |
| Primary resource type | `sfnt` blobs - contain valid TrueType or OpenType (CFF or glyf table) outline data |
| Secondary resource type | `FOND` (Font Family Descriptor) records for family metadata and legacy bitmap font sizes |
| Multi-face bundling | A single `.dfont` may contain multiple faces (Regular, Bold, Italic, Bold Italic) as separate `sfnt` resources within one file |
| Glyph format inside | TrueType quadratic Bezier outlines or OpenType CFF cubic outlines within the `sfnt` stream |
| Typical size | 20 KB - 5 MB (varies with glyph count, number of faces, and hinting data) |
| Encoding | Binary, big-endian resource fork layout |
| Extraction compatibility | `sfnt` streams are valid standalone TrueType/OpenType; extractable by DfontSplitter, FontForge, and the `fondu` command-line utility |
| System font path | `/System/Library/Fonts/` - legacy Apple system fonts remain as `.dfont` after most migrated to `.ttf`/`.otf` in macOS 10.6 |
| File type code | HFS+ file type code `dfon`; no fixed magic bytes (file starts with 16 zero bytes) |
| Windows compatibility | Not natively installable on Windows; requires extraction of `sfnt` resources to `.ttf` via DfontSplitter or similar tools |
| Compression | None - glyph data stored uncompressed within resource blobs |
| Released | 2001 (Mac OS X 10.0) |
| Latest version | No versioned spec; format frozen at introduction |
| Open standard | Yes · royalty-free |
| Specification | fontforge.org |
DFONT conversions
Community Q&A
asked by usersNo questions yet - be the first to ask about DFONT files.