Features / Spacing and kerning
Metrics keys
Linking a glyph's sidebearings or width to another glyph, for example m following n, so spacing changes carry through.
How it works
Every glyph has an advance width, the distance from where it starts to where the next glyph begins, and two sidebearings: the space between the outline and each end of that width. Many glyphs should share a sidebearing or width with another. An fi ligature, for example, should take its left sidebearing from f and its right one from i. A metrics key records such a link, so when you respace the source glyph, every linked glyph follows.
The font stores only the resulting numbers: the hmtx table holds each glyph’s advance width and left sidebearing, and the right sidebearing follows from those and the outline. TrueType composite glyphs have a related flag that gives a composite the metrics of one component, such as an accented i taking those of its dotless i.
Why it matters
Even spacing depends on consistent sidebearings. Microsoft’s character design standards call n and o the model characters most type designers use to space the rest of the lowercase, and H and O for the capitals. Links keep the glyphs that follow these models consistent while spacing changes.
What to check
- Whether links stay live and update when the source glyph changes, or copy the value once (the Partial level below).
- Whether each sidebearing and the width can be linked to a different glyph.
- Whether links work separately in each master (see Masters and axes).
- How links combine with Automatic spacing and Components.
Read more
- hmtx, the horizontal metrics table, Microsoft
- Character design standards: lowercase spacing rules, Microsoft
- glyf composite glyph flags, Microsoft
Editors
- Full
- Linked metrics that update when the source glyph changes.
- Partial
- Metrics taken from another glyph once, without a live link.
| Editor | Support | Evidence |
|---|---|---|
| BirdFont | Full | Spacing classes automatically carry lsb, rsb and kerning to linked glyphs.Checked 2026-10-26 · developer documentationSource |
| FontCreator | Full | Metric expressions, such as a glyph name or lsb() and aw() functions.Checked 2026-10-25 · developer documentationSource |
| FontLab | Full | Metrics expressions link LSB, RSB or width to other glyphs; Live Metrics updates them.Checked 2026-11-10 · developer documentationSource |
| Glyphs | Full | Persistent links; out-of-sync keys are flagged and updated with one command.Checked 2026-10-25 · developer documentationSource |
| FontForge | Partial | Copy LBearing, RBearing or Width from one glyph and paste onto others.Checked 2026-10-25 · developer documentationSource |
| Fontra | Partial | Glyph names and expressions in metric fields are evaluated once, not linked.Checked 2026-10-25 · developer documentationSource |
| RoboFont | Partial | Expressions like =n are converted to fixed numbers, not live links.Checked 2026-10-25 · developer documentationSource |
| Fontself Maker | Not supported | Checked 2026-11-02 · stated by the developer |
| FontStruct | Not supported | Widths are automatic, per letter, global or monospaced; none link to other glyphs.Checked 2026-10-29 · developer documentationSource |
| Glyphr Studio | Not supported | Code: glyphs store a plain advance width; no metric links to other glyphs.Checked 2026-10-29 · developer documentationSource |
| iFontMaker | Not supported | Not in iFontMaker's FAQ, App Store text or websites (read 12 Nov 2026).Checked 2026-11-12 · developer documentationSource |