Suggest a Feature

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.

SummaryAdd an option to prevent variables used in published components from being detached in consuming files. ProblemWhen a component library is published and used in another Figma file, consumers can detach variable bindings, potentially breaking the intended design system consistency. For libraries that rely on variables to maintain component integrity, this can lead to unintended overrides and make it harder to ensure consistent usage across files.Proposed SolutionIntroduce a setting in the variable's Details panel, such as “Prevent detaching in consuming files.”When enabled, this setting would prevent consumers from detaching that variable when it is used within instances of published components in other files, while still allowing the variable to be used normally elsewhere.Ideally, this restriction would apply only to the variable's usage within the relevant published component, rather than globally across every component or property that references the same variable.Why This Mat

Hey folks, first of all I love the new variable function. Within the setup of spacings I want to reference my base value (“8”) and do calculations, e.g. (spacing-base)*2". This works fine and the value is calculated properly within the input to add a new variable. But I expected not that the calculation string changes to the absolute value. With this behaviour I loose the connection/ reference to my base value and the calculation is some how obsolete. Does anybody feel the same? Will there be an update? Thanks

The desktop app keeps every open file tab fully loaded, each in its own renderer process. With ~12 file tabs open (design system libraries, UI kits, product files), Figma uses 7–9 GB of RAM on my 18 GB MacBook (M3 Pro). That pushes macOS into 8 GB of swap, slows the whole machine and drains the battery. Quitting and reopening doesn't help, because all restored tabs load again right away.The usual advice (close unused tabs, restart, clear cache) works, but I lose my tab setup, and the tab bar plus the native menu bar are the main reasons I use the desktop app instead of the browser.The interesting part: the desktop app already has tab discarding. Its config is delivered as the dynamic config desktop_tab_discarding and ends up in ~/Library/Application Support/Figma/settings.json:"desktop_tab_discarding": {  "default": {    "tabInactivityThreshold": 172800000,    "discardCheckInterval": 3600000,    "minTabThreshold": 5,    "minNonDiscardedTabThreshold": 3,    "gracePeriod": 1800000,    "i

Description: As a designer with many years of experience, I do almost all of my design work in Figma, including print and packaging projects. However, working with print layouts in Figma currently faces two major bottlenecks: Pixels-only constraint: The lack of physical units (mm, cm, inches) and DPI settings forces us to constantly calculate and convert print dimensions (like 300 DPI) into pixels manually. No CMYK color profile support: Because of this, we still have to switch to Adobe Photoshop or Illustrator for final print preparation. Proposal: If Figma added support for physical dimensions and CMYK color spaces, it would eliminate these workflow gaps and become the ultimate all-in-one tool for both digital and print design.

Feature Suggestion: Custom Folder ThumbnailsWe all know that folders currently display thumbnails based on the files inside them. While this is useful, it would be even better if we had the option to set a custom thumbnail for each folder.For example, imagine I'm working on products for Meta and have separate folders for WhatsApp, Instagram, and Facebook. Instead of showing file previews, I could set the WhatsApp logo as the thumbnail for the WhatsApp folder, the Instagram logo for the Instagram folder, and the Facebook logo for the Facebook folder. This would make folders much easier to identify at a glance and help improve organization, especially in large projects with multiple brands or products.It would be great to have a "Set Folder Thumbnail" option that allows users to upload an image or choose a file frame as the folder cover.If you'd find this useful too, please leave a comment or like this suggestion so the Figma team can consider it. Feature Suggestion: Custom Folder Thumbn

Our components are themed with a variable collection, not with extra variants. The collection has four modes:Personal light and personal dark are the consumer theme. Light is the normal surface. Dark is the inverted, brand-colored surface. Business light and business dark are a separate business theme. Same two surfaces, different colors from personal.A button has no Theme property. Type, size, and state stay the same. The mode is set on a parent frame and inherited, and the fills come from color variables. The same primary button looks different in each mode.In code we have a matching theme value. Code Connect cannot emit it, because figma.selectedInstance only exposes component properties, nested instances, and text. There is no way to read the active mode.The Plugin API already has this as resolvedVariableModes, including modes inherited from a parent. Please expose the same thing on the Code Connect instance, with the collection name and the mode name, so a template can set the the

