Suggest a Feature

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

When using a grid based system, it would be useful to bump (move) rulers by a set amount. For example if I am designing a UI and I am using a 8px system. It would be useful if I could click on a ruler, press a button (‘b’) and move that ruler by my 8px. You could have a setting called “Grid System px” where I could set the bump amount. That way when I lay out elements by using the rulers I can quickly move them around based on my grid system.

Hi Figma team,I’d love the ability to open multiple selected files at the same time.Currently, it’s possible to select multiple files and perform bulk actions such as Duplicate, Move, or Delete, but there is no option to Open all selected files.This would be especially useful when working on large projects or design systems where multiple files need to be reviewed, compared, or updated during the same work session.Suggested improvementsAdd an Open action to the bulk actions menu. Open each selected file in a separate tab or window. Support common shortcuts such as ⌘+Enter (macOS) or Ctrl+Enter (Windows) to open all selected files.EnvironmentmacOS Figma Desktop AppThis feature would be especially valuable for designers reviewing multiple files every day, making file management much more efficient.Thank you!

Hi Figma team,I’d like Figma to remember my preferred file sorting option.Every time I open the Figma Desktop App, the file browser resets to Last modified, even though I always use Alphabetical.For designers working with large projects and design systems, alphabetical sorting is essential. Having to manually switch the sorting back to Alphabetical every time creates unnecessary friction and slows down navigation.Suggested improvements:Remember the selected file sorting option across sessions. Sync this preference across devices (optional). Or provide a Default file sorting setting in Preferences.Environment:macOS Figma Desktop AppThis is a small UX improvement, but it would noticeably improve everyday navigation and productivity for users managing many design files.Thank you!

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)

When I open my Figma project files, they are always sorted by “Last modified” by default. I can manually change the sorting to Alphabetical order using the dropdown in the top-right corner, but after refreshing the page or reopening Figma, the sorting resets back to Last modified. I’ve seen other people posting the same issue. I want to push this topic forward with sharing it again. Is it possible to fix it please dear Figma? :)

So lately I’ve been designing retro mockups and they use pixel fonts. On most design tools like GIMP, Pixel.net, and Photoshop, there is an option to use Aliasing (Disable Anti-Aliasing) for text, making it pixelated (no blurring caused by anti-aliasing) and unfortunately Figma does not have this, which makes me search for Bitmap fonts that only work on specific sizes to accomplish pixel fonts. So I wanted to ask for an option to have Aliased fonts without Anti-Aliasing, to force them be pixelated.

Hi, the checkbox “Show in exports” in the “Fill” section is not controllable yet from the plugin API. It would be great if this can be exposed via plugin API so it can be automated in plugins. This would also allow Figma Assistant to use it, it currently can’t. My real world use case would be in automating tasks surrounding icon libraries. Thank you! 

Hi everyone! Maybe I’m missing something, but is there a way to copy the currently selected padding token, similar to how interactions can be copied?I’d like to copy a token that is already applied to one component variant and then paste it onto another variant—or any other object with a compatible property—that currently has a regular numeric value or no token assigned.At the moment, I can’t find a way to copy the selected token while the token list is open. Is this already possible somehow?  

 Hello! Congrats on your big update. Btw while I really enjoyed trying the Figma agent to build my own Plugin tool, it was frustrating to know that I have no way to share it with the team. I guess that it's because it's beta version? If you don't have a plan to make it sharable in a foreseeable future, i would prefer building plugin externally for our team rather than these tools. Thanks for reading! 

As AI coding becomes part of the design-to-code workflow, I think there is a new type of information that belongs in Figma: Implementation annotations. Today, annotations can only be added by people with edit access to the design file.This works well for design explanations, but not for implementation guidance. Imagine this workflow:A designer finishes the UI.Later, a developer reviews the design before implementation and notices several places where additional implementation context would help an AI coding agent generate much better code. For example:This Frame should be implemented as a scrollable list. This component should use virtualization. This area should stay fixed while the content scrolls. This value comes from the current device model. This text should truncate after two lines. This image should preserve its aspect ratio. This section should use the shared DeviceCard component. This layout should become two columns on larger screens. None of these change the visual design.T

