Share Your Thoughts

I need to repeatedly access the test styles list or the Fill style library menu only to find it’s large enough for maybe 8 items out of 50 or more. This leads to endless scrolling through a tiny popup menu. Can this be increased to leverage the full height of my screen if the list is long?

We work on large display but Figma UI doesn’t adjust and shows minuscule panels for Text Styles, Library, Font lists, etc…. See related post below: 

Figma Motion: Support importing from Lottie and similar formats Maybe the Figma Motion Team already has this in their plans. When we are allowed to import Lottie files, that could help in bring in more expert animators into the Figma universe, and port their animated works into the Figma community. That’s a massive increase in the resources we can benefit from.  

AI Balance should be displayed in the User Menu, instead of the Figma File Menu.It’s an account-associated info, so it should be displayed there. 

Token-based authentication and MCPWe need to connect to the Figma MCP from Cursor. The current integration uses OAuth; we would prefer to authenticate with Access TokenIs there an official or recommended MCP solution from Figma that supports token-based authentication?

Subject: Feature Request: Native "Code-to-Design" / Reverse Engineering Import for the AI EraBody: Hi Figma Team,The AI era has completely flipped the traditional product development workflow. Today, many developers and creators use AI tools (like Bolt, v0, Lovable, or Cursor) to generate a fully functional website or app directly from text prompts.However, as the product grows, we still critically need Figma for scaling, brainstorming, advanced UX iterations, and maintaining design systems.Currently, moving an already existing codebase into Figma is a massive pain point. We have to rely on third-party plugins (like html.to.design), which often struggle with massive multi-page imports, require paid tiers for bulk uploads, or mess up layers.The Feature Proposal: We need a Native Code-to-Design Import tool built directly into Figma. Bulk Import via Repository/Sitemap: The ability to drop a link to a GitHub repository, folder with local code (HTML/CSS/React), or a Sitemap URL, and have Fi

I would love to have a feature in Figma Design that allows users to change the font family across an entire frame while preserving the existing font weights and styles.If the newly selected font family does not support certain weights used in the design, Figma could display a warning indicating which weights are unavailable and may be substituted. This would make it much easier to explore different typefaces without manually updating each text layer and verifying weight compatibility.

It’d be useful to be able to rename plugins. Right now it seems that you can only alter the name at the point of creation - the AI can rebuild it but will lose all existing chat/history.

About the current animation export:There should be a way of exporting a loop animation with an specific duration even though it’s not animated for that amount of time, if I want to create a loop, I’m able to see it animated on the preview but I’m not able to export it, unless I create again all the keyframes in the other direction, which should be unnecessary. 

I’d like to present an alert/message when an editor switches Mode away from a default variable in the standard Design edit interface. Is that possible?  

String variables in Figma currently work as full replacements — a text layer can be bound to one string variable, and its entire content becomes that variable's value. There's no way to embed a variable within a longer static string, like "Welcome back, [$username]" or "Order #[$orderNumber] confirmed".Supporting inline variable interpolation in text layers — similar to how template literals work in code — would make it far more practical to prototype dynamic content and reduce the need to split text into multiple layers just to inject a variable value.

Currently, when you set a scope for a variable (e.g., "All fills" or "Text fill"), that scope controls which properties it can be applied to, but there's no concept of visibility scope — determining where in the file a variable is accessible at all.Two improvements would make this far more powerful:First, property scopes should be assignable per variable within the same collection, rather than uniformly. For example, a spacing variable that applies only to gap but not to padding — giving design system authors control over where tokens can and cannot be applied.Second, and more importantly, variables should support an accessibility scope: whether a variable is global (available everywhere in the file), page-level (only accessible within the page it's defined on), or component-level (scoped strictly to the component it belongs to, not leaking into the rest of the file). This would allow teams to define internal component tokens that don't pollute the global variable picker, while keeping

