Features / Source files and collaboration
Git-friendly source format
A text-based source format that version control such as Git can compare and merge line by line.
How it works
Version control systems such as Git record changes to a set of files, so you can compare versions and go back to an earlier state. Git merges text files line by line: changes to different lines are combined, and changes to the same lines are marked as a conflict. Git does not merge binary files; when two people change one, the conflict has to be sorted out by hand.
A git-friendly source format stores the font as text, preferably in many small files. UFO 2 and 3, for example, is a folder of mostly XML files, with one .glif file per glyph and layer, so editing a glyph changes a few lines in one file. The UFO specification also recommends writing property-list keys in sorted order, to suit version control.
Why it matters
With a text source, every change can be reviewed and undone, and work done in parallel can be merged. Text alone is not enough: the Git documentation notes that some text files are really small databases, which cannot be merged and whose differences are not helpful.
What to check
- Whether the editor’s native format is text, or you need an exchange format such as UFO for version control.
- Whether the source is split into many small files or kept as one large file (the Partial level below).
- Whether saving writes data in a stable order, so a small edit gives a small difference.
- Whether the files that tie a family together, such as a Designspace file, are text as well.
Read more
- UFO 3 directory structure, Unified Font Object
- UFO 3 conventions: XML property lists, Unified Font Object
- Git attributes: binary files, Git
Editors
- Full
- The editor's own source format is text-based and suited to version control, or the editor saves a text format that keeps all of its own data.
- Partial
- Text only through an exchange format that drops data the editor's own format keeps, or a text format that is hard to compare or merge, such as one long line.
| Editor | Support | Evidence |
|---|---|---|
| BirdFont | Full | Fonts are saved as XML text files, which scripts can also edit.Checked 2026-11-10 · developer documentationSource |
| FontForge | Full | ASCII SFD with meaningful diffs; .sfdir format stores one file per glyph.Checked 2026-10-25 · developer documentationSource |
| FontLab | Full | Its own VFJ format is JSON text, which FontLab suggests for version control.Checked 2026-11-10 · developer documentationSource |
| Fontra | Full | .fontra is a folder of JSON, CSV and text, one file per glyph.Checked 2026-10-25 · developer documentationSource |
| Glyphr Studio | Full | Its own .gs2 project is JSON text; a setting formats it for reading instead of compact size.Checked 2026-11-10 · developer documentationSource |
| Glyphs | Full | Plain-text .glyphs; .glyphspackage keeps one file per glyph.Checked 2026-10-25 · developer documentationSource |
| RoboFont | Full | Native UFO format is a folder of small XML files.Checked 2026-10-25 · developer documentationSource |
| FontCreator | Partial | Saves UFO 3, which the manual says does not cover all font data; it recommends font projects.Checked 2026-11-10 · developer documentationSource |
| Fontself Maker | Not supported | Work is saved directly as OTF font files; no separate source format.Checked 2026-10-26 · developer documentationSource |
| FontStruct | Not supported | Designs are saved on the FontStruct server, not as local source files.Checked 2026-10-26 · developer documentationSource |
Not verified yet: iFontMaker.