Share Your Thoughts

I never use the AI Agent. I have no desire to use the AI Agent. I resent Figma’s attempts to get me to use the AI Agent. Yet, when I create a new Design file, the AI Agent panel is open by default. Two questions:How do I select either “File” or “Assets” as the default pane that opens when I create a new Design? When will you release an update that allows me to remove the AI Agent button from my left nav bar?

It really annoys me that Figma automatically creates subfolders when you export an element that’s inside a component and has a ‘/’ naming convention. I always have to go back into the folder and delete the folders or rename everything. It would be great to have a simple checkbox toggle in the exports panel to enable/disable creating subfolders, similar to Illustrator.

I usually share my Figma file with developers so we can work on the same file at the same time. This is very useful because developers can inspect the designs and start working on them directly.However, I sometimes need to make changes or try different solutions before the design is actually ready for development.The problem is that developers can see these changes immediately while I am still working on them. This can be confusing, especially when I am still experimenting, changing layouts, or making updates that are not final yet.What I would like to have is a simple Draft / Publish option.When I start making changes, they would stay in a Draft version that only I can see. Developers would continue seeing the latest published version.Once I finish my work, I could click “Publish Updates”. At that point, the changes would become visible to developers, and they would receive a notification that there are new updates.It would be even more useful if Figma could highlight the updated scre

In Finland, we have to attach the invoices to all card payments for bookkeeping. Now I need to every month to go to Favro and manually download the invoice. Please add a feature where I can define an email address for the invoice emails and automatically send new invoices in an email with the PDF invoices attached so that we can automate the download and processing of the invoices. The subject of the email should have the same structure each month ("You Figma invoice YYYY-MM-DD) and the PDF invoice name should be unique and contain the date of the invoice, for example, Figma incoice YYYY-MM-DD

First of all, thank you for bringing motion design into Figma. I've been trying Figma Motion, and I'm really excited about its potential.Here are some thoughts I had while using it—features and improvements that I think could make the experience even better.1. Copy & Paste AnimationIt would be extremely helpful to have the ability to copy animation properties from one layer and paste them onto another layer.For example: Copy all keyframes from one object to another. Copy only specific animated properties (Position, Scale, Rotation, Opacity, etc.). Similar to "Copy/Paste Effects" or "Paste Animation" in other motion design tools. This would significantly speed up repetitive animation workflows.2. Better Text Animation WorkflowAnimating text is currently quite tedious because many animations need to be created manually.It would be great to have: Built-in text animation presets (Fade Up, Slide, Pop, Typewriter, Blur In, etc.). Character, word, and line-based animation. Stagger

It would be very convenient to be able to create folders for saved plugins and sort them yourself, which would make it easier to find the plugin you need when you don’t remember its name while working in Figma. For example, you could create a group for plugins called “Palette,” which would contain only plugins related to choosing a color palette. This would greatly simplify finding the right plugin for your work, since you’d know which plugin you need and in which folder you can find it — without having to know the plugin’s name and search through the list of all plugins, especially if you haven’t used it in a long time.

I just want to adjust the page settings for each page “frame” so to speak so I can make it wider. It’s not clear that this is possible.

Whenever I’m creating a component with variants, when it hit the plus button, it puts a copy down and to the right. hit it a couple more times and they just keep going right.My first click after hitting the plus is to turn on autolayout for the component. Feels like this should happen by default. This view can’t be useful for anyone.  

Hello, It would be more than interesting to be able to create variable at a component scope. And of course instance to inherit those variables. Why ? it would be a good way to organize variables. One file can have a lot of different components and subcomponents = a lot of variables. it would give us the possibility to ease prototype creation by preparing upfront variables in components library. it is a good way to get rid of variants. I mean variants are nice but variables are far better :). it would give the possibility to create different set of variables corresponding to different state of the components faster.

