Share Your Thoughts

Hi, I wanted to suggest preset colour options for Sections in Figma, similar to FigJam. The default grey colour blends into the default canvas background meaning I always need to choose a custom stroke + fill after using it. It’s an easy task but it breaks my flow to have to stop and change the colour of a section in the middle of whatever I’m doing. To be honest you could improve this just by changing the default colour from grey, but having some of the FigJam presets makes it a lot easier if you have different colour sections for categorisation.

Let us be able to add audio to the slides to give it more life. Imagine that after creating a presentation with your prototype embedded into it and some animations. You can finish it up with some amazing audio!

Figma has stopped remembering the file sorting preference: It now always defaults to ‘Last Modified’ at the beginning of session, no matter what your choice was. Can we have it back?This is now default at the beginning of every sessionI am these days having to open this dropdown ‘Sort By’ → Alphabetical 30 times a day. Last modified does not work for us since it shows us whole new set of files every time because how many people work and edit files daily; Alphabetical works better for us since we use numerical naming and then every file is correctly displayed in the intended order of product importance (home, registration, features, etc)

It’s the year 2023, and Figma still doesn’t have native table support. I just spent 30 minutes re-jigging all the “cells” in a four-row, six-column fake table because I had to delete one column, add another, add icons, and then manually re-fit/resize all the cells to get things to align properly. I can either fake a table row with a horizontal autolayout, or fake a table column with a vertical autolayout, but it’s still not a table. I want the ability to create a special frame called a Table, that: has an arbitrary number of columns and rows auto-resizes columns evenly based on content width has one or more Header / footer rows can scroll with overflow content (optional) has optional properties for hover / click states (cell, column or row) has optional properties for alternate-line shading can toggle columns or rows to hide as needed can merge or split cells as needed can set text alignment for a column (center, left, right, or currency / decimal) can set to automatically use monospa

I already have two set of position information. [984 | 2000] [ms]984 is where my red line is in the time line of animation, and 2000 is the total time available which is adjustable. I would also like to have the position if I select-drag a keyframe from somewhere within the timeline, sometimes it helps to know where I am.

Description:Currently, Figma Variables only support solid colors. However, many design systems use gradients as core brand tokens (e.g., multicolor accent fills, branded gradient backgrounds).Today, the only way to store a gradient as a reusable token is through Paint Styles, but they don't integrate with the Variables infrastructure — they can't participate in modes (light/dark themes), collections, or scoping.Request: Allow Variables of type Color to hold gradient values (linear, radial, angular, diamond), not just solid colors. This would enable:Gradient tokens that switch between themes/modes (e.g., a vibrant gradient in light mode vs. a muted one in dark mode) Full design-token parity with tools like Style Dictionary and Tokens Studio, which already support gradient tokens A single source of truth for all color tokens — solid and gradient — in one placeThank you for considering this!

it’s different from just using history. we are working on a file that was ongoing for years, some of the frames are old, some are new. we want to see what is the age of each screen to understand the timeline of our work. we could scroll back in time and see, but then we would had to jump between times, trying to discover and guess when a screen was created, rather then the possibility of just clicking on it and see the date of the creation

Every time I exit Figma and come back, the previously selected sort order is lost, and it defaults to "Last modified" – "Newest first". Previously, the selected sorting option was always preserved.

I think It’d be much better if Figma to stop treating its products (FigJam, Slides, Buzz, Site, Make) as separate file types and start treating them as page types within a single file.Every time Figma releases a new tool, it forces us into another siloed file type. If I’m working on a product feature, I shouldn't need one file for research and flows (FigJam), one for Exploration (Design), one for presenting to stakeholders (Slides), and another for campaign assets (Buzz).It breaks context and creates insane file sprawl for what is ultimately a single project.If these were all just specialized page types inside a single master file, everything would live under one roof: Page 1 (FigJam): Research & User Flows Page 2 (Design): High-Fi Mockups & UI Systems Page 3 (Slides): Stakeholder Deck Page 4 (Site / Buzz): Landing Pages & Marketing I know this clashes directly with Figma's tier/seat pricing model for different products, but purely from a UX and workflow perspective,

Hi Figma team,When creating Text Styles, Figma currently captures properties like font weight, size, line height, and letter spacing, which is great. However, color is not included as part of the Text Style definition.This means that even when a Text Style is applied consistently across a design, the color still needs to be set manually every single time. For teams working with a strict brand identity, where specific text colors are tied to specific text roles, this creates unnecessary extra steps and increases the risk of inconsistencies.It would be really valuable to have the option to include color as part of a Text Style, so that a heading style, for example, always carries its correct brand color by default.If there's already a workaround for this that I'm not aware of, I'd love to hear about it.Thanks for considering this.Justin Eleveld

