Suggest a Feature

Hi, We are using Devin in our Org widely and integration with Figma for Read and Write operations are unavailable at this moment, when can we expect Figma MCP for Devin? Thx 

Organization would be immensely helpful if we could create folders for our drafts. I want to be able to organize my drafts into different categories (such as UI kits, Ideas, Wireframe kits, iOS, Android, etc…) so I can find files easily. Right now, the drafts page is a huge jumbled mess and I can’t create Team pages for everything. Maybe something as simple as being able to add ‘tags’ to each file, similar to Zeplin.

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.

Hey folks! 👋 I was using Figma’s Swap Library feature recently and came across a little hiccup that I think could use some improvement. You know how it works: when you swap libraries, Figma tries to match styles between the old and new library based on the token names, right? But… when there’s a name change or a slight difference in naming conventions, it just says “None found,” and that’s it. 😅 You’re left with elements still tied to the old library, which can be a bit frustrating, especially when you’ve spent time updating your naming structure to make things more organized or meaningful. What’s the Ask? Can we get

I would love to be able to create one prototype across the pages in a file that resembles an actual website. This would be ideal for bigger projects and would be easier to maintain as well. We can connect the component libraries across all the pages anyways. A way to connect the prototype would be great in my opinion and that will give Figma a big leg up on other platforms. What do you guys think?

With "Text-wrap: balance" headlines could be made more readable and visually appealing.Here’s how it could look: 

Hello, it would be nice to have the option to insert floating components inside text (like Emojis). Use case would be for signs or infos in complex dashboards. Its a hustle to do this now manually and also set kind of boundingboxes to sync different heighs of text and component. Regards

Stamps currently display the name of the user who placed them, but not when they were added. It would be very useful to also show the date and time for each stamp. Our team uses stamps to mark completed items. Being able to see exactly when a stamp was placed would help us better understand progress over time, track when decisions were made, and improve async collaboration. Suggested improvement:Show the date and time together with the user name on hover. This would make stamps significantly more informative, especially for teams using FigJam for workflow tracking and status updates.

So this boggles me. Why can’t I change (override) the opacity of a referenced color-variable, without having to detach it? To me a color and an opacity value are two different things. So if I want an opacity on my referenced color e.g. “Blue-950” I have to detach it and change the value to my liking, now it is not referenced to the variable collection anymore. A workaround is to add that “Blue-950” with the desired opacity in the variable collection and then reference that new “Blue-950-50-percent”. It is so annoying that you can’t change opacity on the fly without loosing reference!!!

It would be great to be able to merge two variables into one, so anywhere where either variable is referenced, the references will now point to the single, merged variable.

When I write create long paragraphs with text tool on the Figma I get the unnecessary spaces on edges of the paragraph like below. But I think if there a hyphenation feature (like Adobe Photoshop) it could add dashes automatically on the texts and fix this issue.

Request: Through the Figma MCP, access contents of comments made in Figma Design file.Reason: Can provide context for designs, review bugs, etc.Current response from OpenAI Codex with direct link to comment:No, not the comment itself.What I can see from that link is the node it points to:file: XXXXXXnode: XXXXXXscreen: /sign-up-2 (iOS)That screen contains:nav title Sign UpEmail and Password inputsSign Up primary CTAContinue with AppleContinue with Googledivider OrAlready have an account? Sign inbottom legal linksBut I still cannot read the actual Figma comment thread or the #XXXXXX anchor content from this session.If you want, paste the comment text here and I can map it to this exact screen and tell you what change it implies. 

The provided palette for text color is not accessible. Most colors do provide sufficient contrast against the white canvas.  I understand the second row of colors would be useful when the text is placed on top of color/darker surfaces, but the colors on the first row should at least meet AA over the white background of the canvas. Otherwise one is forced to always pick a custom color if the background is white, or from the few that provide the most contrast.

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.

I've been using the Figma MCP server with Claude Code to build a design-to-code workflow, and I've hit what feels like a significant gap in the `generate_figma_design` (html-to-design) capture tool. I'd love to see this addressed and wanted to share the use case in detail. The current behaviorWhen generate_figma_design captures a rendered web page, it converts everything to raw Figma geometry — frames, rectangles, and text nodes. Even if the page is built entirely from your published design system components (Button, Tag, Checkbox, etc.), and even if those components have Code Connect mappings configured, the capture output has no awareness of them. You get a pixel-faithful snapshot, but it's "dead" — no component instances, no variable bindings, no variant properties. The gap this createsCode Connect already establishes a bidirectional relationship between Figma components and code componen

Hey there! I was also wondering if it is somehow possible to include also the layer of variant controls to be exposed or hid! I often have cases where I need to nest base components e.g. an icon wrapper providing me with the ability to select certain sizes, or color overrides and boolean props of an icon. I am now able to expose all of those or none, but I can’t restrict the users to only be able to select just some of those. What do you think about it?

Request: More access through the Figma MCP when inspecting the node in `dev` mode.Reason: I’d assume (correct me if wrong) this would decrease token usage because of the extra coding data (e.g., setting css styles to `Android`) that Figma already has available.Open to being corrected by the Figma team!

Hi Figma developers! It turns out that exporting Figma fonts in JSON format provides the result that looks smth like this: "style": { "fontFamily": "Quattrocento Sans", "fontPostScriptName": "QuattrocentoSans-BoldItalic", "fontSize": 72, "fontWeight": 700, "italic": true, "letterSpacing": 0, "lineHeightPercent": 100, "lineHeightPx": 84.375, "lineHeightUnit": "INTRINSIC_%", "textAlignHorizontal": "CENTER", "textAlignVertical": "CENTER" }, for a page like this:

Problem As a front-end programmer I don’t quite grasp the current concept of so called “Local Variables”. For starters, they’re not local, but global. And the thing with global vars is - they make a big mess, like always. For this reason any programming language considers global vars an anti-pattern. But currently, the only way to make a Figma component “stateful” is to keep its “state” in the global namespace. I use quotes for a reason: there is no real state at all, because in Figma there is no an entity like “state of a component”. This all makes flows unmaintainable and prevents us from transferring components between files and projects, because they get transferred without their “state”. So basically you can’t easily reuse components logic. It also doesn’t provide any level of isolation. For example, if I have more than one instance of the same component, how would I distinguish their variables/state

Hi folks! I’ve seen the posts regarding text overrides with nested interactive components but I’m seeing a similar issue with non-interactive components as well. In the example below, I’ve set my text layers to all use the same layer name and have the same hierarchy structure but if I swap one of the nested components it resets everything. Everything works perfectly if each atom component is used individually and not nested in another component though so I’m left 🤔. Any thoughts?

Mural’s tables auto adjust based on items within a cell. If you add another sticky note, the cell expands to accommodate the new sticky. Not having this in Figjam is killing me. 

It would be a big time saver to preserve the style and formatting of a text layer, when copying and pasting it from one file to another file. Right now the paste operation loses all formatting and I have to re-format the text all over again.

I browse various files in my org very often, and sometimes I’m in dev mode. This automatically subscribes me to notifications which is not what I want.I’d like to be able to set default preferences globally (like “subscribe by default: on/off”), similarly to how another topic states (which to my disappointment didn’t get any replies and was closed for some reason).Or at least the feature to ask me each time to confirm if I want to be subscribed, which obviously would be irritating, but not as irritating as receiving all those notifications and having to open the file to unsubscribe.Or at the very least, to be able to unsubscribe without having to open the file, either from emails or from desktop notifications.

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