I’m developing an icon set, and attempting to export a set of uniformly sized SVG assets. Each icon has a 20 x 20 frame, with the vector graphics nested inside. In some cases, the graphics have strokes that exceed the edges of the frame, even though the vector paths themselves are inside the frame. In those cases, when exporting to SVG, the viewbox is greater than 20 x 20. How can I restrict the viewbox to a very specific size? Seems like this post is related, but I’m having a hard time understanding the guidance: SVG exports at a different size to W & H values in editor - #3 by Corin Thanks!

In Figma prototypes, elements set to Fixed are automatically rendered above scrolling content. This makes sense for common UI elements such as fixed headers, navigation bars, or floating buttons — but it prevents other very common web design patterns.For example, a background element may need to remain fixed while the page content scrolls above it. Currently, this requires workarounds with nested viewport and scroll frames.I suggest separating scrolling/positioning behaviour from layer order, similar to how this works on the web with CSS position and z-index.A simple option for Fixed and Sticky elements could be:Always on top – current behaviour Respect layer order – the element remains fixed/sticky but retains its position in the layer stackThis would make it possible to prototype fixed backgrounds, overlapping sections, layered sticky elements and other common web interactions much more naturally, without restructuring the entire prototype.In CSS, position: fixed or position: sticky 

Hello Figma Support,Please route this maintenance suggestion to the team responsible for the Figma plugin skills distributed for Codex. This concerns instruction discovery and packaging, rather than a Figma document or a demonstrated Plugin API failure.Environment: Codex desktop on macOS. Installed component: figma@openai-curated-remote, version 2.0.21. Observation date: 2026-09-14.In skills/figma-use/SKILL.md, the description at line 3 begins with mandatory prerequisite warnings and puts the actual capability and triggering objects later. In a display with limited description space, the warning is more likely to remain visible than the scope. The installed entry point has 34,998 characters and 435 lines. This is a static discovery concern, not a measured automatic-selection failure rate.Suggested English description:“Create, edit, or inspect nodes, components, variables, and layouts in Figma files using use_figma JavaScript. Read this skill’s API and execution requirements before call

