Features / Components
Corner and cap components
Reusable corner and cap shapes, such as serifs, ink traps and stroke endings, attached to points of an outline and merged into it at export.
How it works
Corner and cap components are small shapes that you draw once, each as its own glyph, and attach to points of an outline. A corner component adds a detail at a corner, such as a serif, the small line at the end of a stroke, or an ink trap, a notch where strokes meet that is meant to trap ink. A cap component shapes the end of a stroke, its terminal. Each shape stays linked to its source glyph, so editing the source changes every glyph that uses it.
When the font is exported, the shapes are merged into the outline they are attached to. Unlike ordinary Components, they cannot stay separate in the font, because an OpenType composite glyph can only add whole glyphs at a position, with a scale or other transformation.
Why it matters
Details such as serifs and ink traps repeat across many glyphs. Drawing each once keeps them consistent, and the outlines you edit stay free of them until export.
What to check
- Whether it has both corner and cap shapes, or only one of the two kinds (the Partial level below).
- Whether the shapes stay linked to their source glyph, or are copied in and must be updated by hand.
- Whether a shape can be adjusted for each use, for example scaled or mirrored.
- Whether the merged outlines stay compatible across masters, with the same points in each (see Masters and axes).
Read more
- Ink trap, Google Fonts Knowledge
- Terminal, Google Fonts Knowledge
- glyf composite glyph description, Microsoft
Editors
- Full
- Corner and cap shapes stay linked to their source glyph and update everywhere when it is edited.
- Partial
- Only one of the two kinds, or shapes that are copied in rather than linked.
| Editor | Support | Evidence |
|---|---|---|
| FontCreator | Full | Path Decorations: corner and cap donors update every use; decomposed at export.Checked 2026-10-26 · developer documentationSource |
| FontLab | Full | Skin filter applies _corner and _cap source glyphs; editing the source updates every use.Checked 2026-11-10 · developer documentationSource |
| Glyphs | Full | Corner and cap components stay in sync with their _corner and _cap glyphs.Checked 2026-10-26 · developer documentationSource |
| BirdFont | Not supported | Checked 2026-11-02 · stated by the developer |
| FontForge | Not supported | Code: layers hold only contours, images, guides and plain references; no corner or cap data.Checked 2026-11-01 · developer documentationSource |
| Fontra | Not supported | Docs: corner and cap components have no equivalent yet.Checked 2026-10-30 · developer documentationSource |
| Fontself Maker | Not supported | Checked 2026-11-02 · stated by the developer |
| FontStruct | Not supported | No outline points to attach shapes to; tools only place predefined bricks.Checked 2026-10-29 · developer documentationSource |
| Glyphr Studio | Not supported | Instance transforms listed are offset, size, flip and rotation; no attachment to points.Checked 2026-10-26 · 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 |
| RoboFont | Not supported | Not in RoboFont's documentation; no extension in Mechanic 2 or the Extension Store does it.Checked 2026-11-12 · developer documentationSource |