Integrating custom typefaces into your design workflow eliminates the guesswork from typography and brings editorial precision to digital projects. For Figma users, the ability to import fonts locally means headlines, body text, and captions can finally match the brand identity with exacting accuracy. This process, while straightforward, requires attention to file structure and platform permissions to ensure consistency across collaborators and devices.
Understanding Local Fonts in Figma
Figma handles type in two distinct ways: web fonts that stream from the internet and local fonts that rely on files installed on your machine. When you import fonts to Figma as local instances, the application references the font files already present in your operating system rather than fetching them from a remote server. Activating this feature is the critical first move that allows your unique type choices to appear inside the editor without requiring every team member to own a license.
Preparing Your System for Installation
Before you import fonts to Figma, you must ensure the typeface files are installed at the system level. On Windows, TrueType and OpenType fonts typically have .ttf or .otf extensions and are added through the Settings menu under Personalization > Fonts. macOS users can install fonts via the Font Book application, where double-clicking a file and selecting "Install Font" makes the family available globally. Skipping this step will result in Figma displaying a generic fallback font, which defeats the purpose of custom branding.
Font Licensing and Legal Considerations
Not every typeface is designed for local embedding, and misunderstanding the license can lead to copyright issues or forced project revisions. When you import fonts to Figma, check whether the license permits desktop installation and local file usage. Some foundries require web-specific hosting or limit the number of seats, so reviewing the terms before installation protects both your work and your client from potential legal exposure.
The Import Process Inside Figma
Once the files are installed on your computer, bringing them into Figma is remarkably direct. Open a text layer, click into the font family dropdown, and you should see your newly added typeface listed alongside the standard web-safe options. If the family does not appear, use the small plus icon in the dropdown menu and select "Install fonts" to refresh the catalog. This action syncs the editor with your system library, allowing you to apply the style immediately.
Managing Weights and Styles
Type families often include multiple weights, italics, and condensed or extended variants, and Figma requires each variation to be activated separately. When you import fonts to Figma, the application imports the entire family only if the necessary files are present on your system. To avoid missing styles, verify that every weight—such as Light, Regular, Bold, and Black—is installed on your computer. You can then toggle between these options directly within the Text section of the right-hand properties panel.
Collaboration and Shared Libraries
One of the nuanced aspects of local fonts is how they behave in shared files and team environments. If you import fonts to Figma from your personal machine and invite a collaborator, their editor will only render correctly if they also have the same typeface installed. To solve this, teams can rely on Figma's shared fonts feature or integrate a robust library that centralizes assets. Communicating these dependencies ensures that stakeholders see the intended typography during reviews and stakeholder presentations.
Troubleshooting Common Issues
Even after installation, users may encounter scenarios where the imported fonts appear correctly in some text layers but not others. This inconsistency often stems from browser caching for web fonts, conflicts between multiple type managers, or incomplete installation of a specific weight. Restarting the Figma desktop app or the browser extension usually resolves these glitches. Reinstalling the font files and verifying that the operating system recognizes the family in a separate test document can isolate the problem.
