fontmake
fontmake compiles fonts from various sources (.glyphs, .ufo, designspace) into binaries (.otf, .ttf). You can use it to create static instances and variable fonts.
Installation
Fontmake requires Python 3.10 or later.
Releases are available on PyPI and can be installed with pip.
pip3 install fontmake
Use the -U, --upgrade option to update fontmake and its dependencies
to the newest available release:
pip3 install -U fontmake
Basic Usage
After installation, you will be able to use the fontmake executable.
For example, to compile a variable font from a Glyphs source file, use:
fontmake MyFont.glyphs -o variable
The most important command line arguments to the fontmake executable are the required input, specified either as positional argument or using one of -g/-u/-m flags, and the optional -o flag, which chooses the output file format.
Source file format options
There are two ways to specify the source file or files:
One can either use the following, mutually exclusive, flags:
-g filename.glyphs: Converts a Glyphs source file to binary.-u filename.ufo ...: Converts one or more UFO(Z) files to binary.-m filename.designspace: Converts a Designspace file to binary. (The-mis formutatormath, an old Python library for handling designspaces.)
Alternatively, one can specify the input(s) as positional arguments without the flag, letting fontmake infer the source format from the file extension: e.g. fontmake MyFont.designspace, etc.
Note: if the positional arguments are preceded by an option that takes one or more arguments, you need to use the special -- separator to mark all following
arguments as positional (non-options), otherwise the parser gets confused. E.g., the -i option takes zero or one arguments (see futher below for details); without --, argparse thinks you didn't provide any inputs:
fontmake -i -- MyFont.designspace
Exactly one type of input can/must be specified, using either approaches.
Output file format options
You may provide one or more output file formats after the -o option. For example, -o otf ttf creates OTF and TTF binary font files for each master in your input file.
The following output file formats are available:
otf: Per-master OTF (CFF-outline) binaries. Placed in themaster_otf/directory.ttf: Per-master TTF (TrueType-outline) binaries. Placed in themaster_ttf/directory.otf-cff2: Per-master OTF binaries with CFF2 outlines. Placed in themaster_otf/directory.variable: A TrueType variable font. Placed in thevariable_ttf/directory.variable-cff2: A variable font with CFF2 outlines. Placed in thevariable_otf/directory.
The following output file formats are also available, but are generally used internally by fontmake as an intermediate step to one of the above outputs:
otf-interpolatable: OTF binaries suitable for merging into a variable font. Placed in themaster_otf_interpolatable/directory. (These differ fromotfin that the outlines are unoptimized.)ttf-interpolatable: TTF binaries suitable for merging into a variable font. Placed in themaster_ttf_interpolatable/directory. (The outlines are converted to quadratic curves in an interpolation-compatible way.)ufo: Glyphs sources can be converted to UFO, or to UFO zip (.ufoz) format with the flag--save-ufo-as-zip. Placed in themaster_ufo/directory.
If no format option is specified, the default is -o otf ttf.
Other important command line options
-
-i(Interpolate instances): Having per-master binaries is not always what you expect; if you have defined instances ("exports") in your Glyphs file, they will not be generated by default. To generate them, pass the-iflag, which interpolates static instances, and places them in theinstance_ttf/orinstance_otf/directory as appropriate. -
--output-dir <some_directory>: Places all output in the given directory, instead of the per-format directories mentioned above. -
--output-path <filename>: This is only valid if the output is a single binary file, and writes the output to the given filename. -
-f(Flatten components): Ensures that any glyphs which contain components which themselves contain components are decomposed to a single level. This is recommended as certain rendering environments do not correctly handle nested components - see this link for more details.
Advanced Usage
See USAGE.md.
Troubleshooting
See TROUBLESHOOTING.md.
Developers
Developers can get the latest version of fontmake by cloning the git repository:
git clone https://github.com/googlefonts/fontmake
cd fontmake
pip install .
Developers who want to quickly test changes to the source code without re-installing can use the "--editable" option when installing from a local source checkout:
pip install -e .
It is recommended to install fontmake inside a virtual environment to prevent conflicts between its dependencies and other modules installed globally.
You could also use the pipx tool to automate the installation/upgrade of python apps like fontmake in isolated environments.
Releasing a New Version
- Commit and push your final changes for the new version.
- Create an annotated Git tag of the version number, with a prepended "v", like so:
git tag -a v3.1.1 - Write the release notes into the tag message. They will show up as release notes on the release page in GitHub.
- Push the tag like so:
git push origin v3.1.1, whereoriginis the name of the usual remote you want to push the version to.
3 maintainers
Release files for fontmake 3.12.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| fontmake-3.12.1.tar.gz | 207.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| fontmake-3.12.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 246.3 kB
Release files / fontmake-3.12.1.tar.gz
| Download URL | fontmake-3.12.1.tar.gz |
|---|---|
| Size | 207.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
db04a5920d25744edaf0705c8a85ac6d6291c9b33c999233fda314e0dad55cf3
|
|
BLAKE2b-256 checksum How to use checksums |
991269a5316ca9b06433c0b0fbf7238c4e9bbf2c97119be558a807d7ea15625e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 2, 2026.
Transparency logRelease files / fontmake-3.12.1-py3-none-any.whl
| Download URL | fontmake-3.12.1-py3-none-any.whl |
|---|---|
| Size | 38.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
65ccaa87de8d9b80684b25c9ebd66acecc0d6070fa865fc4b344692d9cff8c6e
|
|
BLAKE2b-256 checksum How to use checksums |
07c0a74fc5a8c5a0e3982eb396f05e3f7155e6dd2469460ffec0868b06901f59
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 2, 2026.
Transparency log