I’ve created a detailed set of design guidelines for my product, covering layout structure, spacing, naming conventions, responsive behavior, component usage, interaction patterns, and platform-specific requirements.However, I haven’t found a way to make these instructions part of the Figma Design Agent’s persistent default context.Custom Skills are helpful because they can package reusable instructions and remain available across files. However, they still need to be explicitly invoked in each conversation. Libraries and attached guideline files also need to be added as context manually, while Figma Make’s guidelines.md is scoped to an individual Make file.I’d love to see a persistent context system for the Figma Design Agent, with multiple levels such as:Personal context — preferences and conventions applied across all of my files Team or workspace context — shared standards automatically followed by everyone Project or file context — product-specific guidelines applied to every agen

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

Hi, I stumbled across this issue as I wasn’t able to read the comments of the master file in the branch. I always need to switch back and forth to incorporate feedback from reviewers and this is very annoying.

I love the new “Ready for Dev” status option on Sections, but would love to add and use other statuses relevant to my process. For example, it’d be great to have a “Ready for Design Review” and “Ready for PM Review” statuses so that everyone knows where things are at.

Hello Figma! I can not change the direction of the Autolayout on the instances of a component. I can not understand why such a great feature is disabled on the instances and why not allow us to overwrite it? There are so many incidents that I would have wished to be able to change the direction of the Autolayout in the instances of the component but right now I have to create multiple variants. 😦

We have a Design System with parent components composed of nested instances. Both parent components and nested instances are in the file “A”. To avoid having thousands of components available within the Assets when publishing the library, the nested instances are hidden with “.” at the beginning of their names. The problem: When using the component library from file “A” in file “B”, everything works fine. The issue arises when a nested instance from file “A” requires an update. Firstly, it does not allow me to publish the nested instance update without removing the “.” from its name, and I also cannot publish the parent component containing the updated nested instance. If somehow I manage to publish the parent component, file B will prompt me to update it, but the updated nested instance does not receive the changes made. Is this a bug? Or what is the correct way to work, update, and publish nested instances so that they always receive their updates without cluttering the Assets librar

We’re working on a larger Component library that includes non-published components (components with the prefix _ or .) as base components in order to simplify large, complex components. We intended – in some specific cases – to offer regular components as templates, that a designer would then have to detach and work with a bunch of base components to build the desired design. What we have come to realize with this approach, however, is that these non-published components don’t receive updates from the library when they are updated in the main library. Is this intended behaviour? We basically have the option to simply publish these base components as regular components, but that of course would mean cluttering up the assets overview with a bunch of modular components.

I have a problem where I have noticed that when a designer detaches a design and it is using hidden components within it, that it ends up decoupled from the library… I was always under the impression that since it is a component in the library, that if it was detached it would still be able to receive updates via these hidden components… I have realized this is not the case.I think a new feature request should be made to allow hiding the components from the asset panel view (which is what people actually want from the hiding feature) without losing the link to the library.If the feature intent is to not publish these components at all, I am not understanding why when we detach, why those hidden components don’t detach as well? This is what gave me the false notion that they would still be able to receive updates, since they are still an attached component -- but attached to the wind it seems...Design system maintainers are not looking to not fully publish these components, but instead

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.

It would be EXTREMELY useful to be able to pin images using typical CSS background-position propertiese.g. background-position: left centere.g. background-position: top rightWe have multiple components in our Design System library that would benefit from this. Currently, we cannot communicate this with developers without annotating it on-page.It would:allow the designer to be able to see it in-action in an auto-layout/responsive manner give the developer the intention of the design inside the code inspector. allow the designer to not have to design provide a cut image from another program or an image specific frame within the file and communicate which image to export or to use for development.This gentleman wrote about this exact use case and provided the screenshots of how each should work.