Methodology
Who runs this site
fonteditors.com is made by High-Logic, the developer of FontCreator. High-Logic also makes the font manager MainType and the handwriting font tool Scanahand; neither is a font editor, so FontCreator is the only High-Logic product compared. Every editor, FontCreator included, is held to the same evidence rules and scored with the same formula below.
Why this site exists
We make font editors, and we kept running into wrong or outdated information about them, our own included: "best font editor" lists that rank programs nobody maintains any more, quote prices from years ago, get the platforms wrong and cite no sources. So we built the comparison we wanted to point people to. Every value shows where it comes from and when it was checked, and anyone, including the developers of the other editors, can send a correction.
How we made this site
We used AI to help build this site and to collect the data from developers' websites, documentation and release notes. That is why every value shows where it comes from, with a link to the page or a label saying the developer stated it, and when it was checked. So far, every value comes from the developer's documentation or a statement by the developer; none has been tested in the editor itself. If you find a value that is wrong or outdated, please send a correction.
Which tools are included
The site covers font editors: tools for drawing and editing fonts as vector outlines. Handwriting font services, font managers, stock-font and font-hosting services, and bitmap (pixel) font editors are not included. Production and specialist tools, which do one part of the work next to a font editor, such as editing finished fonts, OpenType layout or hinting, are listed under Other font tools.
A font editor is compared when it exports OpenType fonts (TTF or OTF), can be bought, downloaded or used online, has been publicly available for at least two years, has had a release or update in the last two years, and is documented well enough to verify its features. Two years count from its first public release; ready-made builds anyone could download count, numbered or not. A feature list says what an editor can do, not how stable it is or whether it will still be developed, so a new editor first needs a track record. Editors that meet these conditions are added once their features are researched; newer editors, and editors in alpha or beta, are followed until they qualify. Other font tools lists the editors we follow, older and discontinued editors, and the tools this site does not compare.
How the chooser scores an editor
Every editor stays in the list. Platform, price and must-haves are requirements: an editor that does not run on every platform you select, does not fit the price you choose or does not support a must-have is listed under "Doesn't meet your requirements", with the reason. Features grouped as "At least one of these is required" count as one requirement: the editor needs at least one of them. With the condition "No required host application", an editor that only runs inside another app, such as Fontself Maker inside Adobe Illustrator or Photoshop, is a mismatch too, with that reason. The price is checked per edition: a product fits when one of its editions meets every requirement within that price, and the result names that edition. "Free" keeps free and open-source editions, "Open source" only editions under an open-source licence; a maximum price is compared with one payment, or with one year of a subscription, before VAT when the developer lists prices with and without it; euro prices are converted at the European Central Bank reference rate of 29 October 2026, 1 euro = US$1.113. Choosing "Also edit existing" under Fonts makes round-trip editing of existing fonts a must-have. A browser-based editor counts as running on Windows, macOS and Linux. The number on each filter option is how many editors meet all your requirements if you pick it, with the rest of your selection as it is; editors with a requirement not verified yet are not counted. It counts only the compared editors, not the tools under Other font tools.
Every editor gets a score between 0 and 100%: the weighted share of the features you selected that it supports. A must-have weighs 3 and a nice-to-have 1. Each "at least one of" group counts as one must-have, at the level of its best-supported feature, so an editor gains nothing from supporting more of them.
The score measures how many of your selected features an editor's documentation covers, and how fully. It does not measure how easy an editor is to learn, how well it works or whether it suits you, so the results do not show it as a percentage: it only sets the order within each group of results. Comparing side by side shows it, as the coverage of your selected features. We are reworking the goals, so that each one asks for what that task needs rather than for a long list of features.
The conditions under the filters are off unless you switch them on, and change no weight or level. "Without plugins" counts support through a plugin as not supported, only for the features you selected; an editor is not left out because it can use plugins, and built-in support counts as before. "No required host application" leaves out editors that cannot run without another application; optional tools that an editor can use do not count.
In the feature panel, a click on a feature selects it as a nice-to-have, and a second click deselects it. Under Your features each selected feature can be made a must-have or removed, and two or more can be grouped as "At least one of these is required". A group left with one feature makes that feature a must-have, with a notice.
| Support level | Counts as |
|---|---|
| Full: built in and meets the feature's Full criterion | 1 |
| Plugin: through an official or widely used plugin | 0.75 |
| Partial: the main job works, with stated limits | 0.5 |
| External tool: the editor runs a separately installed tool | 0.25 |
| Not supported | 0 |
- Only editors that meet every requirement are ranked. The others are listed below them, sorted by how many requirements they miss and then by score, each with the reason.
- With requirements selected, the ranked editors are in two groups: first those that meet every requirement fully, then, under "Meets your requirements, with limitations", those that meet one only with Partial support or through an external tool, labelled "Limited match" with the feature and the evidence for its level. Within each group the order is the score, and the numbers follow the order shown. Editors with a requirement that is not verified yet, and those that do not meet the requirements, follow under their own headings.
- An editor with a must-have that is not verified yet is listed apart, under "A requirement is not verified yet": unknown is not the same as not supported. The same goes for an "at least one of" group when none of its features is verified as supported and some are not verified yet.
- When a selected feature is not verified for an editor, its score is shown as a range, for example "63–88%": the low end counts that feature as not supported, the high end as full support. The ranking uses the low end.
- Each result shows how many of the 81 features have evidence for that editor: a cited source, or a statement by the developer. That evidence can show a feature as supported or as not supported, so the number says how much is known about an editor, not how much it supports. The rest are "Not verified": unknown, never counted as a no in the requirements. A value checked against a source is a check of the documentation, not a test of the editor.
- Editions of the same product, such as FontCreator Essentials and Professional or Glyphs Mini and Glyphs, are one entry, so no product appears twice. Editions are scored separately, and where support differs, each edition has its own level. A product is ranked by its best-scoring edition that has every must-have; when a cheaper edition also has every must-have, the result names it.
- Some support differs per script, such as automatic kerning for Latin only. Such a value is shown with the scripts it covers and, as with editions, counts at the level of the scripts the editor supports best. A value without such a limit counts for every script; a limit is recorded only when a source states it. When you pick scripts, each editor is scored at its level for those scripts; with several scripts, at the level of the weakest.
- Comparing from the chooser shows the features you selected, grouped as must-haves, each "at least one of" group and nice-to-haves, with the same match score; a value lower than the best of the editors compared is shaded. Below them come the key capabilities of every category, with the other features one click away.
- Equal scores are shown as a tie ("=2"). Within a tie, and in every list that is not ranked, editors are in alphabetical order.
- No editor gets a boost, and there are no hidden weights.
Key capabilities
24 of the 81 features are key capabilities, the ones that most often help choose an editor, together with Color font formats, one choice for the five color formats. The chooser, the side-by-side tables and each profile show them first; the other features are advanced, one click away per category or all at once. Picking Color font formats in the chooser makes the five formats one "at least one of" group, and each format can still be picked on its own. This changes only what is shown first. Every feature counts in the score in the same way, a feature you select always stays in view, and a row that is not shown is never left out of a score or a comparison.
| Category | Key capabilities |
|---|---|
| Font files | TrueType (TTF), OpenType CFF (OTF), Round-trip editing of existing fonts and Keeps existing layout when editing a font |
| Source files and collaboration | UFO 2 and 3 |
| Font information and character sets | Font info and line metrics |
| Drawing | Cubic curves, Layers and background and Boolean operations |
| Components | Components |
| Artwork and tracing | Vector artwork import and Bitmap-to-vector tracing |
| Spacing and kerning | Class kerning and Automatic kerning |
| OpenType layout | Visual feature and lookup editor and Mark positioning from anchors |
| Variable fonts | Variable TrueType, Masters and axes and Interpolation checks and fixes |
| Color fonts | Color font formats (COLRv0, COLRv1, OpenType-SVG, sbix and CBDT) |
| Proofing and QA | Text and waterfall proofs and Font-wide validation |
| Automation and extensions | Scripting language, Plugin support and Batch actions without code |
Hinting has no key capability: a goal or a selection shows its features.
Goals
A goal is a shortcut that selects a fixed set of features. It changes nothing in the scoring, and the selection can be adjusted afterwards. Since 17 November 2026 each goal asks only for what its task needs: My first font needs one way to make glyphs and one font format to export, and no longer selects professional features such as automatic kerning. Where a task has real alternatives, the goal asks a follow-up question; an answer that names a feature of the goal's "at least one of" group takes that group's place.
| Goal | Must have | Nice to have |
|---|---|---|
| My first font | One of Cubic curves, Quadratic curves, Bitmap and pixel fonts, Vector artwork import or Bitmap-to-vector tracing; one of TrueType (TTF) or OpenType CFF (OTF) | Text and waterfall proofs, Glyph sets and encodings |
| A professional family | OpenType CFF (OTF), TrueType (TTF), Class kerning | WOFF2, Components, Metrics keys, Kerning exceptions, FEA editing and compiling, Mark positioning from anchors, PostScript hinting, Automatic TrueType hinting, Font-wide validation, OpenType feature proofing, Batch export, Glyph sets and encodings |
| Editing an existing font | Round-trip editing of existing fonts | Keeps existing layout when editing a font, TrueType (TTF), OpenType CFF (OTF) |
| A variable font | Masters and axes, Variable TrueType | Interpolation checks and fixes, Named instances, WOFF2 |
| A color font | One of COLRv0, COLRv1, OpenType-SVG, sbix or CBDT | Layers and background |
| From drawings or artwork | One of Bitmap-to-vector tracing or Vector artwork import; one of TrueType (TTF) or OpenType CFF (OTF) | Reference images, Automatic outline fixes, Text and waterfall proofs |
After A professional family, the chooser asks "How will you make the styles?" Until it is answered, the goal gives its own results. "Static styles" adds nothing, so editors with masters still count. "Interpolated from masters" adds Masters and axes as a must-have and Named instances as a nice-to-have.
After Editing an existing font, the chooser asks "What must survive the edit?" Until it is answered, the goal gives its own results. "Outlines and metrics" adds nothing, so round-trip editing stays the only requirement. "Also the OpenType layout" adds Keeps existing layout when editing a font as a must-have.
After A color font, the chooser asks "Which color format?" Until it is answered, the goal gives its own results. "COLRv0 (layers)" adds COLRv0 as a must-have. "COLRv1 (gradients)" adds COLRv1 as a must-have. "OpenType-SVG" adds OpenType-SVG as a must-have. "Bitmap (sbix or CBDT)" adds one of sbix or CBDT as a requirement.
After From drawings or artwork, the chooser asks "What is your artwork?" Until it is answered, the goal gives its own results. "Vector files, such as SVG or Illustrator" adds Vector artwork import as a must-have. "Scans or photos" adds one of Bitmap-to-vector tracing or Reference images as a requirement.
Scripts
Picking a script selects the features it needs, on top of a goal, and scores each editor for that script. Latin, Greek and Cyrillic need no extra features. Support for the other scripts is judged from each developer's documentation of the features listed below, not by testing fonts in each editor, so a match means those features are documented, not that every shaping case of the script has been tried.
| Script | Must have | Nice to have |
|---|---|---|
| Arabic | Complex scripts (Arabic, Hebrew, Indic, CJK) | Mark positioning from anchors, FEA editing and compiling, Visual feature and lookup editor, OpenType feature proofing, Auto-generated features, Components, Glyph sets and encodings |
| Hebrew | – | Complex scripts (Arabic, Hebrew, Indic, CJK), Mark positioning from anchors, FEA editing and compiling, Visual feature and lookup editor, OpenType feature proofing, Components, Glyph sets and encodings |
| Indic | Complex scripts (Arabic, Hebrew, Indic, CJK) | Mark positioning from anchors, FEA editing and compiling, Visual feature and lookup editor, OpenType feature proofing, Auto-generated features, Components, Glyph sets and encodings |
| Chinese, Japanese or Korean | – | CID-keyed fonts, Vertical layout, Complex scripts (Arabic, Hebrew, Indic, CJK), Components, Smart or parametric components, Glyph sets and encodings, OpenType CFF (OTF), FEA editing and compiling, TrueType Collections (TTC) |
What counts as support
- Every feature has a definition, with what counts as Full and as Partial, on its own page.
- Partial means the main job works, with stated limits. If the main job cannot be done, the feature is Not supported, and the note says what does work.
- For font formats such as TTF, OTF, WOFF and TTC, exporting is the main job. For source formats such as UFO and .glyphs, opening and saving both count; one direction is Partial.
- External tool means the editor runs or connects to a separately installed tool. A tool that the documentation only recommends using separately does not count.
- Plugin and External tool count only when the plugin or tool meets the Full criterion. When it only meets the Partial criterion, the value is Partial, and the note names the plugin or tool.
Editor profiles
- Every description follows one template: what the editor is, who makes it and where, what the developer says it is built around, and its editions. It is paraphrased from the developer's own material, with a source, and uses no words that praise or criticise, for FontCreator too.
- "What this editor stands out for" lists up to 3 workflows, from one fixed list that is the same for every editor (below). An editor has a workflow when it supports, fully or through a plugin, every feature the workflow needs and at least one of its alternatives, and at least two of the workflow's features in all; support through a plugin is marked as such. One strong feature is not enough for a whole workflow.
- A workflow is listed only when at least one other editor of the same kind is verified as not having it, and at least 3 of them have a verified status: a workflow that every compared editor has is not a strength. Not verified never counts against another editor.
- Workflows are ordered by practical value: how much the goals rely on their features (per goal, 2 when one of them is a must-have, 1 when one is a nice-to-have). Then comes the quality of the evidence: the share of the values documented by a source rather than only stated by the developer. How rare a workflow is only breaks a remaining tie, and the number of features in a workflow gives no advantage. An editor can show fewer than 3 workflows, or none.
- The workflows:
- Editing existing fonts: Round-trip editing of existing fonts and Keeps existing layout when editing a font (practical value 2).
- Drawing and construction: Cubic curves, Layers and background and Components (practical value 4).
- Spacing and kerning: Class kerning and one of Automatic kerning or Automatic spacing (practical value 2).
- OpenType development: Visual feature and lookup editor, FEA editing and compiling and Mark positioning from anchors (practical value 1).
- Variable font production: Masters and axes, Interpolation checks and fixes and one of Variable TrueType or Variable OpenType (CFF2) (practical value 2).
- Color font creation: at least two of COLRv0, COLRv1, OpenType-SVG, sbix or CBDT (practical value 2).
- Automation and extensibility: Scripting language, Plugin support and one of Batch export or Batch actions without code (practical value 1).
- Font testing and QA: Text and waterfall proofs, Outline proofing and Font-wide validation (practical value 3).
- Artwork to font: Vector artwork import and Bitmap-to-vector tracing (practical value 4).
- "Specialist capabilities" lists up to 3 features for a smaller audience: CID-keyed fonts, VOLT editing and compiling, Vertical layout, Feature variations, Axis mapping (avar), Variable font subsetting, COLRv1, TrueType manual hinting, Variable font hinting and Command line and headless use. They count under the same conditions as workflows (supported fully or through a plugin, and verified as missing in at least one other editor of the same kind) and are ordered the same way. A feature already listed under a workflow is not repeated, and the line is left out when no feature qualifies.
- "Doesn't have" lists features verified as not supported while more than two thirds of the other editors of the same kind with a verified value have them, built in or through a plugin. A feature is compared only when at least 3 of them have a verified value.
- All these lists are worked out from the data and change when the data does. An editor's own source format, such as .glyphs for Glyphs, is left out, for that editor and as a value of the others: opening its own files is not something an editor stands out for.
- On a head-to-head page, "Better supported in" lists the features where one editor's support level is higher than the other's, in their most capable editions, such as full against partial, or partial against not supported, key capabilities first. A feature is compared only when both editors have a verified value; an editor's own source format does not count for that editor.
- An "Alternatives to" page takes the features an editor supports, fully, through a plugin or in part, in its most capable edition, and lists every other editor with how many of those features it supports too, highest first; when some of those features are not verified yet for an editor, the number is shown as a range and the order uses the lower end.
- Editors are compared within their kind: professional editors with each other, and hobbyist, web and plugin editors with each other. A hobbyist editor that lacks variable fonts says nothing about a professional editor that has them.
- The profile of an editor with editions, such as FontCreator Essentials and Professional, lists under Editions the features in which the editions differ, side by side with each edition's price; the evidence for each value is under All capabilities. A feature that is not verified for any edition counts as the same in each.
- Release activity counts the releases in the developer's release notes in the last 12 months, bug-fix builds included.
Where the data comes from
- Every value links to its source, or is labelled as stated by the developer, and shows the date it was checked. "Checked" means the value was compared with its source on that date; "Tested" is used only for values tried in the editor itself; so far no value has been tested that way.
- The developer's own documentation comes first. When the developer's sources disagree, the newest one that covers the feature counts, and the note says so. Third-party sources are used only when the developer's material says nothing.
- A value without proof stays "not verified". A feature is marked "not supported" only when a source says so explicitly, when the developer's own complete list (such as its list of export formats) leaves it out, when the developer states it, or when the developer's documentation covers the editor in depth and does not mention it; the note then names the documentation that was read.
- Values stated by a developer are labelled as such.
Corrections and proposals
- A correction needs evidence and is judged by the rules above, whoever sends it, the editor's developer included. When the documentation is out of date, a newer source from the developer, such as release notes, the repository or an answer on the developer's forum, takes its place. When there is no such source, we try it in the editor itself; the value then says "Tested", with the version tried.
- A proposal to change a feature, its criteria or a goal is a change to the rules. It is made only when it applies to every editor alike and reflects what someone with that goal needs. Each such change is listed under Data updates; when an editor's developer proposed it, the entry says so.
Data
Download the full dataset (JSON), with every source and verification date.