Features / OpenType layout

FEA editing and compiling

Writing OpenType features in Adobe's feature file syntax (FEA) and compiling them into the font.

How it works

OpenType layout features, such as ligatures, contextual alternates, kerning and mark positioning, are stored as lookups in the GSUB and GPOS tables. A feature file (FEA) describes them as text, in a syntax defined by Adobe. For example, feature liga { sub f i by f_i; } liga; tells the font to replace f followed by i with an fi ligature wherever standard ligatures are on.

A compiler turns the text into lookups. Adobe’s makeotf, part of the AFDKO, is the compiler the specification’s implementation notes describe; fontTools’ feaLib is an open-source Python compiler for the same syntax. Editors either include a compiler or call one. Many also write part of the code for you and add your own code to it: kerning from your kerning data, mark attachment from your anchors (see Mark positioning from anchors), or features such as ligatures from glyph names (see Auto-generated features).

Why it matters

FEA is plain text, so the same code can move between editors and build tools; UFO keeps it in a file called features.fea. Code can also express rules that a visual editor may not offer (see Visual feature and lookup editor).

What to check

  • Whether compile errors point to a line and say what is wrong.
  • How the editor combines the code it generates with yours, and whether you can see the combined result.
  • Whether the code survives a round trip through UFO files (see UFO 2 and 3).
  • Whether you can test the features before exporting (see OpenType feature proofing).

Read more

Editors

Full
Edits and compiles FEA code inside the editor.
Partial
FEA with stated limits, such as import only or part of the syntax.
EditorSupportEvidence
FontCreatorFullCode editor compiles AFDKO FEA, including the variable-value additions.Checked 2026-10-25 · developer documentationSource
FontLabFullFeatures panel edits and compiles FEA code, with diagnostics in the Output panel.Checked 2026-11-10 · developer documentationSource
FontraFullCode editor, compiled on the fly with live error reporting.Checked 2026-10-25 · developer documentationSource
GlyphsFull (not in Glyphs Mini)AFDKO syntax with Glyphs extensions, edited and compiled in Font Info.Checked 2026-10-25 · developer documentationSourceGlyphs Mini: Not supportedHandbook: custom feature code is not available in Mini.Checked 2026-10-25 · developer documentationSource
RoboFontFullCode editor for AFDKO feature syntax, with linked .fea files.Checked 2026-10-25 · developer documentationSource
FontForgePartialImports .fea into lookups and exports .fea; editing happens in lookup dialogs.Checked 2026-10-25 · developer documentationSource
BirdFontNot supportedChecked 2026-11-02 · stated by the developer
Fontself MakerNot supportedFeatures limited to aalt, liga, dlig and kerning, all set through the panel.Checked 2026-10-26 · developer documentationSource
FontStructNot supportedFAQ: OpenType features are beyond the FontStructor; export to Glyphs instead.Checked 2026-10-26 · developer documentationSource
Glyphr StudioNot supportedDocs list OpenType features as unsupported beyond ligatures and kerning.Checked 2026-10-25 · developer documentationSource
iFontMakerNot supportedNot in iFontMaker's FAQ, App Store text or websites (read 12 Nov 2026).Checked 2026-11-12 · developer documentationSource

Report incorrect information