lucid.page Installing a Hobby Font Without Losing Track of What You Just Built
Text size
Read time2 min

# Installing a Hobby Font Without Losing Track of What You Just Built

The moment after a TTF downloads is oddly easy to fumble. The file is on disk, the system font list is already crowded, and it is not always obvious whether the menu is showing the new build or an older file with a similar name.

Contents

I work on the MakeFont team. These are the install checks we suggest for a personal or prototype font, especially one drafted in a browser and downloaded as a TTF.

# Keep the builds in a dated folder

Save each successful TTF with a version or date in the filename, in a folder you control, before you install it. If you later repair a glyph and export again, you will know which file is current. Do not rely on a browser downloads list as the archive.

# Install, then type outside the generator

Install the font on your system, or in a design app that can load a local file, and type a short sentence, a line of numbers, and the punctuation you actually use. The preview inside a font tool is useful, but it is not the same as the font menu in the place you will set type.

If a character is missing, many apps silently fall back to another face. Look closely at letters that suddenly feel off-style.

# Watch for family-name collisions

If the family name matches a font already on the machine, the new file may fail to appear, or it may overwrite the wrong style in the menu. Rename the family in the source and rebuild if that happens. Uninstall the older build rather than leaving two nearly identical files fighting for the same name.

# Uninstall the previous file when you iterate

A repaired outline is not in the installed font until you replace the file and reopen the document. Cached previews are common. After each rebuild, confirm the file date and type the same test sentence again.

MakeFont lets you generate and edit a font in the browser, then download a TTF once the required glyphs are in place. The install step is still yours: keep versions, test in a real text field, and do not trust a successful build until you have typed with it. The product is at MakeFont.

Written by the MakeFont team. More about the tool is at makefont.app.

End