Suggest a Feature

Is there any work currently being done to allow a mobile navigation in a hamburger menu for Figma sites.None of the navigation blocks have this option. in the mobile component and even when I create components with an overlay interaction, the overlay will not appear when I use the component in Figma sites no matter what I try.This is a pretty big limitation to one of the most common patterns in mobile UI.Is there any way to accomplish this that I am missing?

FigJam的工作背景版本增加了切换为深色背景的功能，可以根据需求设置。白色太耀眼了，我一直习惯Figma的深色背景，用起来非常简单。

It would be helpful to have the ability to download a CSV file of members with all of the data available online. It would also be helpful to be able to view historical data for specific time periods in the event permissions have changed or members have been deleted.

Feature Request: Multi-Select in Point and Edit Current: Single element selection onlyProposed: Ctrl+Click for multi-select with task list Benefits:✅ Select multiple elements at once✅ Clear task list above chat: "Task 1", "Task 2", etc.✅ Reference specific tasks: "#Task1 change color to red"✅ Faster, more precise, less confusion Use Case: Complex forms/dashboards with many similar elements

I’m working on our team’s design system and we’re planning to use CSS Grid as the basis of our page structure in code. I’d like to replicate this behaviour in Figma to close the gap, and while the Grids frame setup in Autolayout is CSS Grid, it’s incredibly limited. You have a max of 12 columns (which is fine, that does everything you need) but the rows having to be predefined by the number, and worse, by having to be 1fr makes this setup useless. This means rows have a predetermined height based on the number you add that evenly divide the space within the frame. But content is king, and they don’t respond to the heights of what lives within them or collapse if something needs to be hidden. It’s frustrating that Grids was released without even this basic aspect, I don’t know what you can do with the current set up except for a super simple splash page, and the inspect makes it even more useless as it won’t be accurate. I’ve been told by (supposely) an employee at Figma

I’d love to see some enhancements to the Projects screen and file browser. There’s a variety of old topics for this out there, but they appear dead – many of them years old. Better UI for ProjectsDisplay descriptions – Currently you can add project descriptions in the project settings, but they don’t display anywhere Display metadata – See belowAdditional metadata for projectsTags – Ability to add tags to projects, particularly around what products they are for Statuses – Similar to the ready for dev status in designs, allow labelling project statusFiles not in a projectWith miscellaneous concepts and FigJams, sometimes they don’t have a dedicated “project”. We don’t want them in drafts though, because we want to have shared access. This usually ends up with us creating a “miscellaneous” project to store these files. It would be great if files did not have to be in a project, similar to ho

Figjam’s Pages and their restricted horizontal scrolling has become an issue for my team. Typically, we work left-to-right. For instance: When we have a meeting with stakeholders, we create a board with the agenda and content. During the meeting we annotate that board, then to the right, we create another board to ideate the next topic. As more work items and meetings come up, we add boards to the right, so that we have a visual trail of the work we’ve done. Figjam’s limited Page canvas have made it very hard to work like this because we can’t keep adding content to the right because the canvas ends. Because of this, we wrap our work lane up (because we have more vertical space available), but that makes the Page more difficult to navigate because a user then has to zigzag through the trail of work. Questions: Do people ever use the vertical height of a Figjam Page to it’s fullest extent? Is there a way to limit the Figjam board based on a storage level instead of a ar

There’s no visible scrollbar in Figma prototyping mode. Yesterday we’re having user testings and once again this same topic popped out. Some of the users didn’t thought that they could scroll prototype because scrollbar wasn’t visible. One of the user was using laptop’s touchpad and he wasn’t able to scroll with only using touchpad. Guiding user how to use prototype during test can harm testing situations. Atleast it’s sure that if user thought that he can’t scroll it leads to biased feedback about product. If there’s some reason not to have scrollbar it could be atleast optional feature that designer could turn visible scrollbar on from options. It’s not only who has came across with this weakness in Figma. Here’s old Spectrum thread about same topic but Figma hasn’t done anything for this yet and I hope

I was trying to find a way to combine more than one string variable together without the need to create to text layers. My use case is: I have plenty of small string variables with specific details associated with a main variable mode. I have plenty of variables modes. I need to combine some of the variables together to generate a more complex string. Current possible solutions (both the solutions are not great for various reasons): Create 2 text layers and connect them with String Variable A and String Variable B. [I need to create an auto-layout frame that contains the 2 layers and resize automatically based on text content and if a variable is empty for any reason] Create a String Variable C that contains String Variable A and String Variable B. [I need to copy and paste the content of both Variables A and B into Variable C. If anything change in time for A or B, I have to change also C]

SummaryAllow Figma Make to read an .npmrc file so teams can install and use internal or private scoped packages (e.g., @company/components) within their projects.ProblemOur organization maintains internal web component libraries that align to our design system in Figma. These components are published as scoped npm packages (e.g., @ourorg/design-system). Currently, Figma Make does not support .npmrc configuration or scoped package resolution, which prevents us from using our own code directly in Figma Make. It would also reduce the amount of code Figma make generates if it doesn’t have to generate common component code.ImpactWithout this support, designers cannot easily work with the same components developers use in production. This creates a disconnect between design and code, increases manual work, and raises the risk of inconsistencies.

As a product designer, I find myself spending quite some time setting up different boards, pages and files to structure my work well. Yet as a pretty unstructured person, I find myself struggling with this. I therefore got thinking how much I would love a set of file presets, that would automatically set up a good structure for working on a digital product, like a “Product Exploration - preset” or a “Service Iteration - preset”. For instance, it could contain files for different purposes, such as iterations and finished sketches. And within those files already organise them in relevant pages, such as “Components, Flow A, Playground” etc.  Sounds pretty vague as I´m writing this, but think there is a good idea in there somewhere.

