Suggest a Feature

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)

Please make Dev Mode Annotations visible by all roles, not just Full Dev Mode seats. This can become costly for users needing context but not all the other dev-mode features. Here’s the scenario: We have a dashboard, with cards showing a customer’s account status. This status can be mapped from multiple back-end statuses, to show just one front-end status. For example, any of the following could be mapped to a single status known to the customer as “Completed”: canceled, terminated, sold, complete, etc. This is something that the developer needs to reference, but then also the PM needs to reference in writing tickets (who doesn’t need full dev-mode access), the QE needs to reference for testing automations, and various other individuals on our team. Placing it in a comment makes it less clearly attached to the specific piece of the design, and requires us to keep documentation dispersed among different tools (Jira, Confluence, Figma etc). Simply making Dev mode annotations visible to v

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.

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!  

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 

Add the new Midjourney model to the Img gen tools

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. 

.

i can not connect to the figma remote mcp server via antigravity cli.i get an error: OAuth app with client id WPj[xxxxxxxxxxx]sit7 doesn't exist.The internet suggests that the Antigravity CLI is not whitelisted as a tool. Can you confirm?If possible, please whitelist it. Gemini cli support will end in 3 days and my workflow will be broken.

Dear developers, please add the ability to define a variable's color based on several other variables.For example: let's say I've decided that the hover state is created using the rule "brand color + 50% opacity of the theme color" (white for the light theme and black for the dark theme). But then the client suddenly decides to change their brand color. It would be really convenient to be able to create rules like this, so that you don't have to change every color manually. It would save a lot of time.  

In massive organisations with tons of projects and documents, we are trying to figure a way to tag them in order to facilitate our job when searching for anything.. The implementation of a tag system would be quite welcome. Here is a sample image of what I mean below :  

Fractional units and hugs are definitely a welcome addition to Grids, but what’s still missing is the ability to assign both the number of columns/rows and colspan/rowspan to variables.We’ve defined our website breakpoints as modes so we can build components that automatically adapt to the viewport (for example, a 50/50 layout that stacks on mobile). Right now, the only way to achieve this is by storing fixed column-width values for each breakpoint and use them in combination with horizontal auto-layout. It works, but it defeats the whole purpose of Figma’s grid system.Assigning variables directly to the grid would allow every component using that grid to automatically adapt based on its current mode (breakpoint). This would make creating mockups across different breakpoints significantly faster and more efficient.

The Figma MCP server fails to authenticate when using opencode, returning a 403 Forbidden error. To Reproduce1. Configure Figma MCP in opencode.json:{  "mcp": {    "figma": {      "type": "remote",      "url": "https://mcp.figma.com/mcp",      "enabled": true,      "oauth": {}    }  }}2. Run: opencode mcp auth figma3. Error received: HTTP 403: Invalid OAuth error response: SyntaxError: JSON Parse error: Unexpected identifier "Forbidden". Raw body: Forbidden Expected behaviorOAuth authentication should succeed, as it does with other MCP servers like Context7, Sentry, etc. Root causeAccording to Figma's documentation (https://help.figma.com/hc/en-us/articles/32132100833559), Figma only supports a pre-approved allowlist of MCP clients:- Claude Code ✓- Cursor ✓  - VS Code ✓- Codex ✓- etc.OpenCode is not on this list, so Figma's authorization server rejects the OAuth flow. DiscussionFigma's approach breaks the core promise of MCP - that any client should work with any server. This creates v