Share Your Thoughts

Please simply support the Code Syntax of Variables more holistically in DevMode. Especially in Annotation Properties(!). We recently started making use of the code syntax of variables, but unless it is widely support, it does not seem to be very beneficial for our developers.

As a consumption side of the design system in Figma, it is very hard to realize there’s more information inside the component descriptions. It is like, I didn’t know the team has link documentation there that’s useful for my designs.  It is hard to know that a couple of text lines are clickable and that they contain more than just text. 

The user story is as simple as “As a user of figma design when using the AI tools such as `boost resolution`, `edit image`, `remove background`, I would like to hear a sound feedback when the job is done, so I can do something else while waiting for it to complete and be more productive” I don’t know you guys, but I like the AI features a Lot, and I’ve been working a lot specially with the edit image for videogame placeholder assets (it’s amazing), but I just don’t want to stare a the screen for a 2 minutes doing nothing, I would like to leave it working and do something else. I hope this is a super simple feature you guys can make, it would be good :)

SummaryEnable Figma Make users to preconfigure the default code output framework (e.g., Angular, Vue, React) and set organizational coding guidelines that are automatically applied when generating code.ProblemCurrently, Figma Make defaults to generating React code. While prompts can be used to switch frameworks or enforce custom rules, this adds repetitive manual steps for every session. Our teams have established rules and standards (framework choice, naming conventions, linting rules, accessibility standards, etc.) that we want consistently applied from the start.Impact Designers and developers must repeatedly remind the system of our preferred framework and rules. Inconsistencies can arise if someone forgets or phrases the prompt differently. Slows down adoption because teams want their code to be generated within their established ecosystem by default. Proposed Solution Allow users to define a default project configuration for Figma Make (framework, package manager, language ve

I'm so pissed off by FIGMA MAKE!!FIGMA MAKE used to be very smart, quickly understanding any requirements I asked for. Lately, however, it's been incredibly clumsy! I've been given a lot of requirements and then constantly making random changes. I find this experience incredibly poor! I'm so angry!

Hey there, I’ve created a branch and added a component to our library. So far so good. Then I accidently moved an instance of a component a bit, so that in the “Branch Review”, it says “Node Reordered, Position, Rotation, or Scale changed”. And yes, that’s true. Even though, nothing has changed. I missed to it CMD + Z to revert it, so now when I want to merge, I have to merge it even if I don’t want, and then push a library update of this modified pattern. My suggestion would be the same as we can do it in VS Code for example. Before commiting something, you have the ability to “Discard changes” meaning that all the changes you made in this commit will be removed and the component will be in it’s main branch position/state. That would be helpful for not having to merge something you don’t want/did only for testing purposes.

Before: After:I want the edge I’m adjusting (the right edge) to snap to grid. So the answer is not “Turn off Snap to Grid”. Figma, when the user is making an adjustment to A, just make adjustment A. Do not go head and make adjustments to other random things B, C, D...

Hi there,I’d like to propose a feature that allows individual sections to exist within a parent section, with the ability to collapse and expand them via an accordion-like function. The default state would be closed—similar to an index—so that child sections are only visible when expanded.Currently, it’s challenging to guide developers to the correct layers because the default open view doesn’t always reveal all sub-sections, which can make navigation and referencing less intuitive. This feature would help improve clarity and streamline collaboration.

Please kindly add native support for custom-assignable keyboard shortcuts within the Desktop App. I currently cannot add any custom keys and our workflows would be greatly improved with this essential feature. Thank you! 🙏🏼🌊Computer: Mac Studio M1 | OS 15.3.1

When selecting semantic tokens/variables for colors, you can’t search by section name—this is a HUGE MISS. For example, if I need a color for inputs and type “inputs,” in the color selector, the system doesn’t surface the variables you’ve grouped under that section. That feels like an obvious expectation. On top of that, actually locating these colors is incredibly frustrating when selecting a color. Whenever I’m building something new in a complex design system, this becomes one of the biggest pain points. It’s like there wasn’t any UX done for this. 

In a Design file I can create structure and hierarchy for my font styles by using a naming convention that leverages a “/”. However, even if it’s the same naming convention, this doesn’t result in the same outcome in Slides (in Design. Mode or Slides Mode). In a Slide file in Slide mode, I see the whole name in a list with no hierarchy applied. In a Slide file in Design Mode, I just see a list with no hierarchy in the dropdown + the prefix before the “/” is cut off. But then when I select it… it shows up in the panel… It’d be great to haver a similar behavior in Slides as in a native Design file…  

Currently, when working in Libraries, Figma picks up changes and in the modal to Publish, you are basically forced to Publish any changes that Figma picks up. There’s no way to “reject” those changes. This adds a layer of complexity because Figma doesn’t say how things got changed, it just says that something changed. So often times, we’re not sure why Figma is saying it got changed when visually things look the same. We also keep our editor list rather small but it happens often where I log in the morning, see there are changes, ask the team did anyone make changes, and they all say no they didn’t do anything. From that point on, there’s nothing to do but publish those changes which has negative downstream effects to our entire design org who uses our libraries. They see that they need to update their libraries but for no good reason. We do add comments when we publish so we have to say stuff like nothing actually changed, Figma is just picking up changes when there are none. Does any

It looks like impossible to change the gradient direction?  the gradient is popping over where i have to drag it from and i can’t find out how to change it 

can we have option to switch from desktop, tablet and mobile when prototyping from figma design, similar to figma sites 

Just putting this suggestion here for the ability to indicate what symbol / value to add to the end of truncated text instead of just the ellipsis (...)Technically there is support for this in code via the text-overflow CSS property, so it might be good to also bring that functionality within Figma Design.Additionally, hoping it could also be possible to change the way text is truncated, where we wouldn't be limited to just text lines, and have the ability to switch to set the truncation via number of characters in the text layer.

 안녕하세요. 초보자가 “MAKE”에서 웹을 개발하다 보면 너무나 많은 버전 히스토리로 인해 웹페이지 로딩이 느려지고 있습니다. 이미 FIGMA 팀의 도움을 한번 받은적이 있는데,앞으로 자주 사용하다 보면 매번 FIGMA 팀에 도움을 요청하기가 부담스러울것 같기도 하고,시간적인 소요도 제법 있는것 같습니다. 사용자가 스스로 버전 히스토리를 삭제 할수 있는 기능을 구현하는건 어떨까요?

Hello,We currently are creating annotations utilizing the native Figma annotations tool, but we also need to recreate the annotations to create a format that we can export to pdf for client review and approval. If we could make it possible to turn on Annotations and have them visible along with the frame elements, so they could be proofed by others not within Figma that could be exported as a hard copy, that would be an amazing feature. Currently we need to move them every time the layout shifts. It isn’t very user friendly.

Lately, I’ve been trying out asking Make’s model for design feedback and collaborate on ideas, BEFORE I want to make actual (code) changes. This is a good workflow people use with more experience with prompting.Unfortunately, I’ve noticed that when I ask it to “not make any changes” because I’m asking for ideas first, it just gets stuck on “Reasoning...” 😅 💡 Proposed solutionHaving a Chat Mode that can be toggled, similar to Lovable, would probably be a nice user-friendly way to provide this type of functionality, without having to prompt for it.

Kind of what this says really. Figma Make is a brilliant tool even in Beta.I have a workflow of taking screenshots from Make and putting them into FigJam and sketching over them with my iPad, so it would be great to have the copy to PNG function that exists across the other products (even if it was an interface button). It’s also useful when needing to paste a screen back into the chat to provide feedback.In terms of working with Cursor it has great conversion of images. Ideally there needs to be a way to export all screens (or a selection) to an image folder. At the moment it’s painful having to take screenshots and then deal with the external organisation of these. Exports should have some form of naming logic too (date, time, screen, etc...)

I’ve been playing around with converting figjam notes into slides. Would be great if Figjam could talk to the custom templates. For example, a sticky labeled insight #1 should use the Insight slide format from this Custom Template

It is unfortunate that the ability to export assets is tied to the ability to copy code. My developers need to be able to copy code from my mocks in dev mode but it would be best to be able to separately NOT allow asset export to force development to pull the assets from our internal repository.

Right now, overlays in prototypes only work if the trigger and the overlay frame exist on the same page. This creates big limitations for real-world workflows: Many teams work with a WIP page for ongoing design and a Presentation page for final client delivery. Moving frames between pages breaks all prototype connections. Centralizing overlays in a dedicated page is not possible, since prototype actions cannot target frames outside the current page. This forces designers to duplicate overlays on every page, which is error-prone and makes maintenance harder. 👉 Feature request: Please allow prototype links (including overlays) to reference frames across pages, with persistent connections that don’t break when moving components or screens between pages.This would massively improve scalability for large prototypes and save hours of re-wiring interactions every time we restructure or clean up pages.

Publishing and updating has become more specific and more powerful (I think) with each update. It also has become more cumbersome equally with each update. We publish/update every 2 minutes if we’re unlucky and that takes a lot of clicks currently. Go to the right tab in the library, open the publish, pick what to publish, avoid the extremely subtle “Make” banner, click the right button, etc. etc. etc.. Updating is the same.So I would love to just have a magic button that does it all for me on the highest level. Although I’m sure there are plenty of edge cases where this idea might fail, but for me it would be great to click the magic button and having it publish all tabs that are open, have changes and are a library. At the same time, update all open tabs that use one of these libraries.Food for thought?

It’s a kind of missing feature that breaks a bit the productivity and in my case creates frustration :( It would be nice to add an extra “+” on the edges of a selected column/row to add a new one just on the side.Thank you for reading! 

It would be great to have an AI model integrated into Figma’s comment feature. For instance, when someone comments on a design, the AI could generate a draft version based on that feedback. This would help designers better understand the intent behind the comments and refine the final design more effectively, rather than relying solely on written notes.