Share Your Thoughts

Hello. Since the latest UI3 updates, the native AI image generation and editing tool has suffered two major usability regressions that significantly slow down my workflow:Missing Prompt History: The "Recent prompts" history (the clock icon) is completely gone from the new floating toolbar. Every time I need to reuse or tweak a complex prompt on a new image, I am forced to retype everything from scratch. Missing Quick References (+): Before, while the image generation panel was open, I could simply click a "+" icon on any image or frame on the canvas to add it as a reference automatically. That option has been removed, and adding references now takes considerably more steps.Together, these changes make iterating on AI images much slower and more frustrating than before. Please restore the recent prompts history tab and the quick canvas reference tool as soon as possible. Thank you.

The annoying part of the agent mode itself is that it is always located on the top right of every selection that we make -- which does not seem to be our use case at every moment to the point we have to keep it in every selection. A bigger problem is that it does not have an exit button when you accidentally click into the ask agent mode. You can only click out by clicking on the background canvas, and even then I figured out the way out after a few minutes. It is very annoying. 

Title: Feature Request: Independent UI Scaling Without Affecting Canvas RenderingHi everyone,I'd like to suggest a feature that I believe would significantly improve the Figma experience, especially for designers working with high-resolution monitors and Windows display scaling.The problemCurrently, Figma doesn't provide a way to independently resize its interface (menus, side panels, icons and text) while keeping the canvas at a true 1:1 pixel rendering.I've tested the following configurations on Windows:Configuration 1 — Sharp canvas, small interface Windows Display Scaling: 125% Figma Interface Scale: 80% Figma Canvas Zoom: 100% Result: Perfectly sharp images, but the interface becomes too small. Configuration 2 — Readable interface, slightly blurry canvas Windows Display Scaling: 125% Figma Interface Scale: 100% Figma Canvas Zoom: 80% Result: Comfortable interface size, but images appear slightly blurred, even with Pixel Preview enabled or disabled. Although both config

i find myself having to increase the size of a shader to render at high quality which also requires me to reconfigure all the settings. feels like theres a better way

Hello,I am looking to create a good hero section for my site, where it should take the height of browser in the first fold. The subsequent sections can be of fixed heights based on content. I need something like 100vh to have for my hero section.

Sometimes when I am working on a specific frame I accidentally click the Figma make sparkle icon and it brings up the chat as a popup and there is no way to click out of this unless you click out of the frame (it is extremely difficult because I use sections to group my frames)

Please let me disable this fly-out. It’s so annoying! 

I’m new to prototyping with variables, and I’m finding the learning curve is pretty steep 😅 I’m trying to build my own variable troubleshooter in my prototype that displays the current value for each variable, to help me see if the issues I’m running into are due to my failing to SET a variable, vs failing to properly DISPLAY a variable. But now I find myself troubleshooting my troubleshooter… 😭 Place forehead on desk, repeat rapidly It would be amazing if there was something in the native Figma UI for the prototype that would display the current value for each variable. Then as I interact with the prototype, I can see whether those variables are changing properly or not. It would really help narrow down the culprit for my prototype bugs. For example, when previewing a prototype in Axure, they have a Console panel that looks like this:

I would like to request an option in Figma's SVG export settings to preserve invisible vector elements in the exported SVG. This would apply to elements that remain on the canvas but are visually invisible, such as:Objects with opacity: 0 Objects with no fill and no stroke Other non-rendering vector elements This request does not apply to layers that have been explicitly hidden in the Layers panel. Hidden layers should continue to be excluded from export by default. Why this matters SVG is increasingly used not only as a static graphic format, but also as a foundation for interactive applications, design systems, animations, and developer workflows. In many cases, invisible elements serve important structural purposes, including:Acting as geometry references for JavaScript interactions Providing targets for future CSS styling or state changes Defining paths for animation frameworks Serving as semantic markers or anchors within an SVG document Supporting external tooling that relies on

Steps1. Put a few objects in collapsed groups and select them.2. In a plugin: figma.currentPage.selection = [a, b, c]Actual: the Layers panel scrolls to them and expands every collapsed parent.Expected: selection updates without touching the layer tree — or an opt-out.Why it hurts: alignment plugins have to restore the user's multi-selection aftera click, so every "pick key object" action opens several layer branches andscrolls the panel. Same for figma.createRectangle(), which auto-selects the node.Request:- figma.currentPage.setSelection(nodes, { revealInLayers: false })- figma.createRectangle({ select: false })

i can not connect to the figma remote mcp server via antigravity cli.i get an error: OAuth app with client id WPj[xxxxxxxxxxx]sit7 doesn't exist.The internet suggests that the Antigravity CLI is not whitelisted as a tool. Can you confirm?If possible, please whitelist it. Gemini cli support will end in 3 days and my workflow will be broken.

