Suggest a Feature

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

I’m always juggling between files and I need many tabs to be opened for easy access. Tab grouping was a really helpful feature. I request Figma team to also roll-out vertical tabs feature for Figma Desktop client. Even chrome has vertical tabs now. Since figma is chrome based I think it should’nt be a problem for them to implement it.

Viewport-based animation triggersAnimations should be able to start when their component enters the viewport while scrolling in Prototype mode, rather than starting immediately when the parent frame loads.Suggested controls:Start when entering the viewportConfigurable visibility thresholdPlay once or replay on re-entryPause, continue, or reset when leavingOptional delayIndependent playback from the parent frame’s timelineThis would make animated components practical in long, scrollable page prototypes and allow multiple animations with different durations and start positions to coexist.

In other design tools you can simply press a key, and any selection outlines, grab handles, etc. get hidden while the key is down, so you can preview and evaluate how things look, without having to de-select everything and lose your selection. Apparently there is no way to do this in Figma =( This is important while experimenting with different colors, fonts, etc., and in Figma it could be used to see how different sizes, variants, and states, look in your design, without those selection handles and outlines getting in the way of you previewing things.

Feature requestI would like the ability to choose which point in an animation is displayed as its static preview in Design mode.Currently, an animated frame always shows its initial state. This is not always the most representative or useful visual state when working on a layout. My workaround is to create a component with separate “Cover” and “Animation” variants, but this adds complexity and can affect video playback and animation timing.Ideally, an animation could have a configurable Design mode cover or poster frame. Designers could select a timestamp or capture the current animation state, while playback in Present mode would still begin from the actual start.This would:Make animated designs easier to understand on the canvasProvide more representative thumbnails and previewsRemove the need for duplicate cover variantsPreserve the original animation timeline and video playbackImprove collaboration when reviewing files in Design modeThis could work similarly to selecting a poster f

I have been designing for set-top boxes for several years now. And it is very convenient to do it through the transmission of the screen to the TV. But, there is no official support for Figma Mirror for TV sets. Many times I wrote to support and asked, but I always got the answer that there is no support. The most interesting thing is that Figma Mirror works perfectly on Nvidia Shield or Google Chrome (last generation) set-top boxes. You only need to put the app through aptoide. But with each time figma mirror refines the functionality for the phone, which severely degrades the functionality in TVs. For example, last year, after another update, the Remote Control for prototyping stopped working on the TV. It was very convenient to make a prototype, connect the buttons on the remote, and control the app. It felt like you were really using an out-of-the-box app. But it doesn’t work anymore. The second example happened with the last update. There was onboarding, which doesn’t allow you to

I’m sure this is a request that has come up many times before, but I’d really love to see the ability to configure haptic feedback in Figma.Many mobile interactions rely on haptic feedback, such as pull-to-refresh, confirming whether a gesture will trigger an event or not (like drag and drop), or providing tactile feedback when an interface changes state.For truly faithful prototyping, haptic feedback is something Figma is currently missing, and it makes it harder to accurately replicate the final user experience.That’s why I’d love to see haptic feedback integrated into Figma prototypes, with the ability to configure when and how it’s triggered.

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.

Annotation mode is useful, but when you write a lot of specifications, it clutters the screen and makes it difficult to concentrate. I want it to be an experience where you can read each comment in turn, like comments. Ideally, it would have the same visibility as the comment panel.

Hi Figma team,My team and I have been experimenting with slots recently. I'd like to propose a feature enhancement: when a component with properties is added via a slot, those properties should be accessible directly from the main component.Ideally, these nested properties would surface automatically, eliminating the need to click deep into the component hierarchy to make edits.

I usually share my Figma file with developers so we can work on the same file at the same time. This is very useful because developers can inspect the designs and start working on them directly.However, I sometimes need to make changes or try different solutions before the design is actually ready for development.The problem is that developers can see these changes immediately while I am still working on them. This can be confusing, especially when I am still experimenting, changing layouts, or making updates that are not final yet.What I would like to have is a simple Draft / Publish option.When I start making changes, they would stay in a Draft version that only I can see. Developers would continue seeing the latest published version.Once I finish my work, I could click “Publish Updates”. At that point, the changes would become visible to developers, and they would receive a notification that there are new updates.It would be even more useful if Figma could highlight the updated scre

In Finland, we have to attach the invoices to all card payments for bookkeeping. Now I need to every month to go to Favro and manually download the invoice. Please add a feature where I can define an email address for the invoice emails and automatically send new invoices in an email with the PDF invoices attached so that we can automate the download and processing of the invoices. The subject of the email should have the same structure each month ("You Figma invoice YYYY-MM-DD) and the PDF invoice name should be unique and contain the date of the invoice, for example, Figma incoice YYYY-MM-DD

It would be very convenient to be able to create folders for saved plugins and sort them yourself, which would make it easier to find the plugin you need when you don’t remember its name while working in Figma. For example, you could create a group for plugins called “Palette,” which would contain only plugins related to choosing a color palette. This would greatly simplify finding the right plugin for your work, since you’d know which plugin you need and in which folder you can find it — without having to know the plugin’s name and search through the list of all plugins, especially if you haven’t used it in a long time.

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.

Whenever I’m creating a component with variants, when it hit the plus button, it puts a copy down and to the right. hit it a couple more times and they just keep going right.My first click after hitting the plus is to turn on autolayout for the component. Feels like this should happen by default. This view can’t be useful for anyone.  

Hello, It would be more than interesting to be able to create variable at a component scope. And of course instance to inherit those variables. Why ? it would be a good way to organize variables. One file can have a lot of different components and subcomponents = a lot of variables. it would give us the possibility to ease prototype creation by preparing upfront variables in components library. it is a good way to get rid of variants. I mean variants are nice but variables are far better :). it would give the possibility to create different set of variables corresponding to different state of the components faster.

I’m developing an icon set, and attempting to export a set of uniformly sized SVG assets. Each icon has a 20 x 20 frame, with the vector graphics nested inside. In some cases, the graphics have strokes that exceed the edges of the frame, even though the vector paths themselves are inside the frame. In those cases, when exporting to SVG, the viewbox is greater than 20 x 20. How can I restrict the viewbox to a very specific size? Seems like this post is related, but I’m having a hard time understanding the guidance: SVG exports at a different size to W & H values in editor - #3 by Corin Thanks!

In Figma prototypes, elements set to Fixed are automatically rendered above scrolling content. This makes sense for common UI elements such as fixed headers, navigation bars, or floating buttons — but it prevents other very common web design patterns.For example, a background element may need to remain fixed while the page content scrolls above it. Currently, this requires workarounds with nested viewport and scroll frames.I suggest separating scrolling/positioning behaviour from layer order, similar to how this works on the web with CSS position and z-index.A simple option for Fixed and Sticky elements could be:Always on top – current behaviour Respect layer order – the element remains fixed/sticky but retains its position in the layer stackThis would make it possible to prototype fixed backgrounds, overlapping sections, layered sticky elements and other common web interactions much more naturally, without restructuring the entire prototype.In CSS, position: fixed or position: sticky 

I want to present a full page prototype in Figma Design where most interactions are built in Design, but more advanced sections are built in Figma Make. Today, a Make embed can be shown on the canvas, but not as part of the actual Present/prototype mode flow. I would like Make content to render as an embedded block inside a scrolling Design prototype, so advanced interactions can be presented in context together with the rest of the page.

  Hi Figma team,I'm writing to suggest adding Simplified Chinese as an official UI language. Here's why it matters:1. Huge unmet demandChina has hundreds of thousands of UI/UX designers and an even larger number of PMs and developers who collaborate in Figma daily. Many currently rely on third-party Chinese localization plugins, which frequently break after Figma updates and pose security risks. An official solution would immediately serve this massive user base.2. Competitive pressureLocal competitors like MasterGo and JS Design (即时设计) have captured significant market share in China largely by offering native Chinese interfaces and local server infrastructure. Official Chinese support would help Figma defend and grow its position in one of the world's largest design markets.3. Better cross-functional collaborationFigma's core strength is real-time collaboration across roles. In Chinese product teams, PMs, engineers, and stakeholders often have varying English proficiency. A native Chi

This has been mentioned here: Hide layer using variables - #5 by Andreas_Braendhaugen1 Invert boolean variable for layer display - #14 by Desislava_Slavkova Inverted Boolean Property - #2 by drewcovi_usb but those topics are all closed. I am looking for the availability to HIDE a layer when a Boolean variable is TRUE and SHOW it when it is FALSE. So, the inverse of the default/current behavior. I want to do this without using components. Use case: When a variable is true, show one frame. When that same variable is false, show a different frame. I can get basically this by using two different variables: but it would be more convenient to be able to do it with just one. Just give me a Boolean toggle when the variable is used to say if the variable should be inverted or not.

For an product I’m working on, the design team has a system used by all designers. We hand-off designs both in english and arabic. So all components and pages need to support switching the initial english (left to right alignment) design to arabic design (right to left).Currently, I handle this in the following way:English font is [x] and arabic font is [y] → add the font names as typography variables to switch between Text direction, english [ltr] and arabic [rtl] → manually handle or use a plugin like RTL layout Components for english [ltr] and arabic [rtl] view → eg list, checkbox, header → add layout direction variants to change multiple elements direction to right for arabicThe problem with all of this is that it’s a lengthy process which is not scalable. The ideal solution would be that when a language is identified and set as a property/variable/setting, then on each element/frame figma smartly set the right rtl expectation → text direction right aligned, set font and it’s sizin

Proposing (but might just be me)I use the Paste to Replace shortcut a load. It’s one of those little but massive time saving shortcuts.  However, the shortcut Shift+Command+R is very close to Shift+Command+T (Open Recently Closed Tab). So I keep opening tabs which annoys the dooky out of me. I don’t know whether opening a previously used tab is such as common action that it deserves a hotkey. But if so perhaps it can be Shift+CTRL+Option/Alt+T.  Dunno. 

I’d to request support for using variables within prototypes for animation properties such as duration and easing. We’re working to systematize motion in our design system, and the ability to define duration and easing as variables would make motion much more consistent and reusable across files and teams. This is important because these values are foundational to how motion feels in the product, and they should be treated with the same level of structure and control as other design tokens. Right now, there’s a disconnect between how motion is defined in code and how it’s represented in Figma, since animation values can’t be managed in the same systematic way. Supporting variables for prototype animation properties would help bridge that gap, improve alignment between design and engineering, and make motion easier to maintain at scale.

Hey Figma team and community,Is there any chance we could get native support for WebP and WebM exports anytime soon?Right now, exporting web assets feels a bit outdated. We’re still relying on giant PNGs or super heavy GIFs, only to manually run them through external conversion sites before sending them off to dev.Having native WebP for crisp, lightweight images and WebM for smooth UI video clips (especially with transparent backgrounds) would be a massive quality-of-life upgrade. It would make the design-to-code handoff so much cleaner.Upvote if you’re also tired of using 5 different file converters every day!