Skip to main content

I saw another post Whyte font is missing from Slides template and it’s solved literally 15 hours ago. But the issue still exist in this design kit where this font family is used as a Text Display styling but not available to most users.

I assume it’s a similar problem to that post so I reported it as a bug. If this belongs somewhere else, I’m happy to submit this there.

Hey ​@_April — welcome to Figma Forum and thanks for catching this!

First, can you double-check that you’ve received the latest updates to your library? This article walks through how to do that: Start designing with UI kits → Receive updates.

If that doesn’t clear things up, please reply back with a bit more context to help me get clarity before I run this back to our product team:

  • the steps leading up to where you notice the missing font
  • any error messages you’re seeing
  • and a screenshot of where you expect the font to appear, but it’s not.

Really appreciate you taking the time to surface this. I’ll keep an eye out for your reply. 🙏🏻


Hi ​@Tom Reem , thanks for the additional details!

I’ve checked updates and there’s none so far. Also ever since I copied the community file, which is just several minutes before the time I posted this question, I don’t recall receiving any library update modal. Please correct me if there’s anything else I can do to retrieve latest updates.


It started from I copied the community file. And I noticed that there’s a font missing error in the file as attached. After I double check, this font family is only used in the Display text styling.

 

I’m not sure if this is by design that this font family is not available in the default font options in Figma. But as a user, I would strongly suggest to have it available to most users because it’s included in official UI3 library file, which suggests users can easily reuse all stylings and components without having to download them on their own.

 


I also had this issue and, sadly, had to replace the font everywhere.


Hi ​@_April and ​@Rae_Gibbs1 — thank you both for following up and for sharing these details. I’m sorry this issue is still lingering and that it’s added extra work with replacing fonts.

It looks like you’re doing everything correctly. We haven’t yet been able to pinpoint the root cause, so additional specific examples would be a big help. When you have a moment, could you please reach out to our Product Support team and include:

  • the link to this Forum thread for context
  • a link to a file where the issue occurs
  • and ensure support-share@figma.com has can edit access (this won’t affect billing).

This will help our team dig deeper and coordinate with the right folks on our side. Thanks again for your help and for flagging this so thoughtfully — we’ll keep an eye out for updates.