Suggest a Feature

To reduce component weight, my design system team has been exploring using variable modes to toggle between different “variants” of a component, rather than just using variants. The benefit of this is that for these “style” specific properties, where just styles are changed like fill and stroke, using modes significantly reduces the weight of a component in the system. In this example I use a Badge component, and variables to change between the colors of the badge.However, my component code still has a “color” prop. Because I don’t have a color prop on my Figma component, but rather a “BadgeColor” mode that controls this property, is there a way in which CodeConnect can still map this to the correct code property? Currently it doesn’t seem like CodeConnect can read anything that is not a property. Realistically all I need is the CodeConnect to be able to read the string value of the mode, and map that to the actual code prop.

I was writing an interaction annotation for a screen that has the same pop ups as other screen so wanted to tell our devs that they can see the pop ups in this other section and redirect them back and forward to the pop ups.

I got the issue that I could not extend the column span of a layer if it stands at the end of row in Grid.I understand that a layer’s colspan cannot exceed the maximum number of cols, but it should have been automatically wrapped to the next line when the colspan number is still valid.Can you help to investigate this? I have found a workaround (at the end of each video), but it is time-consuming.

When exporting variant names, the file name becomes a combination of all the variant properties. There is no way to control the variant export name, which is especially difficult for developer hand-off. In this example, I have a back icon variant group (Named “Back”) containing both an Apple and an Android variant of the back icon. If I then go to export the Apple variant as an SVG, The variant export name then defaults to “OS Type=Apple.svg” It would be even worse if I had multiple properties. For example, having two more properties could result in a variant name export as “OS Type=Apple, Direction=Left, Style=Line.svg” This is a very poor naming convention, especially for icons. What I would like to have is the ability to control the name given to each variant export. In the above example, I would like the Apple icon to export as the name “back.ios.svg” and the Android icon to export as “back.android.svg”. This way, our developers can export assets as needed directly from Figma wi

Hello!I was going through our team files today, and organizing some that we shared with other vendors. I realized for one of the projects, we needed a ‘draft’ page for our team to ideate and brainstorm there, but didn’t want the vendor to actually see the WIP.I was wondering why isn’t there a page-level permission for viewers? This way I can hide / lock the ‘playground’ or draft page within a file from non-designers!

In design mode the layers sidebar just shows all information and allows for fluid horizontal and vertical scrolling.In dev mode, it all of a sudden just cuts off everything above a certain width.

Hi there! I would like to know what Figma is going to do to comply with the US sanctions against russia regarding design software coming into effect in September. I haven’t seen any new updates on the topic. It seems like the old approach described here will be in violation of the new sanctions. For example, Notion has already communicated here that to comply with the US sanctions they will restrict access to their platform for all users in russia. Please vote for this topic to draw Figma’s attention to this serious matter.

Hello Figma Team,First of all, thank you for building Motion. It has made it much easier for designers to create engaging animations directly inside Figma.One feature that would significantly improve Motion is a built-in Typewriter (Auto Typing) text animation.Currently, designers who want text to appear letter by letter have to create complicated workarounds by splitting text into individual layers or manually animating masks and keyframes. This becomes especially time-consuming for longer paragraphs or multiple text elements.I propose adding a native Typewriter animation with customizable controls such as:Character-by-character typing Word-by-word typing Adjustable typing speed Start delay Blinking cursor (optional) Cursor styles (line, block, underline) Delete/backspace animation Pause after completing a sentence Support for multiline paragraphs Compatibility with existing Motion keyframes and easingThis feature would greatly benefit designers creating:Product launch videos Social m

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 often have a need to annotate designs from different perspectives, like..Accessibility Analytics tracking Localization...and the stakeholders have a need to easily find and check the annotations related to their responsibilities.Currently in Figma I can create color-coded categories for annotations and use them to tag layouts, which is great. I can even filter them to some extent.What makes the filtering almost unusable for me is that only ‘All categories’ or a single category can be chosen. ‘All categories’ is too much: layouts will get flooded with annotations. Unfortunately just selecting one (like ‘Tracking’ in the image below) Figma still shows all the rest as these reduced mode red things (see lower image). What I’m getting at is that there should be a way to easily toggle any combination of categories visible/hidden. It’s weird that in the Filter by -list you can’t choose to display say “Accessibility” and “Interaction” and the rest would be hidden. Showing all those reduced m

Today: As an agency, we’re frequently starting new projects for new clients. We’ve evolved a set of best practices for Figma file organization, per-client design systems, etc. These best practices have been captured in a Starter Project project in Figma. However, to use this Starter Project each designer must duplicate each file in the Starter Project individually and then move them over into a new project. Idea: We’d love to see Figma support duplicating projects in addition to the existing file duplication functionality. This would be a small but noticeable improvement in efficiency for spinning up new client projects.

Dear Figma TeamThanks for all the efforts and products you are producing for the wolrd it is really inspiring us all. Since Figma products have a lot of features and it is hard for anyone to know about all of them, I suggest to build an AI tool where I ask it on how to use a feature and it will produce a video with voice on how to use this feature and it can suggest more videos on youtube if I need more explanation or deep dive.

