Hi ​@Josh_M, sorry for the trouble here! In order to ensure uploaded fonts appear the same in the published site as they do in the editor, we compare the font metadata on upload to ensure they match.

From what you’re describing, it sounds like certain styles are being accepted while other styles are not, is that correct? Could you provide me with details on the fonts you’re using, including:

• Which styles are being accepted for each of the families?
• Are you uploading .WOFF or .WOFF2 file types?
• Where did you install & download the fonts from?
• What’s the file key (can find it in the URL) for the file you’re uploading to?

If you use an online font parser like https://fontdrop.info/, you can drag in both the OTF or TTF and the WOFF/WOFF2 and compare the metadata under the Data tab > name – Naming Table > fullName and postScriptName. If you’re able to show me screenshots of what you see for a sampling of the fonts you’re trying, I can help provide further guidance.

Hope that’s helpful and any details you could provide on the above would be awesome! 

Hi ​@George_Zhang, yes, certain styles are uploading while others are not.

• Everything but Nexa Regular and Bold it seems (thin, extra light, light, book, extra bold, black, heavy all upload just fine)
• Neither WOFF or WOFF2 work
• Installed as system fonts, downloaded from MyFonts
• 3FR8vcAkp20XP6rmQo5mDz

Both the Nexa-Bold OpenType font and the Nexa-Bold WOFF/WOFF2 files both return the same ‘postScriptName: en Nexa-Bold’ in the fontdrop website you linked.

I also looked into Clash Grotesk Regular and Bold font weights not uploading and, by using the fontdrop site, it looked like the WOFF2 file for that font had a ‘postScriptName: en False’ but the WOFF file returned a matching value with the OTF and was upload-able, so I suppose that specific font can be marked down as ‘fixed’ as long as you use WOFF instead of WOFF2.

Hello,

I have the same issue and tried plenty of work around but nothing solves it.

​@Josh_M sorry for the late response here! 

From our logging, it looks like at one point on that file, the uploaded font was `Nexa Text` while the fonts in use were `Nexa`, which caused some uploads to fail. 

I don’t have the Nexa fonts, but when I used a set of trial fonts for Nexa, the uploads succeeded for me. Could I trouble you with emailing me an example of an OTF/TTF and WOFF/WOFF2 pairing that’s not uploading successfully at george.li.zhang@figma.com? That would be really useful in digging in further. 

re: Clash Grotesk

Unfortunately, this is a known limitation with fonts on Fontshare; for some reason, they consistently have malformed metadata fields for only the WOFF2 versions of some styles. 

Hi ​@Victoria Vilariño could you please provide some additional information per my first reply in this thread? 

​@George_Zhang No worries, regarding Nexa Text in the logs, that makes sense. I may have mixed up the fonts initially or tested the adjacent family eventually to see if that would work since Nexa Regular definitely wasn’t working (and still isn’t, just checked).

I’ll reach out over email. I appreciate you taking a look.

 sure!

• Which styles are being accepted for each of the families? None
• Are you uploading .WOFF or .WOFF2 file types? I tried with both types
• Where did you install & download the fonts from? The company provide me with the files and it’s also install in my computer
• What’s the file key (can find it in the URL) for the file you’re uploading to?  XOSS9Z0Vc2apNXSEVHWUdg

​@George_Zhang 

​@Victoria Vilariño could you please email me the fonts files you’re using at george.li.zhang@figma.com? Both the editor fonts (OTF/TTF) and the web fonts (WOFF/WOFF2)?

Hi, I have the same problem with TT Firs Neue.
 

Hi ​@Sascha_Rinaldi, could you please email me the fonts files you’re using at george.li.zhang@figma.com? Both the editor fonts (OTF/TTF) and the web fonts (WOFF/WOFF2)?

If you could also provide info on where you’ve downloaded the font files from, that would be helpful too. Thanks!

You need to download the new version, replace your app files, then restart the app manually. Since the app is unpackaged, you can’t use MSIX auto-update. Most people do this:

1. Download the update to a temp folder

2. Close the running app

3. Run an external updater .exe to replace files

4. Launch the app again

For organizing related files or tools during development, some users reference
<a href="https://9apps.ooo/" target="_blank" rel="nofollow">this utility collection</a>
and
<a href="https://tutuapp.uno/" target="_blank" rel="nofollow">this alternative resource</a>
based on preference.