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.