Is it possible to view a user’s drafts as an Enterprise admin or a Team admin?As an admin I really should be able to view all files that have been created, but it seems that user’s drafts are still private even after the update.

It would be really nice if I could just search the version history to find specific saves, instead of having to scroll through the entire list. This becomes especially annoying if I have a lot of versions saved and am searching for a very old one. Search / Filters that would be nice: text search date filter creator filter

In their current state, comments try to accommodate multiple use cases into a single system: general note-taking, questions to ask stakeholders, functionality/purpose annotations, feedback, prototype tour points, etc. When all these use cases pile up in a single page, it could easily start to reach over 100 individual comments and makes it difficult to distinguish between them. I’m proposing expanding the functionality of the comments feature to allow for the most common use cases to be different comment types. Invision does a great job of this by changing the color of the pin when a certain comment type is selected. This allows users to quickly identify the most relevant comments to them and ignore the rest. (From Invision) What would make it even better is if the visibility of types of comments could be filterable from the right toolbar. When the comment tool is active, editors could filter down which types of comments they would like to see. They could also determine if a comment t

The new sidebar takes up valuable horizontal space, only to display a few links that can be moved elsewhere. How can we hide this? Or collapse it into the Figma button, instead of using 100 pixels just for 6 links, 4 of them who already existed somewhere else before anyway?  

Problem: There is currently no Plugin API to enumerate all connected/enabled libraries of a file, nor to list the styles (paint, text, effect) published by a connected library. The only library discovery surface is teamLibrary.getAvailableLibraryVariableCollectionsAsync(), which returns variable collections but nothing about styles.Current workarounds and why they fail: Scanning the document for remote style IDs — You can walk every node across all pages, collect fillStyleId, strokeStyleId, textStyleId, effectStyleId, check style.remote, and group by the file key embedded in the style ID (S:<fileKey>,…). This is extremely slow on large files (thousands of nodes across many pages), incomplete (only finds styles actually in use, not the full library), and fragile (relies on internal ID format for grouping). getAvailableLibraryVariableCollectionsAsync() — Returns LibraryVariableCollection[] with libraryName, which lets you discover library names and their variable collections. But

Similar functionality to AE, and also Figma’s native Sweep functionality with Ellipses, the ability to trim any path’s Start and/or End points would allow for more optimized design and prototyping. Some examples: Elegant design/prototyping of custom bar and line charts as well as interactive sliders (RN my adjustable horizontal charts and sliders components are leveraging AutoLayout right padding to adjust a stroke set to Fill) More advanced/custom loader animations Easily make drawn path animations

A great feature to have is text styles not breaking when a designer is using Cmd + B to bold a word or phrase. Currently it unlinks the text style and applies the bold to the underlying font. It would be great if there was a feature where when I use Cmd + B, it swaps to that text style in the library (where the style already exists) and updates in the property panel as well.

I find managing template colors really difficult in Slides. I can’t easily organize, re-order, or rename them. I’ve found some ways to hack it but it feels really convoluted trying to provide color options in the templates I’m making. I think Slides is doing a really great job on most fronts and I love the product, but I find myself just using colors from other libraries because managing them within Slides is so confusing.

Hi Figma team and community,This is related to a similar issue reported here:MCP rate limit not acknowledging subscription I'd like to suggest an improvement to the error messaging around API and MCP access for Dev seat users.Current situation:When a Dev seat user tries to access a Figma project via the API or MCP without having edit permission granted at the project level, they receive this error:> "You've reached the Figma MCP tool call limit for your View seat on the Professional plan. Upgrade your seat or plan for more tool calls."This is misleading in two ways:1. The user already has a Dev seat — not a View seat.2. Upgrading the plan is not the fix. The actual issue is that edit permission hasn't been granted for that specific project. There is also a conceptual confusion worth addressing: Dev seat users do not have edit access to projects by design, which makes it counterintuitive that they need to be granted edit permission by the project owner in order for API/MCP access to

Prototyping a circle progress ring based on variable set would allow for significantly simpler and native prototyping and managment. RN I have a progress ring component with 25+ variants progressing based on a Day variable that then does a Change To to transition to the right one, but this is cumbersome to maintain as each variant requires all the conditional logic to possibly switch to any other given variant. If I could apply a variable to the Sweep then I could then progress the Sweep variable in relation to the Day variable on just 1 Ellipse, and manage only 1 set of conditionals applied to it.

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

As teams and design systems scale, finding the right Figma file becomes a major bottleneck. Many of us manage hundreds of cross-functional projects, and the current dashboard limits our ability to organize and locate our work efficiently.To make it easy to see what needs to change, here is a breakdown of the three major file management limitations we face daily, our frustrating workarounds, and the proposed solutions: Feature Request The Figma Limitation The Frustrating Workaround The Proposed Solution 1. Native, Searchable Tags No way to categorize or add custom metadata to Figma files. Cramming categories, client names, and Jira codes into the title, cluttering the dashboard. Introduce a native tagging system to filter files by status, team, or tracking codes. 2. Quoted Search Terms Search splits words by hyphens (e.g., PROJECT-123 becomes PROJECT and 123). Quotes are ignored. Sifting through dozens of irrelevant search results that share common prefixes or nu