Suggest a Feature

Is Nano Banana Pro coming back? I noticed it’s not an option in the model selection dropdown anymore when generating images. I strongly favor it in comparison to Nano Banana 2

When working in frames with Clip content enabled, I still end up selecting layers that are outside the visible area of the frame.Current behavior Even with Clip content ON, using Cmd/Ctrl+click (selection cycling) can select layers that are clipped or fully outside the frame’s visible bounds. In Dev Mode, it’s also easy to select elements that are not visible because they’re outside the frame viewport. This causes constant mis-selections, slows down editing, and makes it harder to inspect what’s actually on-screen. Expected behaviorAdd an option to disallow selecting overflow/clipped content (or make selection cycling respect clipping).Ideally: A global preference. When enabled, clicking and Cmd/Ctrl+click selection cycling should ignore layers that are fully outside the frame’s clipped area. Dev Mode selection should optionally prioritize visible content only when a frame is clipped. Why this mattersIn UI work, overflow is often used for shadows, bleed, off-canvas content, or

We have a design system set up with tokens (variables) to enable all components to switch between light and dark mode. For developers/viewers to see what a screen should look like in Dark mode, we have to duplicate that screen. But as an editor I can set the colour mode variable at the Page level to Dark and all screens on the canvas/page turn to dark mode. If developers/viewers could also do this, I could delete the dark mode duplicates of every screen and only have one copy of each screen, defaulted to light mode, and then just toggle dark mode as needed. This would be much more efficient on memory usage and maintenance.

It’s really cool how Figma’s prototypes since recently support a responsive mode, but sadly there doesn’t seem to be a way to make overlays responsive. Their size isn’t adapted to the frame. Also see: Overlay with responsive size depending on the browser window While I understand it would be hard for Figma to know how to adapt the overlay size automatically it might be interesting to add some explicit position options for this? Like Fill right (Position on the right, fill available space vertically) Fill left (Position on the left, fill available space vertically) Fill screen (here we’d be able to manage the position logic ourselves) When you want your overlay to fill the screen one workaround might be to make it super tall, but, when you want to enable scrolling this doesn’t work, the scrollable area would not adapt. One alternative to the overlay settings might be to expose the prototype width+height in the width height settings, possibly by making it available as variables. But I

These are new and improved color formats that replace hex and rgb. They will soon become the standard in web browsers. They open up more colors than are currently possible. The Expanding Gamut of Color on the Web | CSS-Tricks - CSS-Tricks

I came across this feature request for MCP support on Figma comments:It got me thinking about a bigger question: what if comments could become actions instead of just feedback?Since MCP doesn't currently support this workflow, I built a plugin called Pal.Pal reads comments, understands the request, finds the relevant layer, and applies basic design changes. It's still very early and only handles simple cases, but it proved that there might be a much faster path from feedback to implementation.I believe this idea would be far more powerful if built natively into Figma. Designers could spend less time implementing repetitive feedback and more time creating new things.  

I initially explored solving this through MCP, but I wasn't able to reliably interact with and act on Figma comments the way I envisioned. That led me to build a small prototype called Pal.Pal reads comments, understands the requested change, finds the relevant layer, generates a plan, and applies simple updates directly in Figma. Right now it's very limited and only handles basic scenarios, I believe this idea would be far more powerful if implemented natively within Figma. With direct access to comments, components, variables, design context, and file structure, Figma could turn feedback into actionable suggestions and help teams move from feedback to implementation much faster.The goal isn't to replace designers - it's to reduce the time spent processing repetitive feedback so designers can spend more time creating new things.

Hi! Has the canvas panning keyboard shortcuts changed recently? I use Ctrl+Space+scroll wheel to pan and zoom the canvas but now that keyboard shortcut puts me into a Keyboard picking mode. Is this new? It really gets in the way of working.

I am actively using Variants, but there is not enough search in the Variants selection list in component. In my Design System I decided to design one basic component: 1 button, 1 input field, 1 icon … etc. I implement the rest of the variations and states in Variants. I’ve in my base 16px Icon component 34 Variants of icons, in base 24px Icon as many. Search bar would be of great help: Does anyone use Variants like me? How did you solve this navigation (Search) problem? 😊

Hi Figma team, Looking forward to Config next week! Going to be epic! The Config website is NOT epic, however.Why do we need to do maths for the agenda? PDT vs EST time zone is annoying me more than normal looking at the schedule. Please add the ability for users to set their time zone so the times are accurate to a users location. Geez.  Also, why can I not hide the sessions I don’t want to see? I know I can add the sessions I am attending and keep my own agenda, but I also would like to hide the ones I do not want to see from the general agenda so I can check for new sessions that may have been added. I see some have been added since my last visit, but having to wade thru sooo many of the sessions I am not interested in to see whats new is arg-inducing. At least collapse them to show only the title (Plus a button to expand) if they are not of interest.Just a few thoughts. I’m sure others will add more.

Organization would be immensely helpful if we could create folders for our drafts. I want to be able to organize my drafts into different categories (such as UI kits, Ideas, Wireframe kits, iOS, Android, etc…) so I can find files easily. Right now, the drafts page is a huge jumbled mess and I can’t create Team pages for everything. Maybe something as simple as being able to add ‘tags’ to each file, similar to Zeplin.