Community / User RoleDeveloper / Engineer using Dev ModeThe ProblemCurrently, when inspecting components in Dev Mode, developers frequently only need a single line of code (e.g., a specific border-radius, box-shadow, or font-size) from the generated Layout or Style text areas.To get this single line, developers must manually highlight the text—which often results in accidental multi-line selections—or copy the entire code block and manually delete the unwanted lines in their IDE. This adds friction, slows down implementation, and introduces minor manual errors.The Proposed SolutionIntroduce the ability to copy a single line of code by clicking its corresponding line number in the Dev Mode code inspect panel.Interaction: Clicking a line number copies only that specific line to the clipboard. Visual Cue: Hovering over a line number could display a subtle "Copy Line" tooltip or a small copy icon to make the feature discoverable. Success Feedback: A brief "Line copied!" toast notification

When I have library updates available for my file, sometimes I just want to apply them to a specific page – not to the whole document. The Updates panel lets you select Current page, and as a result you only see which components of the current page have some update available. All good so far. Now if you want to review changes of a component rather than blindly click Update, you select the component in the list and end up in the second-level, Review updates panel. The trouble is: At this point the Current page filter is forgotten and you can only review all the instances of the document. How can I review one by one the instances of the current page only? Motivation: I would like to always review and update stuff on the local components page of my file, because if I update this first, a lot of updates will propagate automatically to the rest of the file, saving me a lot of work.

I often need to update component instances on a specific page without affecting those on other pages. However, Figma currently requires me to go through every instance across the entire file, which is frustrating — especially when working with versions and wanting to preserve old designs. While the "Review Updates" panel could help, it actually makes things worse because instances are not listed in order. For example, instance 1 of 34 might be on Page 3, while Instance 4 is on Page 1, making it incredibly tedious to track and update only the relevant ones. A "Update on Current Page Only" option would be incredibly useful, allowing users to selectively update instances only on the active page, without affecting other pages. This would greatly improve workflow efficiency, especially for large projects with multiple design versions.Please make this a feature.Thanks!  

seems like a simple thing but yet it cant find them

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.

Hello, my team is facing a huge problem with project file categorization, such as folders like Project 1, 2, 3, and so on. Each folder contains many version files. I would like to create new parent folders (which already exist), second-level, third-level, and even fourth-level folders to store my sub-files, so that my team can better organize the files.

Section names used to be bigger and more readable when zoomed out in older versions of Figma. Now they are too small to read when zoomed out, which makes it harder to navigate my file by scanning section titles. I'd like the old larger section title size back, or an option to control section title font size.

With "Text-wrap: balance" headlines could be made more readable and visually appealing.Here’s how it could look: 

Hi,Currently, the FigJam formatting toolbar only defaults to bulleted (unordered) lists. Because I mostly use numbered (ordered) lists, converting existing text into a list takes multiple extra steps: Apply bullets to the selected text. Manually change each bullet point to a number. Having a dedicated numbered list option directly in the text toolbar—or a quicker shortcut—would save a lot of time.Are there any plans to introduce direct numbered list formatting in FigJam soon? I’d love to hear the team's thoughts why it wasn’t added explicitly now?Thanks Default option After explicit mention of a number 

Whose idea was it to put the little icon for the new AI agent so close to the upper right corner of an object? I can’t tell you how many times I’ve gone to adjust the size of an object and accidentally opened the agent. Each instance doesn’t take that much time, but when you do it countless times a day, it makes work that normally feels fluid feel disjointed. If I want to open the agent, the option in the left nav panel is super easy to access. I don’t need the agent connected to every object I touch. I’d like to see the user research (or lack thereof) that made team Figma think this was a good idea. You’re assuming the agent is so helpful and so needed that people need it right there. That’s confirmation bias at it’s finest. Please take this away or at least move it!  

Add the new Midjourney model to the Img gen tools

Hi, I think my request is obvious and I bet all pro tier users agree. We really need this. Thanks

Right now under price I can choose All, Paid, and Free. Under “free” I often find items that aren’t actually free but are demos, with limited functionality or times they can be used before you have to pay money. From a marketing perspective I get it, the plugin technically has some free functionality, but if its limited by time or uses, the use of “Free” is misleading. So I think what would be ideal is a new facet, “demo” for all plugins/resources that aren’t fully free.The other request is a filter to offer the option to include or exclude plugins that use AI to perform their function.

When working with large files, I encounter such wasteful actions as expanding/collapsing each selected group of layers.I find it better to perform these actions in bulk. Here is my solution to this problem. Please vote if you are also troubled by this time-consuming process. 

.