Suggest a Feature

Right now it seems like the ‘default’ variant is set based on which variant is ‘upper leftmost’ in the variant container frame. Instead, I suggest decoupling arrangement from precedence, and using the property ordering functionality to determine the default variant. The default variant should simply be the one with the first value for each property, regardless of where it’s placed in the variant frame. This would allow teams to set defaults directly from the properties panel, without having to move components around. See this thread for some more context: How to set defaults / precedence of variants with multiple properties?

Dear Figma,I wanted to bring to your attention that we are in the 21st century, and there are devices specifically designed for designers, such as tablets. I own an iPad, which has an amazing display and can be used with a keyboard and mouse. However, I currently use it only for viewing my designs because Figma, the professional tool I rely on, does not fully function on my iPad. This leaves me with a few options: sell my expensive iPad to buy a PC or laptop, which is less comfortable for me, wait for an iPad update from Figma before GTA VII, or use it solely for watching movies. I wanted to remind you that tablets exist for a reason, and it would be beneficial if Figma could support them more fully.

It would be highly beneficial if we could create Variables for Effects (Drop Shadows, Layer Blurs, etc.) just like we do for Colors and Numbers. Currently, handling different shadow intensities for Light and Dark modes is tedious because we have to switch Styles manually.By adding this feature, switching between Light and Dark modes would become much more seamless and effortless, as shadows could automatically adapt to the active mode.

 I’m building a component library for Figma Slides and ran into some issues:Users can use my published variables / styles inside the components, but they can’t use those same styles directly when creating content themselves in Slides.For example, I built a dark/light mode switch with variable colors. Works great in the components. But if someone adds a new text box, they can’t pick those colors from the library.Would be really useful if published library styles/variables were available directly in Slides, so native content can stay aligned with the rest.

ContextWith the Figma MCP server's `get_design_context` tool becoming a key part of design-to-code workflows, there's a friction point around how variable group separators are handled in CSS output.Figma uses `/` to create variable groups (e.g., `blue/600` creates a `blue` folder containing `600`). This is great for organizing variables in the Figma UI. However, when the MCP generates code, the `/` is preserved literally in CSS custom property names: `--blue/600`.The ProblemIn Tailwind CSS — the default output framework for `get_design_context` — the `/` character is reserved as the opacity modifier delimiter:bg-blue-500/75  →  background-color: rgb(59 130 246 / 0.75)So when MCP output includes `bg-[var(--blue/600)]`, Tailwind's parser interprets `/600)]` as an opacity value, producing broken CSS.The MCP works around this by escaping slashes as `\/`, but JavaScript consumes the backslash in normal strings. This forces every token reference into a `String.raw` template literal:```jsx//

I’d like there to be a quick way to restart a figma make prototype preview. currently, I have it pasted in my Figjam for a design review meeting, and once i go through the interaction, theres no way to easily start from the beginner. 

Immediately sticking out for me is the absence of a “blur” interaction. This is necessary to simulate “focused” states in things like drop-downs and text inputs. Without this, my components get stuck in the focused state without an elegant solution for having them blur like they do on the web. My current workaround is to use the “mouse leave” action, but this is suboptimal. I imagine you could add a trigger called “Click Outside” or something similar. Besides this, the feature is a golden so far 🙂 You folks are killing it!

I really like Slots and the Duplicate features but I would love for a slot to duplicate the content when set to fill and the parent item is expanded.At our organization, OCLC.org, we just a lot of tables or in MUI’s case, DataGrids. Like a lot of datagrids.  To make a component that expands columns and rows when an frame is expanded isn’t available. I’ve been working on this with Slots and components in our design system but you still need to select each slot and pull the duplicate bar to expand it to shape. 