Something like the below features  would make my world 100,000,000,000,000,000,000s easier native support: the ability to drag a mp4 or animated gif into a frame, lay text on top and re-export as animated gif or mp4  the ability to pick a gen ai model and generate a clip as background, lay type on top and export as mp4 or animated gif with any gen ai feature the ability to allow users to select from a specified library of reference photos  Hope this helps!  🤣

Hi Figma team,After updating the desktop app today, I noticed that the Auto Layout panel no longer appears when selecting an Auto Layout frame. Additionally, the Layer panel now uses icons, making it difficult to distinguish between Frames and Auto Layout containers.Interestingly, the web version works correctly, showing the Auto Layout settings as expected.This change has significantly affected my workflow, and I hope you can either restore the panel visibility or provide a clearer way to access Auto Layout settings in the desktop app.Thank you for your attention!

I use percentages in a project for the letter spacing. I can’t use variables to achieve this value. It always defaults to pixels.

Hey Figma team,The progressive blur update was 🔥. I’m guessing the implementation uses a linear grayscale gradient (limited to two color points) as a blur map to control the effect. If that’s the case, adding radial progressive blur shouldn’t be too hard.Also, if you’re considering custom blur maps, it would be awesome to let users control crop/fill/fit/tile of the blur map, just like the regular image editing options. Plus, a toggle to switch between blur map input vs. blur map output would make experimenting way more intuitive.This could give designers way more flexibility and open up a ton of creative possibilities.Thanks for considering!

Firebender is a coding agent, that many android engineers use. Currently the Remote Figma MCP does not work whenever I configure it. Is there any way to get this to work? I tried:https://docs.firebender.com/context/mcp{"mcpServers": { "figma": { "url": "https://mcp.figma.com/mcp", "type": "http" }}} and I get a message saying to reach out to Figma support to allow Firebender MCP client use OAuth scopes with the Figma remote MCP

When using Freeform, is there any good way to set distance constraints so that I can achieve something similar to padding in Auto Layout?

Hello, I really would love a setting that would make the new layers, freshly duplicated layers, etc, appear downwards - on the bottom of the list if nothing is selected or underneath the currently selected layer. In other words, to change the general direction of layer stacking - to go from top to bottom, instead of bottom to top only, as of now. This is very logical, isn’t it? We create pages in figma and they go from top to bottom, most designs are created from top to bottom, most content flows from top to bottom. Then why do layers go freaking upwards? 😀

Ok maybe we got that wrong, but it seems that the new Dev Mode “Annotate” and “Measure” Features are only available to designers but not the developers themselves? We’d think it would be very useful for them as well. When the developers want to add some info during handoff, or if we forgot something and they want to add that info later as a reminder etc.

Please bring the lighter, less intrusive FigJam background grid style into standard Figma files. It needs an easy way to be toggled on/off Add a new "Dot" style within the Layout Grid settings, allowing for a dot pattern.

I saw a post on linkedin that suggesting a great feature.Font selection shows a hundreds of fonts on the list, but we all have our favorite fonts. why not to save most used fonts as starred or bookmarkhttps://www.linkedin.com/posts/tim-agayev_%D0%BA%D0%B0%D0%BA-%D0%B4%D0%BE%D0%B1%D0%B0%D0%B2%D0%BB%D1%8F%D1%82%D1%8C-%D1%88%D1%80%D0%B8%D1%84%D1%82%D1%8B-%D0%B2-%D0%B8%D0%B7%D0%B1%D1%80%D0%B0%D0%BD%D0%BD%D0%BE%D0%B5-%D0%BF%D1%80%D1%8F%D0%BC%D0%BE-%D0%B2-activity-7395207256302047232-3-WpHere is screenshot posted by 

Could you implement a feature that allows the AI chat to memorize the conversation and then archive it to clear all the history messages? It tends to get really laggy at some point when the conversations has been going on for a few days. This is typical in Chat GPT as well. But this needs to be sorted. When I work with figma make at the moment i haev to write all my updated request in a notepad document and then paste into the chat becuase its lagging so much. And if claude sonnet doesnt allow this workflow, come up with something else. Thanks in advance!

I don’t want to see some properties or values of any properties, if they are not used in the component. This is making it difficult to use the components. Example: I have a button component with Property 1 (Type: Primary, Secondary) Property 2 (State: Default, Processing) I only want “State: Processing” to be available for “Type: Primary” button. I have created a Variant of “Type: Primary” button with “State: Processing”. Currently the problem is when I use “Type: Secondary” button, I can see “State: Processing” in the properties. When I select it, the button “Type” changes to “Primary”. It would be great if the “Processing” state doesn’t show up in the properties list, since I don’t have that “State: Processing” created in the component Variants.

HI! it would be an incredible time saver if you could PLEASE consider adding a key stroke for filling container and hugging contents for objects selected within auto layout! Please come thru 🙏🏼

We want to use string variables for translation handoffs. It is common in our projects that we use long text elements, that have mixed styles (adding links, adding bold to key phrases). When we add variables to text, the font style is “flattened” when switching modes. We can create text with HTML tags like “Hello <‘b1’>World<‘/b1’>” (b1=semibold equivalent of the font style used) so our devs know where to style the text, but it makes it difficult for us to evaluate visual aspects of our texts (like “Is the text not too busy? there’s to many bolded words”). It would be great to have a tool that can do both: add font styles to strings, and render them at the same time.