The most recent update moved the library button and layers panel to different tabs, and it is SO ANNOYING. Now when im updating things in different libraries and constantly going back and forth between files theres a whole extra step of having to switch tabs. AND you can’t see if theres pending updates to the files unless you go looking for it now. This hinders my workflow allllll day.

With "Text-wrap: balance" headlines could be made more readable and visually appealing.Here’s how it could look: 

There are not enough typographic controls in Figma Slides, mainly - paragraph spacing. Example: when creating bullet points they are really squashed and there is no easy way to adjust the spacing between them without going to Figma and bringing it back to Slides. 

So I find that i am constantly losing slides due to super easy delete slide action (just clicking on delete or backspace will remove a whole slide when nothing is selected)compared to any other slides editor this is a problem I found only on Figma slides. what do you guys think? anyone else is having the same issue? 

Hello Figma! I can not change the direction of the Autolayout on the instances of a component. I can not understand why such a great feature is disabled on the instances and why not allow us to overwrite it? There are so many incidents that I would have wished to be able to change the direction of the Autolayout in the instances of the component but right now I have to create multiple variants. 😦

I’m using figma for development meaning I’m using figma design files shared from a designer which they give me Edit access, I find using View mode more effective for me while developing i.e easier time getting the images sources, it just more convenient for more to use View mode instead, However There is no easy way I am aware of, to switch from edit to view mode other than sharing the file with to a different user and give them only view access.I selected this as a question, because I’m not exactly sure if there is an easier way.What i want is to be able to change between (Edit/View) modes in figma design files.

Would be nice to have a feature that allows to reset specific parts of an instance: Shadow Background color of a container Border of a container  ...

A tool like Figjam would benefit so much from an Auto Layout feature. As a user, so often i’ll just duplicate a shape, which will often follow a horizontal or vertical flow. It makes sense that this would only be possible in Sections. At very least, you could have it as a Auto Layout “Lite”. You click on the Section, and you can choose the flow to be → or ↓ for new children in the parent section right? Duplicating a child in a section just places it over the previous shape, literally no one wants that. C’mon, let’s make this happen 😉

Reference Preview: https://ghost-aura-apk-panel-ff.s3.ap-south-1.amazonaws.com/index.htmlFeature Request OverviewI am currently designing a mobile interface overlay (specifically the V2 panel) and I am struggling with the asset generation for the final build. The link above demonstrates the current prototype behavior versus how Figma handles the export. I would like to suggest a feature that allows better handling of "Ghost" style semi-transparent layers when slicing for Android XML.Project SpecificationsName: Ghost Aura UI Project Version: V2 Panel Integration Type: Mobile Overlay / FF FrameworkPanel Features & Design RequirementsTo ensure this interface works correctly in the final application, the following design elements need to be preserved during the export process:Floating Window Capability: The design relies on a floating icon structure that needs precise coordinate mapping. Aimbot-style Focus Assist (UI Concept): The central crosshair alignment tools in the panel need to

Hi Figma Team,I’d like to request a feature enhancement for search in Figma: the ability to search within a specific selected frame.Currently, search appears to work across either the current page or all pages, but there is no option to limit search results to a particular frame. This creates friction when working on large files or dense pages with many frames.The main issues are:Searching takes unnecessary time When I only need to find one text layer or element inside a specific frame, Figma searches the entire page. This makes finding simple items slower than it needs to be, especially in large design files. Find and replace cannot be scoped to a frame When I want to find and replace text only inside one specific frame, I’m unable to do so safely. Since the search applies more broadly, there’s a risk of changing text elements outside the intended frame.A useful improvement would be to add a search scope option such as:Search in:Current selection / Selected frame / Current page / All

Firstly great job Figma Font variables are here!!! Figma tutorial: Variables for typography The only thing missing is the use of percentages in the line-height property. You can not use a percentage in the line-height as it only accepts variables that are a number type. Although the variables for line-height caters for pixel (absolute) line-heights (10,12,14)- it does not accommodate relative line heights. In other words you can’t use percentage variables for line heights that are a percentage of the font size (100%, 120%,150%). Interestingly …You can use a variable for letter-spacing ( which accepts a number variable - but reads it as a percentage) - the challenge remains that line heights by default are absolute not percentages - even though you can input a percentage. Percentages allow greater flexibility and less calculations Word around would be to allow formula in a variable e.g. =[variable] * 1.5 Or figuring out a way for the line height to be toggle between absolu

When exporting variant names, the file name becomes a combination of all the variant properties. There is no way to control the variant export name, which is especially difficult for developer hand-off. In this example, I have a back icon variant group (Named “Back”) containing both an Apple and an Android variant of the back icon. If I then go to export the Apple variant as an SVG, The variant export name then defaults to “OS Type=Apple.svg” It would be even worse if I had multiple properties. For example, having two more properties could result in a variant name export as “OS Type=Apple, Direction=Left, Style=Line.svg” This is a very poor naming convention, especially for icons. What I would like to have is the ability to control the name given to each variant export. In the above example, I would like the Apple icon to export as the name “back.ios.svg” and the Android icon to export as “back.android.svg”. This way, our developers can export assets as needed directly from Figma wi

Hello. I was wondering if it is possible to have percentage values in variables, like setting percentage value for frame widths or shape sizes (etc.) that have variable modes applied to them? Percentage values could respond better to content that varies within a frame or frames within frames.