First off. Yes, we all love variables. Secondly, this may have been discussed before, but it might be worth repeating. Also, I’m a bit frustrated so I’m sorry if I gripe a bit. Components need to have their own instanced variables. It is so time consuming having to set up a brand new variable collection for every component that uses variables, in every file. The way my team and I thought we could use variables is to set up the basic variable structure for a component in our library, then be able to adjust the value of the component for each instance. This would have so many use cases, and would honestly make my life so much easier. The current reality is that, when we set up a variable collection in a library, we are stuck with those values for all eternity. No way to change them unless I wanted to make a new variable collection in the file I’m working in and map them to the library variables (which I don’t even know if you can do because Figma seems to arbitrarily not allow you to sel

Title: AI “Improve My Design” Button (Auto UI Optimization)Description:It would be incredibly useful to have a one-click AI feature that analyzes an existing frame or screen and suggests improvements to the design.For example: Improve spacing, alignment, and layout hierarchy Suggest better typography scaling Enhance visual consistency (colors, padding, components) Optimize accessibility and readability Offer alternative layout variations Right now, Figma AI helps generate new designs, but there’s no simple way to refactor or improve an existing design directly.This would work similarly to how developers use “refactor” tools in IDEs — but for UI/UX design.Use case:Designers often have rough drafts or mid-fidelity screens and want quick, intelligent suggestions to polish them without starting over.Why this matters: Speeds up iteration Helps newer designers learn best practices Improves overall design quality Makes Figma AI more practical in real workflows A simple “Improve

Similar to how you can add an image in a Figma comment, support to add a video

I am currently working on integrating a Figma Make prototype with Rudderstack, but I have found that Figma Make does not offer the option to create environmental variables. I would like to request that you consider adding support for environmental variables to Figma Make, similar to what Vercel or Netlify offer.This feature would greatly improve security and make it easier to configure applications.

I’d like there to be buttons that act as controls to jump to the first or last item on the page. In documents with lots of screens, this could be useful to avoid having to scroll up and down so much.I’d also like to be able to mark screens as main screens or flow starters (in the same way we currently mark a screen as ‘Ready to dev’) and navigate directly between them using ‘previous’ and ‘next’ controls.Is there already something like this?

As a user who does not want to create extra work for my UX team but wants to create workflows and up to date examples that persist I want to be able to“Copy as Linked” - Copy the item “Paste as Linked” - pasted item updates from copied item Replace as Linked” (Ctrl+Alt+Shift+R) Replaced Item updates from copied item So that My UX can use components the way they want and we can keep different pages up to date across figma boards by updating a screen that is the source of truth. 

We have found a lot of efficiency improvements with the JIRA and Confluence widgets within Figma Design. With incorporating more teams into the Figma ecosystem, I’ve found a lot of opportunities for building libraries and design systems and pulling in assets to Slides to build launch decks to share outwardly. We track a good amount of things through JIRA.Would LOVE Jira + Confluence widget support in Figma Slides. Atlassian and Figma work awesome together, but need it across more platforms than Figma Design only

As in chrome or any web browsers, having the ability to group file tabs will allow users that work in multiple projects, to have them organized and easy-to-find.   

The resize handles that appear when using focus view in Dev Mode or mobile preview in Figma Make are very handy. An option to display these when viewing a prototype in Responsive mode would be a very nice and helpful addition.

I know that I can export as SVG from draw.io and then drag and drop in FigJam but this does not allow me to edit. I would like to import a flowchart from draw.io in an editable format. Thanks.

I use nested auto layouts for my tables: The table is an auto layout containing columns, and each column is an auto layout containing cells. I want my table to be responsive, so I set all columns to hug, except the last column, which is set to fill, so that the table spans the whole width of its container. But in smaller screen sizes, if the screen width goes below a certain number, the last column gets clipped/truncated as it’s on ‘fill’. So I set a min-width to ensure it is not clipped. But, right now I need to hard-code the min width. It would be ideal to set the min width to ‘hug’, so that I don’t need to hard-code it or change it every time I update the contents of the last column.

1. Why I’m Writing ThisI’m sharing this as someone who deeply understands how design actually breaks—not in files, but in real products.Figma has already solved some of the hardest problems in our industry: real-time collaboration scalable design systems bridging design and development through Dev Mode But there’s still a gap that every serious team feels, regardless of size or maturity:Designs look correct in Figma, but behave differently in reality.This gap is now more visible than ever as Figma expands into product building, Sites, and AI-assisted workflows.2. The Core Problem (Observed in Real Workflows)Across teams, the same pattern repeats: Designers create visually perfect screens Prototypes simulate only happy paths Edge cases are not explored deeply Developers reinterpret behavior Issues surface during development or after launch This leads to: unnecessary rework misalignment between design and engineering avoidable UX issues in production The problem is not a

Would it be possible to have slots show placeholder UI without having to mouse over, at least at the master component level?Helps to just take a glance at something and understand the layout, also stresses me out to look at something and its just blank 😅  

IT would be great i Text would behave like colors for bulk update , When you ctrl + a. a file all text styles will be selected you can then open a list similar to variants and choose the correct text style to apply to all varients just as you do with colors Why it’s needed LLM like claude code and make disregard text styles but for dev teams using text styles is a must so we , currently we need to select each text field one by one there is not way to select similar text fields.Plugins allow to update the text style in a bulk but not as a text style just as an alerternative text .super important for maintaining clean code .

I don’t want to see some properties or values of any properties, if they are not used in the component. This is making it difficult to use the components. Example: I have a button component with Property 1 (Type: Primary, Secondary) Property 2 (State: Default, Processing) I only want “State: Processing” to be available for “Type: Primary” button. I have created a Variant of “Type: Primary” button with “State: Processing”. Currently the problem is when I use “Type: Secondary” button, I can see “State: Processing” in the properties. When I select it, the button “Type” changes to “Primary”. It would be great if the “Processing” state doesn’t show up in the properties list, since I don’t have that “State: Processing” created in the component Variants.

I’ve been working on a system-driven prototype in Figma where a global control (navbar) manages the state of multiple components (cards).The goal was simple: A button click updates a global state (for example active card) Individual components react to that state Smooth transitions (Smart Animate) happen between states (closed to open) However, this currently isn’t possible in Figma without major tradeoffs.Current limitations: Variables can update global state, but components cannot respond to them in a way that triggers variant changes with animation Smart Animate only works when explicitly defined through interactions such as Change to or Navigate, not when state changes indirectly To achieve smooth animation, we are forced to duplicate entire frames or create complex variant systems, which does not scale What this leads to: Either you build a scalable, system-driven prototype using variables but lose animation Or you build animated transitions but end up with exponential f

Pinning plugins to right-click menu A new section with the plugins you pin (it’s an option when you right-click a plugin from the regular menu). I don’t think I could explain this more. Pinning plugins to toolbar I think it could look something like this: When you would click the icon, the plugin would pop up like in illustrator, only it would have the UI of the plugin. It could only show up to 3 icons and the rest would be in a “more” menu. You could pin 3 plugins. If you do this, two more slots appear, showing the two most recent plugins you used that aren’t pinned but have been added to the toolbar. when an app is pinned like this, you can move it around like normal. However, when you launch it from the top it gets snapped to the top under the icon and the close button would minimise it. If I should make a hole Figma UI redesign, just ask.