Suggest a Feature

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.

It would be nice if I could quickly open pages in my design file in a new tab. Often pages contain designs that would be useful to view side by side with the current page you are working on. It would be nice if I could quickly open them in a new tab / new window instead of having to go back to files, open the file, wait for it to load and then navigate to the page.

Feature Request: Git-like Version Control for Figma BranchesCurrently, Figma allows us to create a branch from each file, but this limitation makes it difficult to manage complex design workflows — especially for teams working on large design systems.Git-like branching would make version control in Figma far more powerful and flexible. With this approach, designers could create multiple branches from existing ones — functioning much like environments (e.g., test, staging, production) in development.Attempt at elucidating through a flow diagramAs a design system maintainer, this would be a huge benefit. For example: Components that need additional review or testing could be safely designed in separate subbranches. Compatibility between different branches could be tested before merging changes into the main file. It would reduce merge conflicts and ensure higher quality and consistency across the system before releasing updates. Allow for other users to expand on branches through t

The gapVariable mode inheritance only works within a single collection. A mode cannot be derived from anything: not from a variable, not from an alias, not from a component property. This means that in any composed component, the mode of a nested component must be set by hand on every instance. Concrete caseAn Alert has two sizes, driven by modes in an `Alert size` collection. It contains a Button and an Icon, each with their own size collection. What I need to express is a mapping:| Alert size | Button size | Icon size || --- | --- | --- || small | Small | 14 || large | Default | 18 |There is currently no way to state this relationship anywhere in the file. Setting the Alert to `large` leaves the nested Button at whatever mode it happens to carry. Why the existing workarounds don't hold upOne shared collection.This requires the scales to align on two axes. They don't. My icons have five steps (12/14/16/20/24) and my buttons have three (Default/Small/Large). Forcing both into one mode