Feature Suggestion: Custom Folder ThumbnailsWe all know that folders currently display thumbnails based on the files inside them. While this is useful, it would be even better if we had the option to set a custom thumbnail for each folder.For example, imagine I'm working on products for Meta and have separate folders for WhatsApp, Instagram, and Facebook. Instead of showing file previews, I could set the WhatsApp logo as the thumbnail for the WhatsApp folder, the Instagram logo for the Instagram folder, and the Facebook logo for the Facebook folder. This would make folders much easier to identify at a glance and help improve organization, especially in large projects with multiple brands or products.It would be great to have a "Set Folder Thumbnail" option that allows users to upload an image or choose a file frame as the folder cover.If you'd find this useful too, please leave a comment or like this suggestion so the Figma team can consider it.  

Hi all,Is there a keyboard shortcut to navigate through comments?  eg. Next / Previous (Ondrej_Pavlicek suggested I this post here)Thanks!

Is there any plan to be able to create the gradient itself as a variable? For example, if I wanted some themes to have a solid background variable but others to have a gradient?

I often work with two Figma windows side by side. The left one is for browsing our design system, and the right one is where I’m designing, placing the components I get from the design system.In this setup the sidebars take up a lot of space on both sides of each canvas. In the design system window I only need the Layers/Pages panel to move between pages and find components. I don’t need the right sidebar (text styles, position, layout, etc.) there at all.Figma already lets you minimise the left sidebar. Could we have the same option for the right sidebar, per file or window? Hide UI isn’t a fix, because it also hides the Layers panel I’m using to navigate.

One thing that’s become frustrating is that it’s no longer possible to collapse just the left panel while keeping the right panel visible.In UI2: Ctrl+Shift+\ only hid the left sidebar. The collapse arrow on the left also only hid the left sidebar. Now in UI3: Both Ctrl+\ and Ctrl+Shift+\ collapse both left and right panels. The collapse arrow also hides both panels together. This makes workflows harder for users who want to maximize canvas space but still have quick access to the Inspector or Design panel on the right.Request:✅ Please restore the ability to independently collapse the left and right panels — both via shortcut and via the left collapse arrow.✅ Even a setting in Preferences to toggle between “unified collapse” and “independent collapse” would be great.

When I merge a branch which has some comments, those comments are not copied/merged/… to main file. Is it expected behaviour or “thing in progress”? I would love to have those comments transfered. So i don’t forget anything 🙂

I always want to create an IA before designing, but its such a chore. I end up using a bulleted list (with indents to show hierarchy). I want to be able to copy-paste my list into FigJam and have it automatically generate an IA for me

Please make Dev Mode Annotations visible by all roles, not just Full Dev Mode seats. This can become costly for users needing context but not all the other dev-mode features. Here’s the scenario: We have a dashboard, with cards showing a customer’s account status. This status can be mapped from multiple back-end statuses, to show just one front-end status. For example, any of the following could be mapped to a single status known to the customer as “Completed”: canceled, terminated, sold, complete, etc. This is something that the developer needs to reference, but then also the PM needs to reference in writing tickets (who doesn’t need full dev-mode access), the QE needs to reference for testing automations, and various other individuals on our team. Placing it in a comment makes it less clearly attached to the specific piece of the design, and requires us to keep documentation dispersed among different tools (Jira, Confluence, Figma etc). Simply making Dev mode annotations visible to v

This is the singular reason why choosing fonts is so tedious in Figma. I’m thankful for the update to finally be able to see the font before applying it to my text (which is the literal bare minimum), but being able to see what a font looks like doesn’t make choosing a font any easier if you know what kind of font you need, but you still have to scroll through hundreds of alphabetically organised fonts of varying classifications that don’t apply to you, when a simple filter would make the decision 10 times quicker. It makes the experience of designing start to finish in Figma frustratingly difficult.

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.

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.