Share Your Thoughts

  Currently, an interaction (e.g., a button click) on an object can only have one destination per trigger type. If a designer wants to use the exact same object in two different flows (e.g., a "Happy Path" and an "Error Path"), they are forced to either: Duplicate the page, breaking the "Single Source of Truth" principle and increasing maintenance. Use (page)components and instances, not ideal. Use Complex Variables/Logic, which is powerful but overcomplicates simple flow branching and makes the "Prototype Settings" unnecessarily complicated. RequestA feature where a component can have multiple destinations for the same trigger type depending on which 'Flow Starting Point' is active. 

So, my company has a card component which may have 3,4,5 or whatever number of columns is needed - the same for rows. However, I cannot build a straightforward component without either: a) instead of using grid (the way the devs usually do), using regular autolayout with a bunch of max/min/fill properties. b) creating a huge megazord component with all the variants we´d need or  c) resorting to detaching.  It´d be really useful to be able to toggle rows and columns on a component instance to create really customizable and powerful components.  Would be very useful not only for cards but for things like tables (eg toggle the whole column with checkboxes or with actions) .

Is Figma ever going to allow us to collapse/expand pages in the sidebar? What about text-wrapping layer names?

I’d like to suggest adding support for viewport-based height (for example 100vh) in Figma Sites. In many real-world design scenarios, especially for web and responsive layouts, designers need a page or a specific section to always take the full height of the user’s browser viewport. Currently, this requires workarounds with fixed frame sizes or manual resizing, which breaks responsiveness and does not accurately reflect how layouts behave in production. Tools like Framer and Webflow already support viewport units, making it easy to design hero sections, full-screen onboarding, landing pages that adapt to the user’s screen height. Having a similar option in Figma, such as setting a frame or section height to “Viewport height” or “100vh”, would greatly improve accuracy, responsiveness. This would be especially useful for: Full-screen landing sections and heroes Onboarding and single section screens More realistic responsive previews without manual resizing  I believe this feature wou

I really need adaptive font sizing for text inside fixed-size text boxes, especially for Buzz.Here’s the use case:We create a creative for social media. We then create multiple sizes of that creative using auto-layout, constraints, etc. After that, we generate Bulk Create versions in different languages.The challenge is that text length varies significantly between languages - for example, French is often much longer, while Japanese can be much more compact.It would be incredibly helpful if the font size could automatically adapt to fit the fixed text box, similar to how text behaves in PowerPoint or Keynote.This feature would save a huge amount of time and effort, especially when working with multi-language creatives at scale. I believe many teams would benefit from this.Thanks in advance — really looking forward to this improvement. 🙂

I am writing to request a new feature: the ability to connect my SyncFusion license to 'Figma Make'.Currently, I need to use SyncFusion components while building my designs, and having this integration would allow me to use my licensed assets directly during the prototyping process. This would greatly improve our workflow and design-to-code consistency.Could you please let me know if this is currently possible or if it's on your roadmap?

In regards to Figma Analytics, there’s two ideas I would like to suggest!On the table on the main library statistics page, it becomes very difficult to remember what the columns are as you scroll towards the bottom. Is it possible to make the header bar sticky so that I can still see the column titles when I reach the bottom? Also it is helpful to see how many times a component is detached. While that functionality exists, we cannot tell where the detaches are within the files that use that component/variant. Having the count continue from the variant table into the table with the files that use that variant would help use immensely so we can do some user research to find out why that team/file is detaching that component.Thank you!

I noticed I’m able to set a default color (variable) on shapes, so when creating a new shape it uses the defined color (variable). However, this behavior doesn’t work on text. I’m guessing this has to do with the default text color being tied to the color of the page. However, I’d prefer the option to be able to set a variable as the default text color. When doing rapid iterations, it’s often the case where I accidentally have text unlinked to a variable, and sense dealing with dark grey colors it’s easy to miss some text being black. Tried to set the text to default to my dark grey variable color but it was at this point I realized I was unable to.

Please give the ability to change position of toolbars/widgets (or at least swap left and right), my neck is already in chronic pain to constantly turn my head to keep looking on the right. I want to pop out the damn thing and place it where i need it to. When you have a large monitor it is a pain! Everything tiny and far away from what I am working with.

Upon using Figma Sites, one of the first things I noticed was that you can’t nest pages inside other pages or folders to keep related content organized in the sidebar (like /projects, projects/project 01, projects/project 02, etc.). Dividers, which we got last year, definitely helped a bit—but having collapsible folders or nested pages, like with layers, or pages in Framer, would seriously help keep things organized – especially for URLs.

It would indeed be game changing and important if we could get the option to automatically swap between variants based on the actual size of the parent frame. This could simulate real life complete web applications and be really helpful to show when and how a breakpoint should interfere with a component.

Figma needs a glyph panel to access glyphs per specific font. Photoshop and Illustrator have this feature and it is a necessity for typographic design. Having to leave Figma and go to Photoshop or Illustrator is incredibly inefficient. Implementing better type setting tools within Figma would be a major improvement

When you come to a point that you want to create a dark translucent container on top of a colourful background, we all notice how desaturated it becomes, and how  i.e. Apple seems to negate that. And after having tried each blend mode, it just doesn’t give us 1 blend mode to rule them all and have your container be how you want it to turn out when changing the background to a dark grey background. So instead of messing around with blend modes, how about the backdrop-filter saturate gets introduced in Figma, and bring back some colour?