Figma's color variable system supports solid color values, but there's no native way to define a variant of a color that applies a transparency, saturation shift, or other HSL-based modification. Designers currently work around this by manually creating separate variables for every tint/shade/opacity level, which leads to bloated variable sets.It would be very powerful to allow color variables to reference a base color and apply modifiers (e.g., opacity: 50%, saturation: -20%) so that variant palettes can be derived programmatically from a single source.Beyond colors, this concept should extend to numeric variables as well. Designers should be able to define a variable whose value is a mathematical expression referencing another variable — for example: spacing-xl = [spacing-base] * 3. This would allow design tokens to maintain proportional relationships automatically, making spacing scales, type scales, and sizing systems much easier to manage and update from a single source of truth.

Please separate canvas from interface scale (View>Interface scale). I am workin on iPad app, and with 100% canvas scale i have almost 1 to 1 with physical iPad screen size - thats what I need. But also i want to make all UI elements of Figma smaller. I found this settings in View menu, but unfortunately it scales not only UI but everything including canvas - so with 100% canvas scale frame become smaller then real physical size.

hi! i would love to be able to save a custom-designed spring animation as a preset so that i don’t have to customize it individually for each prototype link.so when i click Smart Animate and pick a Custom Spring curve, i’d like to be able to save that configuration as a preset.

Text  Background color.  That's it, nothing else. 

Is there a way to auto-play a Figma Slides presentation? I created a Slides deck for use at a high school career day booth and I’d like to just start it and let it go through the slides automatically and then repeat until I stop it. Any built-in or creative solutions to achieve this?

Hi! Currently, when you click on a stroke in the right side panel and then Command+C copy it, then go to Command+P paste it on a different layer, the only properties it copies over are the stroke colour and opacity. Would be great if it also copied over the stroke width, position, and side customization 🙂

Could only find a close topic so reopening it. Currently it is not possible to hide components used within components, that will be applied in final use. My clients frequently would use the base components which I would like to disallow them to do. I’m aware of the hide syntax in the naming system, but if i do so, my components will break, because Figma does not recognized hidden components as being published.

When asking Figma Make to recreate an animation done in Figma Motion using shaders, it doesn’t do it properly, answering the following: 

I’m already finding it interruptive to my workflow as I do NOT wish to incorporate it. It’s skill dulling as a designer and annoying overall. I have loved using Figma for years and would hate to abandon ship because it’s joining other companies in wasting their time shilling AI features to customers who don’t want it. The suggestion button has been added close enough to work boxes that it’s easy to accidentally which is malicious and forceful UX.

Hi, Thank you for Figma Motion it’s great !There is one thing I can’t figure out : once I have set motion on the components, then add them to my website frame (desktop, mobile...) how can I set a trigger for the motion to begin ?For now, it appears that they all run at the same time, when the page is loadedIn AE, we can work on different elements (as we do here on components) and then add them to a precomposition so we can choose when to start etc…Can we add this on Figma Motion or on Prototype but the trigger won’t be a timing but a scroll ?Like, you have your full page : Header, Hero, Editorial whatever, and I would like the animation on the Editorial section to start when the user scrolls 10% on itThank you for your help !

Hey folks, Just wanted to share some feedback I had about the new Figma Agent feature when it comes to generating plugins and shaders. I was prompting this morning to create a new shader fill, and initially the agent refused my request to support a dropdown in the shader config because it said it didn’t exist. I checked the docs, found where it is supported, and sent a screenshot to the agent, after which it corrected course. Seems like something it should have understood out-of-the-box. Also, it claims it can’t add handles or overlays to its shader fills, such as how the Mesh Gradient fill gives you handles to configure the colors. Not sure if this is true or not, but if so seems like it would be a nice thing to support for shaders made by users and not just official Figma shaders.   

When you publish a component that contains nested components from another library (or that are bound/linked), the publish dialog doesn't make it clear which nested components are linked externally. This causes confusion about what's actually being published and what's being inherited.The publish dialog should list any linked or bound nested components above or alongside the component being published, so designers can understand the full dependency chain before confirming.