Share Your Thoughts

Currently, only Preview and Code edit modes are visible. Are additional editing modes accessible?

I want to organize my components into Icons, Buttons, Fields etc but these are already inside a folder and figma does not let me create any more nested folders so I need to browser all my 200+ components from one heap? And I’m not going to move them out from the folder because I need the parent folders too. Very bad designer experience!

It used to be that when you changed the fill on a shape from solid to a gradient, it would make the second gradient color the existing solid color with an opacity of 0%. This was great and really sped up my process. In the last update they changed this behavior so now it makes the second gradient color some arbitrary darker shade which just adds more clicks to my workflow and some annoyance especially since it used to work better… Is anyone else having this problem?

ngl, the new ui3 is pretty good. the only thing i dont like is the toolbar position. im still not used to it. maybe add an option to move it to the top?

Figma does let us move an object’s rotation origin with Alt + R / Option + R in the design canvas, but Smart Animate only documents support for matching layers plus property changes like position, scale, opacity, fill, and rotation/orientation. Because rotation origin is not listed as a Smart Animate property, prototypes often don’t honor the off-center pivot the way you expect.Use case: Opening door. Pendulum motion.

I think it would be amazing if there is a font filter Option for the style like, Handwriting, serif, sans!

I need to see the full list of a designer files to transfer ownership to new team member

When using typographic tokens and variables that have pre-determined values for the line-height, the only way to alter the line-height is to detach the variable from the text element and then manually edit the values in the "Type settings" palette. This essentially defeats the purpose of using tokens and variables and makes the detached item hard to update quickly in the future.Please consider adding more typographical overrides in the "Type settings" palette so that we can change the values without breaking the variable connection.  

Right now I’m not able to refresh a page in figma make preview. I have to close the tab and again preview it to refresh it.

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

When a change is made to an instance, any updates made to the original component after that do not carry over. This is very frustrating and results in me updating each instance. 

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?

Hey everyone. I want to share some feedback on the current Figma Make credit system, and provide a literal step-by-step escape route for anyone else who feels trapped.I absolutely love(d) Figma Make for the initial 0-to-1 build. Figma successfully built "vibe coding" into their platform, which is incredibly cool. But what isn't cool is blocking users from actually using it that way. The entire value proposition of Figma is rapid iteration. Yet, I hit my third lockout this week after spending nearly 100’s on credit expansions in a two weeks.Almost all of those credits were spent on debugging, QA, and fixing logic—not building new features. The usage-based pricing essentially acts as an "iteration tax" that actively discourages you from polishing your app.If you are building a complex web app, you have to eject your code to finish it. I was intimidated by this at first, but Claude Code and Gemini (which gave me easy instructions) literally walked me through the entire process. It was sho

This button is too close to the flow starting point section. I almost never want to send to figma make. Make this dismissable or hideable. I just want to make this frame a flow starting point.