The announcement of Figma Motion had me excited, but right now it feels like a more advanced prototyping mode. I understand that it’s still in Beta mode and I hope in the future it will actually be usable for integrating motion in a design system.Animation between statesIf I take a button from our brands design system, it would be very helpful to be able to keyframe states and variants. Maybe take a page from Rive’s book and add something like a State Machine.Text animationText animation is non-existent at the moment. If we want to create an animation of text being typed I’m not sure how we achieve this.TokenizationWhen exporting JSON, there are no tokens visible in the JSON file, it’s just raw values.Preset AnimationsThe preset animations are nice and all, but it would help immensely to be able to make a library of our own animations, so we can quickly build out motion components.Styles/ChoreographiesSimilar to how you can add multiple values to a typography and apply it as a style (c

I want to present a full page prototype in Figma Design where most interactions are built in Design, but more advanced sections are built in Figma Make. Today, a Make embed can be shown on the canvas, but not as part of the actual Present/prototype mode flow. I would like Make content to render as an embedded block inside a scrolling Design prototype, so advanced interactions can be presented in context together with the rest of the page.

  Hi Figma team,I'm writing to suggest adding Simplified Chinese as an official UI language. Here's why it matters:1. Huge unmet demandChina has hundreds of thousands of UI/UX designers and an even larger number of PMs and developers who collaborate in Figma daily. Many currently rely on third-party Chinese localization plugins, which frequently break after Figma updates and pose security risks. An official solution would immediately serve this massive user base.2. Competitive pressureLocal competitors like MasterGo and JS Design (即时设计) have captured significant market share in China largely by offering native Chinese interfaces and local server infrastructure. Official Chinese support would help Figma defend and grow its position in one of the world's largest design markets.3. Better cross-functional collaborationFigma's core strength is real-time collaboration across roles. In Chinese product teams, PMs, engineers, and stakeholders often have varying English proficiency. A native Chi

This has been mentioned here: Hide layer using variables - #5 by Andreas_Braendhaugen1 Invert boolean variable for layer display - #14 by Desislava_Slavkova Inverted Boolean Property - #2 by drewcovi_usb but those topics are all closed. I am looking for the availability to HIDE a layer when a Boolean variable is TRUE and SHOW it when it is FALSE. So, the inverse of the default/current behavior. I want to do this without using components. Use case: When a variable is true, show one frame. When that same variable is false, show a different frame. I can get basically this by using two different variables: but it would be more convenient to be able to do it with just one. Just give me a Boolean toggle when the variable is used to say if the variable should be inverted or not.

Hi, where I can find the prototype mode in this new UI? and also the absolute position in auto-layout is also missing?

For an product I’m working on, the design team has a system used by all designers. We hand-off designs both in english and arabic. So all components and pages need to support switching the initial english (left to right alignment) design to arabic design (right to left).Currently, I handle this in the following way:English font is [x] and arabic font is [y] → add the font names as typography variables to switch between Text direction, english [ltr] and arabic [rtl] → manually handle or use a plugin like RTL layout Components for english [ltr] and arabic [rtl] view → eg list, checkbox, header → add layout direction variants to change multiple elements direction to right for arabicThe problem with all of this is that it’s a lengthy process which is not scalable. The ideal solution would be that when a language is identified and set as a property/variable/setting, then on each element/frame figma smartly set the right rtl expectation → text direction right aligned, set font and it’s sizin

Proposing (but might just be me)I use the Paste to Replace shortcut a load. It’s one of those little but massive time saving shortcuts.  However, the shortcut Shift+Command+R is very close to Shift+Command+T (Open Recently Closed Tab). So I keep opening tabs which annoys the dooky out of me. I don’t know whether opening a previously used tab is such as common action that it deserves a hotkey. But if so perhaps it can be Shift+CTRL+Option/Alt+T.  Dunno. 

Hey guys, I want to share this idea.I work with different companies that, for NDA reasons, each want me to use their own email and account. So I need to switch between accounts all the time.The situation is that Figma is great software, I love it, but regarding user accounts, it's a total mess.Maybe instead of adding an account to the app and creating confusion by having multiple files open from different accounts at once, a simpler solution would be to let users open another Figma instance.That would be helpful to drag and drop between windows and share some components between different projects.

I’d to request support for using variables within prototypes for animation properties such as duration and easing. We’re working to systematize motion in our design system, and the ability to define duration and easing as variables would make motion much more consistent and reusable across files and teams. This is important because these values are foundational to how motion feels in the product, and they should be treated with the same level of structure and control as other design tokens. Right now, there’s a disconnect between how motion is defined in code and how it’s represented in Figma, since animation values can’t be managed in the same systematic way. Supporting variables for prototype animation properties would help bridge that gap, improve alignment between design and engineering, and make motion easier to maintain at scale.

Hey Figma team and community,Is there any chance we could get native support for WebP and WebM exports anytime soon?Right now, exporting web assets feels a bit outdated. We’re still relying on giant PNGs or super heavy GIFs, only to manually run them through external conversion sites before sending them off to dev.Having native WebP for crisp, lightweight images and WebM for smooth UI video clips (especially with transparent backgrounds) would be a massive quality-of-life upgrade. It would make the design-to-code handoff so much cleaner.Upvote if you’re also tired of using 5 different file converters every day!

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. 

It would be helpful if the playhead snapped to time increments as well as existing keyframes. Right now, it’s difficult to position the playhead precisely when editing because it’s not clear whether it’s aligned with the intended time.

It would be amazing if there was an advanced clipping option that would allow designers to choose what edges clipped content and what edges let content run over it. I am working on complex enterprise software where I have dropdown menus with menu items with hover states as well as icon buttons in the menu items with their own hover states. And on top of that I need to show tooltips on some of the icon buttons and allow clicking to open a new modal. (There is a lot going on) We have workarounds for the overlay tooltip but the issue we’re running into is everything is in a scrollable container and that requires clipping to look decent. It would be nice to decide what edges get clipped. In our scenario we need clipping at the top and bottom of the scrollable container but the left and right don’t need it so that absolute positioned items can spill outside of the scrollable container.