Suggest a Feature

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

Hi Figma Support,We are a SaaS Security Posture Management (SSPM) vendor that integrates with Figma to help our mutual enterprise customers gain visibility into their Figma environment.Current situation:We're integrating with Figma's SCIM API and need to clarify the behavior of GET /scim/v2/{org_id}/Users.Two questions: If an organization uses SCIM for provisioning, can admins still create/invite users directly in Figma (outside of SCIM)? If yes — does GET /scim/v2/{org_id}/Users return all organization members, or only those that were provisioned through SCIM? We need a complete user directory for security posture management. If SCIM only returns SCIM-provisioned users, is there any other API endpoint that returns all org members?Thanks!

I have a numeric input field as a component, and its value is set as a text property called value. Pretty simple stuff, right?For prototyping reasons, I want to bind this field's value to a number variable, so I can add/subtract to this value when I press a button somewhere else on the screen. Also pretty simple stuff, right? Well, apparently not. Turns out I just found out that we can't bind number variables to text properties for whatever reason — they don't even show on search results. And since there's no component property of type number, this simple prototyping scenario I'm trying to achieve appears to be impossible. Meanwhile, if I simply remove the value property from my component, then select the plain text layer with the value and try to bind it to my

When working with more complex auto-layouts in Figma, I find myself accidentally changing frames/instances from Fill to Fixed or Hug by double clicking on the edge. In some cases I don’t catch myself and only discover later that parts of a prototype are not responsive. Is there a way to disable this or change the behavior to require a key modifier or something? 

I want to be able to lock a component on the page for everyone except myself. 

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

Hi Figma Community!  I couldn’t find anyone else having this problem, so it’s probably “just a me thing.”  Whenever I duplicate a style, I always edit the ‘old’ version by accident, thus throwing off the entire design system. Any chance that the powers that be could tack on the text “copy” or “duplicate” ?  But it would have to disappear when edited.  Thanks for reading! 

Currently, in Figma, smart animate only works on opacity, color fill, stroke, position, width&height. The options at your disposal when making an interactive prototype are pretty limited. It would come in handy if Figma can expand the supported animatable properties to include: Radius, Effects (shadow spread), VectorNetwork, Polygon Ratio, Ellipse Sweep, Dash, etc.

Smart Animate needs some TLC from the Figma team.I am lucky enough to work in an industry that is not averse to using more interesting animation in our UI, however I can’t create proper examples of interactions because of how Smart Animate works.Animation is directly tied to prototyping flows and that creates issues as animations are not ‘pages’ and exist outside of a page-to-page framework. Smart animating between 2 frames inherently means that all animations start and end at the same time, of course that is exactly how it supposed to work but this makes certain types of animations completely inaccessible - such as cascading items (multiple objects loading in on slight delays). Nested Animations can’t trigger on page load don’t work and they take forever to make so there is no real work around for this. There have been a few posts on the subject, but I believ

It would be really helpful to be able to use a variable to set a Type Style’s Letter Case (under the Type Settings meatball menu). It could be a String Variable, and the options would be “As entered”, “Uppercase”, “Lowercase”, “Title case”, and “Small caps”. I personally use modes to switch between different brands, and some brand styles require uppercase while others don’t allow it. This suggestion may be a small feature in the grand scheme, but I wonder if others would also find it useful.

I love Figma, I’ve finally been able to get rid of Illustator.However, Illustrator had a very useful function when working with a large artboard or a large number of artboards. I could zoom out to view the project, select any object(s) I was interested in, and then zoom+ in to or zoom-to-fit (focus) the selected objects.Currently, the zoom in Figma is always focused on the centre of the screen, meaning I need to reposition the viewing window as/before I zoom in to work.  

Hi,I’d love to suggest improving the experience of working with Color Variables in Design Mode.Right now, copying a variable name (color token) takes several steps and interrupts the workflow. In contrast, Dev Mode has a really smooth pattern — you can simply click on a variable color line and instantly copy its name.It would be great to bring the same interaction to Design Mode:One-click to copy the variable name One-click to copy the hex valueOur team recently migrated from Color Styles to Color Variables, and this has become a noticeable pain point in day-to-day work. We often need to quickly copy token names (for documentation, communication with developers, etc.), and the current flow feels slow and cumbersome.This small improvement would significantly speed up workflows and make wor

