We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.
Find solutions, get advice, help others.
Yesterday I was bugged 3 times with a captcha task! Every 2-3 hours, today morning - the same. Is Figma out of their minds? WTF? Anyone else has had this idiocy? And it’s an organization account!!!!
With the new update, we have a great new feature, but unfortunately, it’s not usable with our component structure. Exposing all props of a nested instance also exposes props that we don’t want in the context of the consuming component. What if we could also select which properties to expose? This would lead to a cleaner sidebar with only valid props.
Material theme builder version 20, released in May 2024, is not operational. The plugin generates theme colours but does not update them in any project files other than the original kit project. This means that if you had any work using Material 3 kit, you are not able to update the theme since May 2024. It is not possible to do any theme-related M3 work with a custom theme since May 2024. Themes in any project that people had done in Material3 UI Kit cannot be updated anymore since May 2024. There is no other Material theme builder plugin. We are hostages of the situation. There are tens, if not hundreds, of reports on the M3 DK page and on the Theme Builder itself page where it has been ignored since early 2024. It appears that version 20 of the plugin was released untested, and the development team was immediately reassigned or disbanded. Nobody from the Material team reads bug reports; nobody responds. Figma announced the category of UI kits but did nothing else; nobody tests anyth
Hi, same issue here. I’ve reached out to Sales multiple times with no response. I just sent another one today. @Gayani_S can you please look into it? My team is interested in a Professional plan, has a a few invoicing questions, and we’re now on a time crunch. Appreciate any follow-up.Thank you!
Hi, We’re trying to export some assets from Figma (either JPEG or PNG) is fine, but running into some issues with resolution. If we export at 1x, the image is low quality… however, if we export at 2x it doubles the dimensions of the image itself (for most ad platforms this is fine, but this time we need it in the exact dimensions) I’ve tried exporting at 2x and scaling down using other online tools, but the assets then become low quality again. Anyone else had this issue / managed to solve it?
I’ve recently worked on a design in a FY 24/25 Q4 document that still needs implementing, and that quarter/year is now over (for us, I’m aware that other orgs use different dates) so I want to: Create a new FY25/26 Q1 design document Move (not copy) the page from the FY 24/25 Q4 design document into the new Q1 document Achieve the above in as few inputs as possible I would ideally expect to be able to right-click the page in the Pages panel, select “Move page to another document” and either choose an existing document or create a new one (naming & choosing its location in the process) However this route doesn’t exist, the choices are only “Copy link to page”, “Rename page”, “Duplicate page” and “Delete page”, none of which help me - I can’t even Copy the page and Paste it into a new document! Suggest this is a pretty obvious missing feature, would be relatively easy to implement, and alongside the “Move page to another document” feature there should be a “Copy page to another document”
Is there a direct phone number where someone will actually answer?
To make use of component properties better and reduce the no. of variants I tried creating my button with primitives which have 2 variants: Large: Icon size 20px (with instance swap), font style is button large (i.e. font size: 14px) Small: Icon size 16px (with instance swap), font style is button small (i.e. font size: 12px) Then I used this large variant to create a new component called ‘Button’ which comprises of all the different types (solid, outline, ghost etc) and states (default, hover, disabled etc.). Now when I take out a child of this ‘Button’, and change the properties of ‘Button’ first and then of ‘Primitive’ it works fine but when I have done this and try to change the properties of ‘Button’ again, then the icon colour gets back to primitive’s icon colour. I’m not sure what I’m doing wrong, I’ve kept the name of icons also similar as mentioned by @Molly_Hellmuth in this article for Icon Best Practices. For better understanding: P.S. If this works fine for you, please try
I’m getting the following error- We can't open this file because we're having trouble with WebGL. Please try restarting the desktop app. If this problem persists, your graphics card or driver may not be supported. This happened after updating Figma. It works perfectly on different browsers but the desktop app isn’t working. Are there any fixes for this?
👋 Hi community – first post. I was able to quickly make myself a working prototype of an idea with great results immediately. But now I’d like to use components based on what I’ve built in my design files. Possible?
I just can’t extract an image using Figma MCP. As you can see its successful, but it gives me a url like this, which doesn’t point to anything hence the images do not get rendered. Also attaching my Figma MCP settings. And before anyone talks about it losing context etc because of the size. This is what I’m exporting, just this… Because I just want to find out how to do a successful export with an image.
Can someone please tell, was is moved somewhere else or is it completely removed for auto layouts?
Hi! I’m testing a site built with the new Figma Sites feature. I’ve set the top navigation bar as a sticky element and made sure it’s positioned at the very top of the layer tree. In the Layout panel, canvas stacking is set to “First on top.” Canvas stakcking settings It looks fine on Figma and Chrome(desktop & laptop) On Safari and mobile browsers, the sticky navigation bar appears underneath the hero section content, even though it’s set to be the topmost layer in the design. On Chrome (desktop & laptop): everything works as intended — the GNB stays sticky and always remains on top. On Safari (desktop & laptop) and all mobile browsers (Safari & Chrome): the GNB is sticky, but appears underneath other layers and is partially or fully hidden. Is there a workaround or fix for this issue? Thanks in advance!
APIs, guides, plugins, and more.
Find a virtual event that speaks to you.
Find answers, learn more.
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.