Font and Metadata Formats
Recall the format taxonomy in Understanding Font Formats. Choose among four categories:
- Source formats preserve editable development data for continuing work.
- Production or final formats deliver fonts to applications, operating systems, or browsers.
- Interchange formats transfer a project between authoring tools.
- Metadata formats transfer selected information, such as metrics or feature code, rather than a complete font.
Font Formats
Use native FontLab sources for continuing work. VFC is the compact binary format; VFJ stores font data as JSON; VFJP organizes a native project as a package of files. Native saving preserves the editable font-design data losslessly; optional session and workspace information still depends on save settings. A production file is not a complete replacement for that source.
Saving a native source and exporting a deliverable are separate operations. An export can resolve live constructions, convert outlines, rebuild tables, and omit editing information. Retain the native source even when the exported appearance is correct.
The principal format routes are:
| Format | Extension | Read/import | Write route |
|---|---|---|---|
| FontLab binary | .vfc |
Open | Native save |
| FontLab JSON | .vfj |
Open | Native save |
| FontLab project package | .vfjp |
Open project | Native project save |
| OpenType TT / Variable TT | .ttf |
Open | Font export |
| OpenType PS / Variable PS | .otf |
Open | Font export |
| Font collections | .ttc, .otc |
Open supported faces | Not the ordinary single-font export route |
| Color OpenType | .ttf or .otf |
Open supported color data | Profile-dependent font export |
| WOFF / WOFF2 | .woff, .woff2 |
Open | Web export |
| EOT | .eot |
Open supported files | Legacy web export |
| Windows Type 1 | .pfb |
Open | Legacy font export |
| Mac Type 1 suitcase | Suitcase and associated files | Import | Not a native save target |
| UFO / compressed UFO | .ufo, .ufoz |
Open/import | Interchange export |
| DesignSpace with UFO masters | .designspace |
Open project | Interchange export |
| Extended Font Object | .xfo |
Compatibility import | Not offered as a standard export profile |
| Glyphs | .glyphs |
Open versions 2/3 | Interchange export |
| FontLab Studio source | .vfb |
Open | Legacy interchange export |
| Fontographer | .fog |
Import | Not an ordinary export target |
| PhotoFont | .phf |
Import | Not an ordinary export target |
| Ikarus | .ik |
Import | Not an ordinary export target |
| Bitmap Distribution Format | .bdf |
Import | Converted through supported font/artwork output |
Production OpenType contains the glyphs, metrics, names, layout, and other tables needed by consumers. It generally does not preserve the editor's notes, guides, recipes, or live filter controls as editable source objects.
Interchange formats can carry much more source information, but another editor may interpret application-specific data differently. A format being readable does not guarantee that every structure can be written back unchanged.
Open Font Format 2026 input
FontLab can open supported fonts using the Open Font Format 2026 extensions, including large-glyph and layout tables, cubic TrueType outlines, VARC variable components, and avar version 2 axis mapping. The standard describes installable binary fonts, not a replacement for a native editing source.
Save the imported project as VFC, VFJ, or VFJP to retain its supported component programs and axis mapping. Opening these structures does not provide an export route back to the new binary formats. Legacy export can reject unsupported large glyph counts, VARC programs, or avar version 2 mappings; keep the native project and inspect export diagnostics instead of assuming those structures will be preserved or silently simplified.
Metadata Formats
Within the metadata category, AFM carries metrics, including widths and kerning, without outlines. Their authoring workflows are Spacing Glyphs and Kerning Visually. Use File > Import > Metrics… or Export > Metrics… for the applicable exchange. Check the current master and whether spacing as well as kerning will be affected.
FEA carries the feature source taught in The Features Panel. Import or export it through the Features commands. It depends on the destination glyph set, classes, includes, and any generated data used during compilation; it is not a complete font backup.
Other focused exports, such as class files, can accompany a project. Record the source revision and master to which each belongs. A metrics file from one revision and feature code from another may each load successfully while describing an inconsistent font.
Per-format production behavior is covered in OpenType, Variable, and Web Fonts and Color Fonts; source exchange and legacy formats are covered in Interchange and Legacy Formats.