Would love it if you could paste a screenshot or image into a sticky note.It’s obnoxious to paste an image onto the whiteboard, move it to align with a sticky note, and then group the two elements together. Takes more time than it should :(

The default settings (at least in my Figma) load a percentage for letter-spacing, but this is not allowed in CSS. For a less avid programmer this may be confusing, when trying to get it to work. Either set the default to a px value, or add a warning inside the Inspect code

new AI agent “describe your idea” icon/text box feature when i click on an instance/frame in my design is a bit intrusive - little star icon gets in the way when i’m trying to adjust my design manually. maybe limiting it to the right click menu or simply creating a new hotkey would be better? also, telling this agent what to do is a miserable experience that usually just frustrates me back into doing the design myself as it is literally faster than typing it out. have seen a lot of feedback similar to this as well here.

Figma is no longer used only by designers and developers.In many real-world projects, designers share Figma files or prototypes with external stakeholders such as clients, managers, marketing teams, legal teams, and other non-design users for review and approval.These viewers did not necessarily choose Figma themselves, and many of them may not be familiar with Figma or comfortable using an English interface.This creates unnecessary friction in the review process.The intended journey should ideally be:Open shared link → Review the designBut in practice, it can become:Open shared link → Understand an unfamiliar English interface → Figure out how to navigate the prototype viewer → Review the designThere is another common scenario where this becomes even more problematic.After a client receives a prototype or shared file, they may need to share it with other members of their internal team. At this point, they have to interact with Figma's sharing interface themselves.This interface involv

When overriding a single element inside a slot in a component instance, Figma marks the entire slot as overridden. As a result, updates made to the main component no longer propagate to any elements inside that slot — even if only one element in the slot was actually changed. Expected behaviorOnly the modified element should be treated as overridden.All other elements inside the slot should remain linked to the main component and continue to receive updates.

Hello,When a user holds both admin and regular user roles on Figma, notifications get mixed together: license requests, AI budget overages (admin) and comments (user) all appear in the same feed, which makes them hard to read through.We currently have 3 tabs: All / Request / Unread.Would it be possible to add a dedicated tab or filter for comments, so that admin-related items (license requests, AI credits) can be clearly separated from day-to-day usage items (comments)? This would make it easier to prioritize and ensure nothing is missed depending on the context we're reading in.Thank you in advance for your feedback on the feasibility of this improvement.

Allow designers to create an AI-powered project space where the agent can use project-specific sources and default memory to understand the design context.Designers can upload or connect sources such as brand guidelines, design systems, UX documentation, product requirements, or tone-of-voice guidelines. The AI agent uses these sources as the primary context when generating, reviewing, or modifying designs.Inside the AI agent panel, designers can configure the project's context and choose which sources the agent is allowed to use.Example ScenarioA designer creates a Nike Brand Campaign project in Figma.They add:Nike brand guidelines Typography guidelines Color specifications Logo usage rules Brand voice guidelinesThe designer then sets the AI Agent's project context to:Sources✓ Nike Brand Guidelines ✓ Project Design System ✓ Default Figma Memory ✕ Other ProjectsThe agent can now generate or critique designs based specifically on the selected project sources.For example:"Create a campai

Describe the problem your experiencing and how your idea helps solve this When you create an autolayout frame, it always defaults to 10px. Many design systems call for an 8px grid and in many cases, users don’t want ANY padding especially where edge-to-edge designs are concerned. Ask questions to bring the community into the conversation What are everyone’s thoughts about the following solutions?: Default autolayout padding based on the big nudge amount in your settings Allow for tokenization of padding/margin grids and offer up autolayout parameters based upon those tokens Allow users to override the padding to 0px at the creation of the autolayout frame by using an alternative key command like ctrl+shift+a (command on mac)

Dear Figma Team,I would like to propose a feature that could be useful for UX designers and researchers. Problems I identified during my research:CJM, JTBD, empathy map templates, and other research methods are scattered across different tools — Figma, Google Docs, Notion, Miro. It takes 15–20 minutes to find the right method, and there is no centralized storage.Difficulty choosing the right research method.Fragmented workflows. After analyzing these problems, I created an application called UX Logic, which addresses them:Adding a library of methods and research materials, with the ability to add custom libraries and research materials. AI recommendations on the home screen. The AI suggests: “Structure insights,” “Validate hypotheses,” and “Build a CJM.” A unified workflow: Home - Projects - AI Chat - Library - Profile. All tools are in one place, without switching between 5+ applications. How can you use this application?Here is an example of one scenario:You paste interview notes int

When creating nested components, I want to lock the contents of a child components slots. For example, I make a generic “menu” component with slots. So then I make a specific “File Menu” using that generic menu component. That’s great. But when I turn that File Menu into a component, the contents are still editable in instances of the File Menu. I don’t want that. I don’t want consumers of the File Menu turning it into an Edit Menu. Standard Lock isn’t what I want, because I do want the user to be able to apply regular overrides, just not use the more drastic “Slot” features.So my request is for a feature that allows a main component to disable child slots.

Hello,I always enjoy using Figma Design and FigJam.I use FigJam for organizing Minecraft addon development and system design, and as projects become larger, I’ve started encountering difficulties balancing “the amount of information inside nodes” with overall readability.Currently, FigJam is extremely effective for:mind mapping organizing ideas visualizing dependencies structuring systems and architecturesHowever, as projects scale up, each node tends to require a large amount of detailed information, such as:identifiers recipes geometry references technical notes implementation status tags JSON-related information various propertiesIf all of this information is displayed at all times, the overall board quickly becomes difficult to read and manage.Because of this, I would love for you to consider adding:“Expandable / collapsible node functionality”For example:Normally, a node would display only a simple summary Pressing a button would expand detailed information A larger text area or s

Something about the old UI made it easier for me to understand that layers and pages were two sup panes. I think it was the fact that pages were indented a bit. It helped easily distinguish the pages and layers section of the left pane. Now with UI3 I find myself not being able to find where pages end and layers begin as easily. I need some sort of visual anchor here. My eye used to follow the negative space to the left of page names all the way down until I hit the layers area and now I feel like I’m going cross-eyed trying to find where my layers start and pages end.

The text above the top left of the frame is very small. Please have some setting so that when you zoom in a lot, the text no longer stays the same size and enlarges, so you can at some point easily see the text and be able to edit it easily. Sometimes I have to take a screenshot and then zoom in to see what i’ve typed. Other text in other apps appear easily readible. I remember another app ( I think Sketch) did this, when you zoom past 100% it keeps the font size relative to the zooms instead. so the artboard name becomes larger and larger.

Prototyping triggers won’t allow to bind an action to diagonal moves of the stick. Both LStick and Rstick. Tried to prototype a command wheel. Segments should be triggered by eight corresponding directions of stick movement. But only four of them was possible: up, down, left and right. Does anyone else in the game industry experience this? Is anyone using a plugin or workaround to help solve this?

I’ve been using Buzz to create full page templates, which has great potential. However, in the Edit Content panel, all editable fields for the entire page are displayed at once, which makes it difficult to navigate and manage.My suggestion is to improve this panel by making it context-aware. For example, when a specific section or component is selected on the page, the panel could display only the fields related to that element. This would make editing full pages much easier and more efficient.To give some context, in one of my projects, Buzz shows around 160 text fields along with dozens of media items. That’s a lot of information to manage in a single panel. A filtering mechanism based on the selected element would significantly improve usability.

Been playing around with the “expose nested properties” feature currently in beta. One of the great uses of variant properties is the ability to batch edit property values on multiple selected components. That use doesn’t carry over to exposed nested properties (yet I hope). Demo file to help When selecting one component instance exposing nested properties, said properties display fine. Add another instance of the same component to your selection (using Shift+Click), and the nested properties outright disappear from the right panel. I haven’t seen this issue raised elsewhere! Do you experience it too?

Hello,I would like to suggest some important improvements to the Lock Aspect Ratio functionality. Since Figma is widely used for building responsive designs, I believe this should be an important feature.I noticed that this issue has already been raised, and I believe it is a real problem when working with responsive layouts.The problemThe main issue is that Figma calculates the aspect ratio based on the exact pixel dimensions of the original element, including decimals, rather than preserving the intended aspect ratio.For example, suppose I have:A parent frame that is 375 px wide A responsive version of the design that is 440 px wide An element inside the 375 px frame that should have a 4:3 aspect ratioAt 375 px, the element is 343 × 257 px. This is not mathematically an exact 4:3 ratio, but this is understandable because using an exact 4:3 ratio would result in decimal values.However, when I resize the parent frame to 440 px, Figma appears to preserve the exact ratio of 343 × 257, ra

💡 Feature Idea for Figma: “Fonts Used in Frame”I’d love to see a feature in Figma that automatically shows all fonts used within a selected frame.For example:Fonts UsedInter — 12 layers Regular — 7 Medium — 3 Bold — 2 Roboto — 4 layers Poppins — 2 layersIt would be even more useful if we could click a font, see which layers are using it, and replace it across the selected frame.Suggested workflowSelect Frame → View Fonts → Identify Usage → Replace FontA Suggestions section could also highlight:⚠️ Missing fonts 💡 Too many font families 📏 Inconsistent text sizes 🎨 Similar text styles/colorsThis could make design audits and maintaining consistency much faster.Would you find this useful in Figma? What would you add to this feature?#Figma #FigmaCommunity #FigmaFeature #UIDesign #UXDesign #DesignSystems  

The fonts looks sharper and crispier in Figma due to the font-smoothing css property that applied in Figma’s CSS style by default. Hence the font-smoothing property is deprecated and the support is limited to MacOS, it is misleading when designing on a Mac and looking in any web browser on Windows. Providing an option to disable the font-smoothing in Figma settings will let us get the same results in Figma and web browser regardless of operating systems. Thanks in advance!

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?

It would be amazing to have a simple MCP tool that allows external AI agents to send prompts/messages directly to an existing Figma Make project.Something similar to Lovable’s send_message capability.The goal is simply:AI Agent → MCP → Figma Make → generate/edit designThis would make it possible to control and iterate on Figma Make directly from the AI agent without manually copying prompts between tools.