Hi, we have been having issues with font names changing for our brands but having spoken to our team no one has been changing them.
We need help understanding how is this happening as this causes issues with our Token Studios and tokens. They start to break the dev side.
This is a headache when you're dealing with Token Studios. Honestly, it’s almost never about someone manually changing names—it’s usually just the font metadata acting up behind the scenes. If your team hasn’t touched anything, the system is likely pulling different naming strings from different local machines.
A few things are probably causing this:
The biggest culprit is usually the PostScript vs. Family Name mismatch. Most design tools like Figma love the 'Family Name,' but dev environments and Token Studios are picky and look for the 'PostScript Name.' If even one person on the team has a version where these don't line up, the token link just breaks. Also, keep an eye on file formats—even a tiny version difference between an OTF and a TTF file can change the internal ID and mess things up.
Here’s how we usually handle this:
Pick one source: Make sure everyone (and I mean everyone) is using the exact same font file version. No mix-and-match.
Stick to numbers: Instead of using 'Bold' or 'Black', try using numerical weights like 700 or 800. It helps avoid those annoying naming conflicts between OS levels.
Double-check your CSS strings: Standardizing the font-family string in your CSS will save you so much debugging time.
I’ve been using a tool called fontchangerpro lately to grab the exact CSS code and font names, but you can find plenty of other CSS verification tools online. It’s a good way to double-check that your token names actually match what the browser is expecting. It really just comes down to keeping those strings consistent across the whole workflow.
Hopefully, that helps you track down where the mismatch is happening!
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.