Share Your Thoughts

AI Builds everything on its own. sometimes its going out of control.Why cant we have a component based AI development system?Eg: i want to build an interactive table in my CRM, ERP which can be used accross multiple products with same UI, workflow & functionality. So, i will build the component myself and the AI builder should use my component only.That way i will have better control on building multiple integrated modules

Hi Figma community 👋Our team manages a shared design system that is actively evolving, and we frequently update components to improve usability and consistency.One challenge we often face is tracking component updates across project files. While Figma provides version history and “Compare with previous versions,” identifying changes requires opening each component individually. This becomes especially time-consuming when updates affect many components or multiple screens.It would be extremely helpful if Figma could provide better visibility into component changes, such as: Notifications when a referenced component has been updated Visual indicators showing which components have changed A clearer diff or change log for component updates This kind of functionality would greatly help designers, PMs, and developers understand whether updates require action on existing designs.Curious if other teams managing large design systems experience the same challenge? How are you currently hand

This is a feature request.I would like the ability to switch frame orientation between portrait and landscape to be restored. Without this feature, the tool has become very difficult to use.This feature may not be essential for people who only create simple mobile UI designs, but in reality designers often need to consider horizontal layouts as well. Content such as TV interfaces, YouTube, video apps, and films are frequently viewed in landscape orientation, so designing horizontal UI is necessary.Figma also supports paper sizes. Not being able to switch between A4 portrait and A4 landscape is inconvenient. When creating portfolios or documents, this limitation is especially problematic.I sincerely hope that the ability to switch between portrait and landscape directly within the canvas will be restored. Thank you very much for your consideration.Designers around me generally agree that Figma’s development is consistently thoughtful, with improvements that are smart and well-prioritize

All of my icons in the design system are part of a component set. When exporting them, the file names automatically include "name=" followed by the icon name. This creates extra cleanup work, as the "name=" prefix has to be manually removed from every file.

Don't change X field value when I change a shape's height or width.This happens when the “snap to pixel grid” is checked Before:X: 10.4, Height: 10 Change the height After:X: 10, Height: 9 If I am editing field A, don’t go ahead and change the value in some other field B.  Please understand user’s use cases instead of just assuming you should add some automated guardrail behavior.  

When you import an SVG to Figma, RECT tags get converted to PATHs. Mutating tags like this makes it a nightmare to work with Figma when developing SVGs.  Please stop mutating element types.

Feature Idea: An easy way to select a frame and delete all of the prototype links to that frame. Why? A lot of times when I’m iterating, I want to just rebuild a whole new version of a page. I’m reluctant to delete the old one though, so I just shove it to the bottom of my canvas. The challenge is that when I do that, sometimes I’m showing a client/stakeholder the new version of a flow and I accidently click a link that links me to the new page. Then I have an embarrassing “oops, that’s an old page!” moment, which sucks.

We are currently exploring a better way to communicate insights from user testing when handing over designs to developers (to create more transparency as to why features we designed they way they are, and to educate developers on user needs). I was hoping to display insights (with a link to the research) on the design (handover) page, so that the team implementing the features can understand why and how the designs came to be. I can’t see a relevant plugin or integration for this.Could we allow for user research tools to have an integration with Figma? Our team uses Dovetail, so that would be my preference. Of course there are workarounds which are more manual for those who would put in the time, but I think this feature would be helpful for team collaboration and encourage useful discussions.

When working on large projects, it’s difficult to find which part of the design refers to each AC in Jira. It would be great if we could link a specific AC from Jira to components on Figma. 

It really feels gross that I have to spend credits on results that turn out wrong despite following the best practices posted by Figma.It makes me want to not start a project with it because I could end up working far into the project before the AI decides it WON’T do something that it CAN. Then I have to decide how many times I try to convince the AI to do what’s being asked.I’d like to see Figma give me a chance to say I got what I asked for.Each result already has a thumbs up or down option. If I give it a thumbs up or start another prompt, the credits should be charged. If I give it a thumbs down, the credits are NOT charged and the prototype reverts to the previous state. Reverting the prototype should prevent people gaming the system except for the final prompt… And you could also put an expiration time on an unapproved prompt if you wanted to prevent that.

It would have been nicer and super helpful if I could rename similar titled multiple selected components at the same time. It helps when I have to link multiple components that have different names but are visually same to a new file.

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

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.

BLOG POST: Why does Figma deliberately add friction to the account upgrade process? 🤬 So I’ve been building start-ups for over 15yrs and the holy grail of any app is to convert a non-paying user into a paying one. But Figma has gone out of its way to deliberately make upgrading your account harder than it needs to be and violates every principle of UX in the process. The Problem:To use Dev Mode in Figma you must have a Full or Dev account. When I click the button to access Dev Mode I get a dialog that pops up that says “Upgrade to work in Dev Mode” and a button that says “Learn More” and a secondary button that says “Back to Design Mode”. Now if you’ve used the internet ever, you’d assume that the “Learn More” button will put you into a user flow where you can enter your billing info and access the premium feature you had just tried to access. But no, the geniuses at Figma have decided that this page should link to a support page!?!? *Blood pressure rises… On this support page no butt

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.