Same problem 
1 Like
+++++ Same problem 
2 Likes
I guess the issue here is in how fonts work on web.
Old school fonts per se do not have âweightâ or âstyleâ. They were just a collection of font files, each containing set of glyphs. When you declare your fonts in CSS you specify what each file means. So Roboto-100-italic.ttf becomes âRobotoâ with weight 100 or âthinâ and style âitalicâ. Roboto-700-regular.ttf becomes âboldâ etc. etc. Then when you specify âfont-weightâ: 200; the browser knows what file to use, or picks whatever is closest. There are some conventions on how to translate ânormal-boldâ into numbers, however this is entirely up to you and developer to follow them.
Now new variable fonts (which sadly Figma is not supporting) have can have weight, width, slant, italic, optical size, and even custom properties specified in font itself. Each of those can be 1-1000 if supported by font face, all in one file. Yet again, you might not need all of them and map specific weight and width to ânormalâ and âboldâ in CSS.
So my guess is if you donât have fonts available locally Figma is unable to get those numbers because the web engine not letting it.
When using the inspector feature in Figma I realized the details for the type used in the button component was incorrect. The font is a medium size with a weight that should be at 500. The inspect tool shows the font weight as 400. I have attached a screen shot of the Figma type details. I also attached a screen shot of the type run throught FontDrop which shows the font weight set at 500.
Uploading: Screen Shot 2022-01-29 at 1.01.32 PM.pngâŚ
1 Like
Running into the same issue with the font Poppins. I first checked to see if I had any version installed on my machine but that isnât the case. The Regular and Medium Font-Styles are both registering as 400 weight. It should be 400 and 500 as shown on Google Fonts.
â
The Font Style is correct in the list view as mentioned by @Gleb , but the Typography section shows the incorrect values.
Same here and I would love to see that fixed.
The testers in my team have found the issue, so I run some test. I donât know if itâs the same for all fonts but it looks that there are no problems with thicker fonts.
For Montserrat Black (900), Extra Bold (800), Bold (700) and SemiBold (600) are displayed as it should. But all other weights (Medium, Regular, Light, Extra Light and Thin) show as 400 (where Medium is 500 and Regular is 400).
Itâs similar with other fonts Iâve tested (but some thicker fonts have some errors too).
1 Like
+1, I have the same issue
Below is the nightmare iâm having because seemingly Figma thinks certain named weights are actually different numbered weights.
In the middle you can see the flutter font weights iâm able to leverage. And i have to configured my Flutter project to use these values. I canât use for example 350. But thats fine, thats a Flutter problem.
To the left you can see the figma reported weights for the different named font weights.
i.e. Gotham Bold is reported as 400 which is clearly wrong in anyones world.
Gotham Thin is reported as 250
As such iâm having to manually convert these values in my application code, which means developers looking at figma will have to ignore the reported weights because they are not correct.
This is a bug.
It looks like your trying to guess the weights from either information from the font file, which is fair enough, but given the standard for font weights loosely prescribes certain weights to certain name style, (thin, medium, bold, etc) it should at least adhere to that or warn the user.
It could be that you could provide an alternative setting where by the font weights are prescribe by settings in the file.
Who knows. But whatever you have now, is waisted significant amounts of my time trying to work out why the font weights are wrong and implementation doesnât match creative. And that really is Figmas issue to fix otherwise your product isnât fit for purpose.
1 Like
Same here.
I reported this issue to figma yesterday, and they said âItâs a bug we definitely want to fix but unfortunately itâll take some time. Meaning this will likely be addressed by a long term update rather than a quick fix.â.
And they recommended me âgiving the developer edit access to the fileâ but you know Itâs paid. The worst thing is this way is the only cheat-key we have now.
I think this is a serious issue.
1 Like
Same issue here - our extra light, light, regular etc all reporting as font-weight:400 and causing issues with development. Sad to see this is 1yr+ with so many people having this issue and itâs not being addressed.
I came here for help because our devs are facing tremdous problems. And because of this we are spending too much time with communicating back and forth, design to dev.
And the client wonder how incompetent we are because the live sites look like shit.
I am a little astonished how figma comes up with cool features but cannot solve this essential issue for over a year after first request has approached you.
2 Likes
Same issue here! Surprised that this has not been solved yet.
Wow, one year after that and I have the same issue here!
I am facing the same issue. I have raised a ticket for the bug. Explained all the details. I am also a font engineer, would love if Figma fixes this issue. Browsing this thread, it looks like Figma is not giving it enough attention.
Figma developers, you can reach out to me if you need any assistance. It is a simple fix, there is a particular property for font-weight in the font data file. Figma is not reading it correctly.
5 Likes
Agree that this is a huge problem. One of the selling points of using Figma is smooth developer handoffs without needing to use an additional add on product or tool (i.e. InVision, Zepelin). This bug is creating unnecessary friction in the development process and needs to be remedied. This particular bug is causing me to reconsider the set of tools my team is using - we need to have smooth handoffs with our development team - itâs better for productivity, morale, and our cross functional team relationships not to mention meeting launch deadlines.
Same issue here! Would like to see this bug fixed.
We had this same issue using an Adobe font, and installing it locally into our font books âsolvedâ the issue. So, it seems like one workaround is to have developers all install the font on their machines. Free webfonts do not seem to suffer from this problem (Inter is handled correctly for us, for example).
Also having the same issue where while using the desktop app on Mac, the font Gotham, Medium shows as
font-weight: 400 in the Inspect panel.
The font is installed locally, so that has not solved the problem as it has for some others. I really hope this is a high priority bug to fix, b/c this adds way too much friction to the handoff process. We also do not have the resources to just buy Editor seats for all our devsâa major selling point for Figma was that it supposedly allowed for better collaboration without needing to do that. 
Upvote, this and does anyone know if there is a bug out there to fix this? This is causing issues for my UI devs.
Upvote! This is causing unnecessary friction in our team.