Dear Figma Support Team,I’m writing to share feedback regarding a limitation we’ve encountered while using Figma’s AI features to generate UI screens and other design elements.  The ProblemWe have an established design system in Figma that includes reusable components, styles, variables, typography, colors, and other design elements. Our design team relies on this system to maintain consistency across our products and ensure that every screen follows our established design guidelines.However, when we use Figma’s AI features to generate screens, layouts, or other UI elements, the generated designs do not appear to be properly connected to or based on our existing design system library.Instead of using our existing components, the AI often generates new elements that look similar to our design system but are not actual instances of our reusable components. Similarly, the generated designs may not follow our established styles, variables, spacing rules, typography, or other design convent

The Plugin API (and the MCP use_figma tool) can't clone or copy a node from one file into another. To reuse a screen from another file, agents have to rebuild it node by node from library components, which is slow and easy to get wrong. Please add a way to copy or import nodes from another file the user can access. I hit this using Claude Code with Figma's MCP server.

For example: I use a Card with a native slot (or the component swap method, either way). I place an instance of my custom component in that slot. I change a text property in my custom nested component. Then I go up to the parent layer and change the state of the Card (assuming it’s interactive). The text prop I set on my nested, sub-component does not persist across states. Currently, it does not!

Description: Currently, Figma allows switching between different Modes (e.g., Light/Dark) within a single variable collection. However, there is no built-in functionality to switch between entire Variable Collections dynamically. This limitation makes it challenging to manage multiple themes efficiently, especially in large-scale design systems where different themes (e.g., Default, Gaming, Minimal, Custom) share a common structure but require separate sets of values.Proposed Feature: Collection SwitchingWe propose adding an option that allows users to switch entire Variable Collections in the same way they can switch Modes. This would enable designers to define multiple themes and toggle between them seamlessly without needing to manually update Aliases or duplicate components.How It Would Work:Collection Selector: Similar to the Mode switcher, users can select a Collection (e.g., Theme 1, Theme 2, Custom Theme) from a dropdown in the Variables panel. Automatic Updates: When switching

As editor and maybe also as viewer I want to be able to see where specific components are used. So I’m basically talking about way to find instances of a component across files. There’s a plugin called “Instance Finder” but unfortunately it’s just working within one file not across. For huge design systems with multiple files and different designers working on it this is far from ideal. This idea is not new but since the other topics are closed I guess I need to open a new thread. See: Searching for component instance in a view-only file Ask the community I am a manager of the design system library in my org and I am trying to find instances of components in other designer files via the Org Libraries options, to see how components are being used. Clicking on a component takes me to the design file, but it doesn’t link to the frame where the component is used, which is what I would expect (even if it’s used in multiple instances, I would want to see at least o

My primary use case for FigJam is for creating flows that help me align with business partners on how we expect users to navigate our product. There are several points where it would be incredibly helpful to be able to add a link to a component that would take me (or anyone viewing my flows) directly to another component in the flow, without having to manually navigate to it. Small potatoes, but would be a big help when trying to create and walk through very large, complex flows.

Recently Figma received an update on Search functionality. Before this update there was a possibility to search across all the teams/plans from the search field in the left upper corner, currently search works only inside one org.I work in several spaces, more so, sometimes I work in client’s files where I’m added to the file exclusively but not to the space. So current update is very inconvenient as I’m supposer to either switch plans every time I’m switching task or go to ‘See all results’ → ‘All plans’. Previous implementation was much better for frequently used files. Please consider either returning back to previous implementation, or having plan selector in search field right away, the same as you can select certain page or all pages when you search through one Figma fileThanks!

English is difficult for me and I struggle with it. Hope to support Chinese language as soon as possible，please，please，please，please，please，please~

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.

Hello!It would be great to have the variables popout into a separate window, not be forced as a floating window within the work space.I work around this by opening my DS in two windows and placing them side by side, but it seems like a bit of a silly work around for something that could be done with a single button click.Thanks!

When working with variables it is really annoying that the Variables window closes on esc. I want to dismiss sample color or selecting another color from my styles as examples, but instead it closes the Variables window.

When using Figma on the web with an iPad it appears that I cannot delete a file. On computer this is triggered by right clicking. Long press works on iPad within the Figma interface but it does not work in the file selector. Instead what pops up is the prompt to save the thumbnail image.  I would like to request that the team prevent a long-press image save dialogue and instead give the option to the delete the file, or create an on screen button to manage file settings.   

我理解你们的初衷可能是觉得个人是团队的一员，弱化了个人，强调了协同；但为什么连最近查看的文件都收进了各个团队里面？多团队的时候切换文件，还要一个个先切换团队，非常难用；有时候东西多了，记不住每个团队对应的文件；其次有些文件是通过个人用户分享过来的，现在难道要我先加入他的个人团队吗？我最近每次找最近文件的时候，非常痛苦，非常难用；这样一刀切处理是不是太简单粗暴了

Absolutely love the ability to move items from one page to another. It would be a massive improvement if the items that are moved didn’t stack on top of one another, sometimes creating a mess of a pile. Certainly don’t expect it to be organized, but not stacking would be a massive improvement.Thank you for all the work!