In my opinion, I think the position of "publish" isn't intuitive. Its new position is on the bottom of the left side bar, which is easy to ignore.

While presenting to my students (all in view mode only), one of them realized that they could turn music on for the entire class by clicking on the music button. I think that users with view access only should not be able to start the timer or music. Could you restrict access to to these widget to only collaborators in edit mode. Thanks, Sean

I have the preference “Use Scroll Wheel Zoom” enabled, and love that this option was added. But unfortunatly, it is very frustrating with the workflow.I use my mouse wheel to zoom in and out, and then click and hold my mouse wheel to pan around. This is just what I am used to in other software.My mouse wheel can also be pushed left and right for horizontal scrolling. If I accidently move the wheel left or right while clicking to pan, then Figma will switch to a “scrolling” mode. Now when I try and use my mouse wheel to zoom, it will scroll vertically instead until I do a single mouse wheel click.It would be great if “Use Scroll Wheel Zoom” was enabled, then horizontal mouse wheel scrolling would also be disabled. Or at least don’t switch it to a scrolling mode

Angular + Figma MakeSupport for Angular in Figma make:Whoever think it’s important - Vote. Thanks,Galit

Dear Figma Team,I am a big Figma fan and want to fully transition from Adobe, I’ve identified two key text-related SIMPLE features that would greatly improve Figma’s layout design capabilities: Text Wrapping Between Text Boxes Figma currently lacks the ability to wrap text between multiple text boxes, making multi-column layouts cumbersome. A native text threading feature (like Adobe indesign) would allow text to flow dynamically between boxes, especially when resizing frames. Hyphenation for Improved Text Alignment Long paragraphs in Figma often result in uneven spacing at the edges. A hyphenation feature (like Adobe Indesign) would automatically add dashes to break words at line ends, improving readability and visual consistency. These features would make Figma more versatile for typography-heavy designs and streamline workflows for users transitioning from other tools.The community has been asking for this improvements for years and still we have not seen any response from you. Pl

I’d love Figma to add the ability to view/sort last edited frame in a file. This is handy because when I return to a project or task after a long while and there’s a ton of ideation content in a file, I have to spend a while trying to figure out where we last left off. I can change my workflow to handle this (maybe adding a special title for the last version or putting a huge emoji near the frame) but it would be nice if Figma would just have a feature that would let me see last edits on a list, I could click on the edit to bring it into view. I could see how saving a timestamp with every edit may be too burdensome to data storage but what about giving us the last 5, 10, or 20 edits? Then drop off the timestamps to save on data storage and bandwidth? Just some ideas.If I’ve suggested a feature that already exists, please let me know.We love Figma, Thanks!

It would be awesome if we could set properties like font, size, alignment so everytime we start a textbox it would have all the properties already set. This exists and works with shapes for example, but the text ends up overridden by the last textbox you edited. Is there a way to workaround this or should it be a possible new feature? Thanks

Why do visual designs created by Figma Make not automatically use Auto Layout? It’s really hard to edit designs and maintain the correct padding. The grouping of layers instead means changes require me to re-create the design because I need auto layout.

Dear Development TeamI have seen many solutions for Menu, Sidebar, Radio Button Group and Tabs. All of them have one in common - only one can be active. So means if you have selected one and select after another item the one before has to be unselected and the selcted has to change to the active one. At the moment people go and do many variants or the better solution is for each State it needs to set one variable for the selected one to “true” and all the other once to “false”. That’s not like an expected solution.For Example the possibility to have local variables (not global) for a main component which are saving the value.So you can easy set the value of a variable and inside to compare the value. For example is the value ==3 than go to menu 3, set radio button 3 to true, set the tab 3 and show it, .. Also a Bit Logic is possible. Exampleconst RADIO_A = 1 << 0;const RADIO_B = 1 << 1;const RADIO_C = 1 << 2;That helps a lot and you have a proper solution.Greetings Fr

Four years since the initial feature request, 14K views since the first request… and still nothing.It’s completely unbelievable that such a basic and essential feature hasn’t been implemented yet in a tool that prides itself on being at the forefront of creation.⚠️ Fellow creators : if we want to have any chance of making this happen, please leave a reaction or a comment on this discussion. Together, maybe we can gain the visibility needed so that we can finally work with an organization worthy of this beautiful craft. Apes Together Strong 🐵🐵🐵Image credit: Court_Kizer

Currently it is only possible to check accessabilty (color contrast) with detached variables. Please make that possible because that would be very helpful and make Figma more efficient.

Hey Figma Community, I’m excited to kick off a discussion on a feature proposal that I believe will significantly enhance our workflow: an easy way to remove missing libraries and immediately conceal the styles copied from other libraries to be applied as core visual styles within the new library. The Problem As we continuously evolve our design projects, we often encounter situations where styles and components from old libraries are no longer relevant or used. However, these linked styles still persist, creating unnecessary strain and clutter within our current design files. It can be quite frustrating to see missing library notifications, giving the false impression that essential design elements are missing when, in reality, they are not even utilized in the new library. The Proposal Introducing a Complete Detachment Button for missing libraries, which will: • Remove Missing Libraries: Allow users to completely detach and remove references to missing libraries. • Conceal Old Styles