Suggest a Feature

It would help to be more aware if an object parameter, e.g. fill equals an existing variable in the file:A quick option to replace the unlinked value with the variable would also make it easier to conform to the design system.

Dear Figma Team,I’m writing as a regular Figma user deeply involved in creating interactive prototypes. I’d like to share a few constructive suggestions that I believe could significantly enhance Figma’s prototyping capabilities while streamlining the designer workflow.1. Keyboard Focus & Tab NavigationIt would be incredibly valuable to set an element (button, input, etc.) as “focused by default” when launching a prototype, and to navigate between elements using Tab or arrow keys — especially for accessible interfaces or controller-based UIs (e.g., TV, gaming).2. Dynamic Properties Linked to VariantsCurrently, variants are static. Allowing properties (color, opacity, size, etc.) to be dynamically linked to a variant state (e.g., “hover”, “active”) would enable truly interactive components without duplicating frames. For example: a button with black text on hover, without needing a separate frame.3. Keyboard & Gamepad Support in PrototypesAdding support for keyboard (arrows, Ent

It seems that previously link previews were updated in slack to show what was being shared instead of the entire canvas. I missed that and now my links are just links, no preview. Which is better than previewing the entire canvas still.I have the same suggestion for link previews in Teams. Please stop showing the entire canvas in Teams previews and either show just what is being shared, or just don’t show anything.

Figma needs an autolayout option for tables, or grids. None of the extensions or apps work well. Designers like me need to make grids all the time. Right now, I make autolayout rows, but they invariably need to be synced with the column header, which I do manually by editing fixed width.  Please add an autolayout for grid that would allow items to be in both a column and a row. 

I know that you can crop one-by-one by using the picture crop feature in Figma. But that will be a very tedious work! I also know there’re planty plugins that can crop pictures. After doing the work, they’re automatically downsizing the picture and not keeping the original pixels. It makes the developer’s measurement impossible:

Scope VariablesI would like to suggest an improvement.When I apply it to the desired location, first need to remove the "show all" option, but considering that I'm accessing a single item, I'll want to select only that option.If possible, it could display the item without selecting it, and if I need to select everything, I have the "select" option for that.Thank you very much.  

Artificial intelligence has transformed the way we interact with technology, moving beyond simple automation to systems that can observe, reason, and act independently. Central to this shift are AI agents, which serve as the backbone of modern intelligent applications. These systems are capable of making decisions, learning from experience, and performing tasks with minimal human supervision, making them essential for businesses and developers alike.Understanding AI agents and their capabilities can help organizations leverage these tools to improve efficiency, decision-making, and innovation. Defining AI AgentsAt its core, an AI agent is a system designed to perceive its environment, process information, and take actions to achieve specific goals. Unlike traditional software, which follows predefined instructions, AI agents are autonomous and adaptive. They can assess situations, make decisions, and learn from feedback, enabling them to handle complex and dynamic tasks.A practical AI

I would like to highlight all the connectors from a given object in Figjam. For example, if I have a block that has several connectors coming into and out of it to many other blocks, right clicking on the block and “highlight all / highlight incoming / highlight outgoing” options. It would make all the other connectors on the screen transparent or greyed out so that I can easily see which objects are connected to my object and how its connected.

Hi, I've been working on a prototype, and animating the chat bubbles turned out to be quite a tedious task. To create the animation, I had to duplicate multiple frames and apply individual delay animations to each chat bubble.I'm wondering, is there a way to apply a delay animation to a group of elements collectively and adjust the timing for each, similar to how you'd stagger animations when loading a collection of cards?With Figma's current capabilities, the only workaround seems to be creating multiple frames and manually adjusting the opacity and timing for each element to simulate delayed appearance which becomes repetitive and time-consuming when applied across multiple components.Would love to know if there’s a more efficient approach or if this is something the team is planning to improve in the future.

I am using auto layout a lot in my projects and think it is awesome. However, there is one small issue that annoys me a lot. The default setting for canvas stacking is always “Last on top”, which is usually not what I want. For instance when switching state of a dropdown in a layout, the dropdown list will appear below the content that is underneath it (at least in my case where the list is using absolute position). With lots of nested auto layouts, things quickly become a mess if you forgot to change this when you created the auto layout. I would suggest either of these solutions: Change default to “First on top”. Make the default setting optional Remember the last used setting (like the animation properties work)

One of the properties, very basic in CSS, that I miss most often in Figma is “background-color” for text. Would be awesome if you’d consider adding this feature on your roadmap, especially that you aim to become a competition for webflow.

I’d like to suggest an improvement to Edit instance swap property.Currently, when swapping a nested component via instance swap property, it’s not possible to adjust the swapped component’s — such as size, state, variant properties, or other component properties.It would be very useful if, within Edit instance swap property 🙏

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.

Just to bypass the disability of not allowing the glass effect to be applied to shapes, here is the workaround I found that does it half-way.The layer hierarchy is as follows:Group layer (Parent)|__ Group layer (Holds the ‘Frame’ where effect can be applied)      |__ Frame (The Layer with the Glass effect)|__ Vector Mask (The shape in question, used as a mask for the Group layer as you can’t get it by just masking the frame, doesn’t work like that)|__ Vector Layer (Used for the Stroke effect around the logo)This is really bad UX and I think should be allowed for shapes if it’s just a shader.

Hello Figma team,Feature Request: Exclude Specific Content from Frame ClippingWe propose introducing an option to selectively exclude certain elements from being clipped within a frame or component.Currently, when a frame has “Clip content” enabled, all child elements are uniformly clipped to the frame bounds. This limits design flexibility in cases where designers need specific elements (such as tooltips, floating labels, badges, or overlays) to visually extend beyond the frame while still preserving the frame’s structure, layout behavior, and constraints.Suggested Enhancement: Add a per-layer or per-component setting such as “Exclude from clipping”. When enabled, the selected element would visually overflow beyond the parent frame boundaries, even if Clip content is turned on. The parent frame should retain its clipping behavior for all other child elements. This exclusion should not break auto layout, constraints, or component integrity. Benefits: Enables cleaner and more real

https://fonts.google.com/specimen/Zalando+Sans+Expanded?preview.text=Hello%20awesome%20people!%20Do%20you%20want%20Zalando%20to%20be%20added%20to%20Figma%20fonts%3F&query=zalando  

This seems like a very large design oversight in Figma Slides. The help article says that “Published changes only apply to new slide decks that are made with the template.” Doesn’t this defeat the entire purpose of having a custom template where you can edit a style and have it apply to your entire presentation, instead of needing to manually tweak a header style on every slide? I expected this to work the same way instances update in Figma Design when you make a change to the main component, but even after publishing changes to a custom template in Figma Slides, my existing slide deck that pulls from that template isn’t updating colors & text styles. The published template changes would only apply to brand new slide decks, which means I’d have to define the template first and then create my slide deck. That completely goes against the general approach to how many of us create slide decks. For example, I don’t make the template before I start the slide deck. I make my slide deck fi

I'd love to be able to transform ONLY selected nodes. For example: rotation, resizing, etc. This can be quite hand sometimes when drawing and using shapes 

I’m working with Figma Sites and its built-in CMS, and I’d like to suggest a feature that would significantly improve the developer experience when using code layers / React components.Feature requestProvide an official React hook (or similar API) to access CMS data from code, for example:const teams = useCollection('teams');orconst { data, loading, error } = useCollection('teams');Why this would be valuable Many developers want to build custom React components (carousels, filters, tabs, animations) that rely on CMS data. Today, CMS data is accessible only through visual bindings, not programmatically. A hook like useCollection would: Bridge the gap between design-driven CMS and code-driven components Reduce the need for manual exports or external APIs Make Figma Sites more attractive for hybrid designer/developer workflows Since Figma Sites already supports React code layers, an official CMS hook would feel like a natural next step.

When a comment is marked resolved, it just shows the filled checkmark icon. It doesn’t say who resolved it and when it was marked as resolved.Contrast this to Google Docs, etc., which shows this information.I already saw:View who resolved a comment and when • 2 years ago • 4 replies See who has resolved or reopened comments • 10 months ago • 0 repliesProblem still stands.We should also be able to see who reopened a previously resolved comment, and when.

Hello, I would like to know if it’s possible to select several words in a text layer, for example to put them all in bold or a different color from the rest, but all at once. Like in Word or Google Doc, I believe the shortcut is ctrl + select the desired words or part of words. It would be useful if it also worked across multiple text layers. I tried all the shortcuts I could think of but nothing seems to work… Selecting words one by one and apply the wanted properties every time feels soooo tedious. Maybe its not a popular request but that would be so useful. Thanks !

Hi there! For design systems, because components can contain other components, it might be a good idea to allow designers to set an “inherit from child” or passthrough option that allows the size to be set by the child component. Right now I think everything is enforced by the parent level, and it can break things (reminds me of my childhood lol .. just kidding - kind of?). Bottom-up works better than top-down in any case :) (see New Scientist, “Why complex systems do better without us”). --And a lot of life is learning to let go lolI have a feeling this may have been reported as a bug in the past, and it may be a technical limitation of HTML itself. It may be worth considering for a future version of HTML/CSS if that’s the case. I notice the “hug” feature already inherits from child in its own way, but sometimes there are defined sizes (not autofit) that need to pass through to other elements. Allowing this setting to flow in either direction depending on the system design would be he

… not fake elements that look like links. The reason why is because someone posted a link to a Figma file inside a Figma comment, and when I tried to open it in a new tab (making sure I’m holding Cmd in macOS, same as Ctrl in Windows), it just opened in the same tab as the Figma file I’m currently viewing. It’s also impossible to right-click the link and get a link-related context menu. It’s not possible to easily copy the link too. Right now what we get is a regular browser context menu. Worst parts are: The draft comment I wrote was completely lost because of this navigation. There was no warning, and it wasn’t saved to be restored later. The back button doesn’t work. It doesn’t take me back to where I was. It just reloads the linked page, and then the back button is fully disabled. I had to go find the previous location myself manually. PS: On that note: Please also reduce the label of long links to be truncated with ellipsis in the middle (max 2 lines).

It would be great if dev could export without rounded corners applied and or have some export flexibilities

I use Figma for Mac, and often need to copy+paste the link designer shares on slack.