Features / Automation and extensions
Plugin support
Extending the editor with add-ons written by others. The note says whether the editor also finds, installs and updates them.
How it works
A plugin is code that the editor loads to add something it does not do itself, such as a drawing tool, a panel, a filter that changes glyphs, a report, or another file format. Plugins are written by others against an interface the editor documents: which parts of the font a plugin can read and change, and where it can hook into menus, tools and windows.
Because plugins are distributed separately, the editor needs a way to find them, such as a plugin folder, a naming scheme, or a plugin manager that also installs and updates them. A plugin may also need to keep data of its own in the font. The UFO format sets aside its lib file for such data and asks for keys in reverse domain notation, such as com.example.myplugin, so tools do not overwrite each other’s data.
Why it matters
Plugins let others add features the editor’s developer has not built, such as support for a particular writing system or a step in a studio’s own workflow.
What to check
- Whether the plugin interface is documented, and how much it reaches; a few extension points only is the Partial level below.
- Whether the editor finds, installs and updates plugins for you (the notes below say which).
- Whether data that plugins store survives a round trip through UFO 2 and 3.
- Whether plugins use the editor’s Scripting language, and keep working after updates.
Read more
- Creating and discovering plugins, Python Packaging User Guide
- UFO 3 lib.plist, Unified Font Object
Editors
- Full
- A documented plugin interface that reaches the font's data and lets add-ons bring their own tools, panels or commands.
- Partial
- Add-ons of only a few fixed kinds, such as extra views or file formats.
| Editor | Support | Evidence |
|---|---|---|
| FontForge | Full | Python package plugins installed with pip; Configure Plugins enables them but does not install them.Checked 2026-10-25 · developer documentationSource |
| FontLab | Full | Third-party Python extensions such as TypeRig add panels and tools; Install Scripts only opens extension resources.Checked 2026-11-10 · developer documentationSource |
| Glyphs | Full (not in Glyphs Mini) | Python and Objective-C SDK; the built-in Plugin Manager installs and updates plug-ins.Checked 2026-10-25 · developer documentationSourceGlyphs Mini: Not supportedHandbook lists plug-ins among features Mini lacks.Checked 2026-10-25 · developer documentationSource |
| RoboFont | Full | Open, documented Python extension format; the Mechanic 2 extension installs and updates extensions.Checked 2026-10-25 · developer documentationSource |
| Fontra | Partial | Python plug-in APIs for views and storage backends; plugins are added by GitHub path, with no catalogue.Checked 2026-10-25 · developer documentationSource |
| BirdFont | Not supported | Checked 2026-11-02 · stated by the developer |
| FontCreator | Not supported | Checked 2026-10-25 · stated by the developer |
| Fontself Maker | Not supported | Checked 2026-11-02 · stated by the developer |
| FontStruct | Not supported | Editor code has no plugin or add-on system.Checked 2026-10-29 · developer documentationSource |
| Glyphr Studio | Not supported | Code: no plugin or add-on mechanism; the page loads only the app's own modules.Checked 2026-10-30 · 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 |