I work in a large design team (50 designers) in a fast-growing company. The product is complex and has many different flows and variations. I often find myself wanting to find a specific screen in Figma from a specific part of the product. If we had a great index internally that we kept very well groomed, this wouldn’t be a challenge. But it is not the case. Most of the time, I really on asking in Slack if anyone knows where I can find a recent-ish version of this or this in Figma, wait, and 50% of the time another designer finds something. What if we could do reverse image search in Figma like we do in Google? I screenshot a part of my product I use it the reverse search in Figma Figma shows me the files, and where in the files, that have designs that match very closely my screenshot I can grab my screen and start designing!

I have a button which is created in the library file in the way it has hover state while hovering:The same button, according to the WCAG AA requirements must have a tooltip on hover (and when it’s focused while using keyboard navigation but it’s not the case here) https://www.w3.org/WAI/WCAG22/Understanding/labels-or-instructionsThe current interaction mechanism doesn’t allow to display a tooltip on hover from the project level as the hover variant interaction is already reserved on the library level. The screenshot from the project: Theoretically I can c

My suggestions is to allow users to include annotations and / or measurements  when they export images. Seems that we can’t currently do thisThe user benefits –allows users to share images with annotations and measurements when creating images to be shared wither wider stakeholders and creating documentation for other platforms. If we can’t export annotations and measurements, then for those instances requiring annotations in an export as an image, users won’t use the annotations feature, and revert to creating “Notes” manuallyHope this makes sense

Often I’m adding autolayout around a frame/component/element, and the default vertical and horizontal padding is 10px. As well, the gap applied is 10px. It would be amazing to set the default padding and gap to auto-layout elements. This would help with keeping your files clean, but also, to ensure that redundant CSS properties are not added to dev mode output. Clearing and resetting these properties takes time and often the gap is not cleared due to the property not having an affect on single children. Thanks!

Please introduce a more prominent visual indicator for active branches in the main file.Currently, the branch indicator appears as a small footnote near the page title, which is easy to overlook. Because there are multiple ways to create a new branch, designers may miss the moment when an active branch is present and unintentionally continue working on elements already affected by it.This can lead to merge conflicts and significant loss of time, as changes may need to be reverted and redone. A clearer and more visible indicator would help prevent these issues and improve collaboration within teams using Figma.

Would love to see metadata added to top-level items on the canvas or in the layers panel, and stored somewhere discreetly. For example, it’d be really advantageous for large teams—and editors specifically—to have the ability to view the timestamp/authoring details of a specific section or frame (e.g., when it was created, who created it, when it was last modified, etc.).

Pretty simple ask: I want to move a page from one Figma to another. I don’t see a way to do it. Select All + Cut + Paste is not a good solution as I might have locked objects that don’t come with the copy and there might be properties set on the page (background color, etc.) that I might lose.

I frequently share notes on designs with a group of developers without knowing which one will work on what I’ve designed. I’d love to be able to tag several in a comment via a “group” I’ve created within my team (eg- “@FrontendDevs”) How are others handling this?

Background: I am a developer, and I use Figma exclusively in Dev Mode via the web interface. I don’t have (nor do I want) any edit access to the designs I’m implementing. That’s for the designers. When the Measure tool appeared (the ruler icon on the upper left toolbar), I latched onto it very quickly. It greatly improved my speed of accurately implementing a design. There are certainly other ways to measure things in Figma, but they are all transient. The best part of the new tool was that I could quickly measure many different things and have all the measurements persist so that I could then just refer to them during development. It was a simple yet well-conceived tool.

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.

Hi Figma team,My team and I have been experimenting with slots recently. I'd like to propose a feature enhancement: when a component with properties is added via a slot, those properties should be accessible directly from the main component.Ideally, these nested properties would surface automatically, eliminating the need to click deep into the component hierarchy to make edits.

A few years ago there was a fix - The icon on the instance inherit color override, imposed by main component, when swaping icon or changing variant. Great!but… Problem If I modify the icon color on the main component - change color style or manually pick new one, doesn’t matter. The instance with swapped icon doesn’t notice the change! Steps to reproduce:Place an instance Swap the icon on instance Change variant's (main component) icon color Instance's icon color will remain not updatedNote: Of course, all layers properly named to keep the naming integrity. The example:

Hey everyone I wanted to share my workflow for designing SEO-optimized landing pages in Figma, something I’ve been refining while working with clients here in Nepal.A lot of designers focus purely on visuals, but I’ve learned that small design decisions can directly impact rankings, page speed, and conversions.Here’s a simplified version of my process:1. Start with search intent (not design)Before opening Figma, I map out: Target keywords User intent (what they actually want) Competitor page structure This helps me design pages that match what users are searching for, not just what looks good.2. Structure comes firstInside Figma, I focus on layout hierarchy: Clear H1 section (above the fold) Logical content flow (H2, H3 sections) Scannable layout (short section