Suggest a Feature

Currently, the "While in view" trigger is too binary. The animation often doesn't feel right because it won't trigger until the entire layer is within the viewport, or it fires the moment a single pixel touches the edge. This makes it impossible to time smooth reveals—like headers or hero images—so they glide in exactly when the user is actually looking at them. It makes high-fidelity prototypes feel "jittery" and unpolished.The Suggestion: I’d love to see an Offset (or Threshold) property added to the Prototyping panel for all scroll-based triggers. Custom Thresholds: Let us set a pixel value (e.g., 200px) or percentage so we can control the exact moment a reveal starts. This ensures the animation happens in the "Active Zone" of the screen, not just the moment the layer edge appears. Better Handoff: This takes the guesswork out of the design-to-dev process. Instead o

It would be highly beneficial if Figma provided a way to view the creation date of a project. Currently, there is no clear or accessible indication of when a project was originally created, which can create challenges in project tracking and management.Having visibility into the project’s creation date would help designers and teams better understand project timelines, especially when working across multiple files or collaborating in larger teams. It would also improve organization, auditing, and version control by providing clear context about when a project started.This information could be displayed in the project overview, file details panel, or alongside metadata such as last edited time. A simple and visible timestamp would significantly enhance usability and workflow clarity.

EDIT: i can already do this by using the Gap function.It’s still almost impossible to design for fluid widths in FigmaBut with the new Grid Beta, it is now possible to set up for example a 12 col grid system , see my screenshot:https://prnt.sc/fetKFckcQpT4 Basically I set the colums to 1fr, and i set the gutter to my design in pixels. This is how most grids work on a webpage. Now if i rescale horizontally, it keeps the gutter, and scales the grid like in real-life.But on smaller screens the gutter usually need to be smaller, and it would be extremely tedious to manually replace 12 gutters for EACH and every frame i use this on a webpage (potentially hundreds)So if we could use variables to the colums in Grid Beta, that would be just one click solution and we almost got a working fluid system in Figma.

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 m

Hello,Looks like Figma doesn’t give you an option to chose dark mode colors when you assigning semantic tokens, in the menu only light mode colors even tho I have dark mode too in my primitives.So that means I can’t use different color pallet for the dark theme (in case if I’m actually want to use different colors in my dark mode completely different pallet). I’m I missing something? or It just feature they didn’t thought about yet? or never will?

Can’t do truly responsive tables in figma.I design complex applications that require a lot of tables. Currrently, there are two primary approaches to responsive tables in figma: row-based and column-based.In reality, neither of these is fully responsive. In row-based ones, when a cell's content expands in height, all cells in that row adjust accordingly. However, if the content expands in width, the cells that are supposed to be in the same column don't follow suit because there is no relationship between them. The same happens with column-based tables, but the issue lies with the height. There is another approach called grid-based tables that almost solves that issue. The downside is that you can't use components in a simple way, like slots. If you need to create a prototype with hover effects, the interaction

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 C

Our design system leverages mix blend modes for hover states so our icon buttons appear on any background color and remain accessible, without needing separate hover–on-primary, hover–on-secondary, etc tokens. We use multiply for light theme, and screen for dark theme. It would be really awesome if we could apply blend modes directly to the color variables, OR support blend modes as variables in general. Our current work around is to apply the blend mode directly on each component variant, but this requires us to define separate light and dark theme variants. would be great if we could use variables here to have it automatically switch between light/dark.

Please can we get percentages for variables? We can use percentages manually, but we can’t create a percentage as a variable. This would speed up my design to dev process tenfold, and considering we can already use percentages in the design, why disallow it in variables?An example is I want store values for line height and letter spacing as percentages which behave responsively/dynamically, so when creating type variables I don’t have to do manual calculations, store 10+ letter spacing/line height values based on which font size they will be used with and hope I never change the font size variable in the future.

It would be beneficial if Figma included the option to enlarge the interactions panel. Reading all the conditional and variable interactions within the small preset frame size can be challenging. Enabling users to expand the panel size, similar to the way the variables frame can be expanded, would make it easier for users to review the interactions they have set. Being able to copy interaction would be extremely helpful and reduce redundant work

The title just about summarizes my issue. Developers until recently had access to ruler measurements and annotations with their Dev Mode seats. Recently, these tools were stripped from them. I don’t understand why only designers can measure distances or leave annotations, so long as they are not editing files, why should Devs be unable to annotate or inspect files using the tools Figma designed for Devs to inspect files?Good design practice in Figma often requires us to build things differently than they would be built with actual HTML/CSS. with Autolayout in mind, it’s better to determine the space between objects rather than apply padding to the top of Divs as many devs would do. However, when a dev wants to measure the total space between elements, they should be able to use rulers to make the measurement THEY need and not the one Figma decided they should have. Why were these tools stripped from Developers? We’re already on an Organization plan, paying quite a lot

Can you please add the ability to add headings to the pages panel? I know Figma gave the option of 'dividers' by typing ' -'. But it would be good if you could make these headings (for exmaple, RESEARCH > Landscape> Insights > Survey'. The divider helps but still leaves you doing things like making an 'Archive' page with everything just dumped onto it, where it would be really good to have an 'Archive' heading, and then whatever pages you’re archiving underneath (for example).I’m also aware that many/most designers hack their own headings together by adding a page and giving it a heading name, but these are still actual pages and add a bit more confusion for other people using the file, and reduce consistency.Please? Not a huge amount of effort but massive value I reckon!

When I create an instance swap property I have the ability to add preferred values. However I’ve arranged my components (icons) into multiple subfolders. And to my dismay, selecting the top-level folder does not automatically also select subfolders. So now I have to click into each subfolder in order to select its contents. It feels like I’m being punished for being organized. Request: Please enable the selection of subfolders from the parent folder level (without having to click into it first). Please make the default behavior such that selecting a parent folder also selects all the subfolders and all the contents within it and any other nested subsubfolders and their contents, etc.

I have been designing for set-top boxes for several years now. And it is very convenient to do it through the transmission of the screen to the TV. But, there is no official support for Figma Mirror for TV sets. Many times I wrote to support and asked, but I always got the answer that there is no support. The most interesting thing is that Figma Mirror works perfectly on Nvidia Shield or Google Chrome (last generation) set-top boxes. You only need to put the app through aptoide. But with each time figma mirror refines the functionality for the phone, which severely degrades the functionality in TVs. For example, last year, after another update, the Remote Control for prototyping stopped working on the TV. It was very convenient to make a prototype, connect the buttons on the remote, and control the app. It felt like you were really using an out-of-the-box app. But it doesn’t work anymore. The second example happened with the last update. There was onboarding, w

Is there any plan to be able to create the gradient itself as a variable? For example, if I wanted some themes to have a solid background variable but others to have a gradient?

Since a couple of weeks Figma Buzz is auto-naming the frames it creates when BULK CREATEing. It simply adds 10 (or something) characters from each CSV-Tag and pastes them in.Please add the possibility to deactivate this feature. It messes with our current workflow and forces us to add additional steps. Would also be nice to be able to fine tune this to our needs (i.e. choose what tags should be used)Also: there seems to be no documentation in terms of release-notes for this.

As I have begun to use Figma Make, I have found that a designer is not the best typer and often makes mistakes in typing. Typing also takes so long to do and you want to speed up your time in Figma Make to go even faster. Imagine I can tap a Mic icon and input my prompt with VOICE. It would be so much faster and more accurate. Then hit the SEND button.You would see your text being inputed to the text field as you speak. You would need a way to stop or pause the voice to text.

When overriding a single element inside a slot in a component instance, Figma marks the entire slot as overridden. As a result, updates made to the main component no longer propagate to any elements inside that slot — even if only one element in the slot was actually changed. Expected behaviorOnly the modified element should be treated as overridden.All other elements inside the slot should remain linked to the main component and continue to receive updates.

I’d like to request visibility into where teammates are working inside Figma Variables.In Figma files, collaboration is already very clear: when someone else is in the same file, their avatar appears, and when they select a frame or layer, that object gets a colored outline. This makes it easy to understand where people are working and helps prevent accidental overlap.I would love to see a similar collaboration model for Variables. For example, when a teammate is editing or viewing a shared variable collection, their avatar could appear next to the relevant collection, mode, group, or individual variable. If they are actively editing a value, that row or cell could show a colored outline or presence indicator, similar to selected frames on the canvas.I’ve attached a sketch to illustrate the idea. Hope this can make it onto the backlog. It feels like a relatively simple addition that would make d

Implement integration with Intune so that organizations mandated to use intune to allow for mobile usage. 

When creating a AI report, and when I go to the AI credits screen and select the one of the date range options The CSV file comes the same usage period start / end date. How can I pull and create a trend report when the dates are the same for every report. 

A tool like Figjam would benefit so much from an Auto Layout feature. As a user, so often i’ll just duplicate a shape, which will often follow a horizontal or vertical flow. It makes sense that this would only be possible in Sections. At very least, you could have it as a Auto Layout “Lite”. You click on the Section, and you can choose the flow to be → or ↓ for new children in the parent section right? Duplicating a child in a section just places it over the previous shape, literally no one wants that. C’mon, let’s make this happen 😉

I’m used to presenting in Google Slides where there is a timer next to the notes. I’d love this feature in Slides so I know how long my presentation takes when I practice.

I’m new to prototyping with variables, and I’m finding the learning curve is pretty steep 😅 I’m trying to build my own variable troubleshooter in my prototype that displays the current value for each variable, to help me see if the issues I’m running into are due to my failing to SET a variable, vs failing to properly DISPLAY a variable. But now I find myself troubleshooting my troubleshooter… 😭 Place forehead on desk, repeat rapidly It would be amazing if there was something in the native Figma UI for the prototype that would display the current value for each variable. Then as I interact with the prototype, I can see whether those variables are changing properly or not. It would really help narrow down the culprit for my prototype bugs. For example, when previewing a prototype in Axure, they have a Console panel that looks like this: