Suggest a Feature

The Problem: Lost in the Canvas WildernessWhen working on large, sprawling Figma files (especially design systems, deep user flows, or complex prototypes) with hundreds of frames, the canvas becomes a massive workspace.We frequently need to pan or zoom away from our current focus—the frame we are actively designing—to: Reference a component in the design library on the far left. Check colors/styles on the style guide at the bottom. Look at a distant flow branch for context. The pain point: After checking that reference, returning to the active working frame requires slow, tedious, and imprecise manual scrolling/panning, which is a significant flow breaker. This effort grows exponentially with the size of the file.The Proposed Solution: "Go to Working Frame" ShortcutWe need a dedicated keyboard shortcut to instantly snap the viewport back to the frame the user was most recently editing.Implementation Options (Figma-Specific) "Last Active Frame" Shortcut (Simpler): The shortcut (e.

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

Summary: Add an automatic, togglable "Viewport Fold Line" on extended device frames so stakeholders can instantly see what sits above the fold directly on the canvas—eliminating scroll height confusion during design reviews.The Problem When frame heights are stretched downward to fit long scrolling pages, Product Owners, clients, and non-design stakeholders often mistake the total frame canvas for the initial viewable screen. During reviews, they assume lower content will be immediately visible without scrolling, causing miscommunication around layout priority and above-the-fold real estate.Source of Inspiration Adobe XD solves this natively: when you choose a preset viewport (such as an iPhone or MacBook preset) and stretch the height downward, it automatically displays a dashed horizontal guide marking the original viewport height. This clearly marks the boundary between the default view and scrollable content directly on the working canvas.The Solution Introduce an automatic "Scroll

Thanks for adding annotations to Design Mode. I have been spending the last day annotating some new design ideas. People who have access to the Figma file love that they can read come design rationale and interaction behaviors. For others, who do not have access, or do not use Figma it would be great if I can export the annotations associated with objects inside a frame.  Thanks, K.

Feature Request to Resolve Ongoing Library Problem: Allow Swap Library to Replace Local Variables with Published Library Variables I would like Swap library to support replacing local variables in a file with variables from a published library when the collection structure and variable names match.
Today, Swap library only supports library-to-library swaps, which means local variables cannot be migrated directly to an existing published library.
This creates extra overhead because the workaround is to publish the local variables as a separate library first, only to swap them afterward.
 Since variable replacement by matching names already works within a local file, extending that behavior to local-to-library swaps would make migration to standardized library variables much easier. Example:A file has local variables in a collection called “Module 1 Semantic Theme.” That file also has layers using local variables like “Color / Text / Primary” and “Color / Background / Default.” Your publ

Add richer descriptions to variable collections, groups, and modes Figma currently allows us to add a description and scope to an individual variable. However, the description field is a relatively limited text input, and documentation cannot be added to the broader structures that give variables their meaning.Proposed Description LevelsIt would be helpful to support descriptions at multiple levels of the variable system: Variable collections: Explain the collection’s purpose, intended use, architecture, and relationship to other collections. Variable groups: Document how a specific category of variables should be applied and distinguish it from related groups. Modes: Explain the context represented by each mode, when it should be applied, and any important differences or limitations. Individual variables: Retain variable-specific guidance, but provide a more capable description experience comparable to component documentation. Ideally, these descriptions would support multiline

Hi there, I’m struggling with text boxes which are not trimmed horizontally. I’m trying to create single speech bubble with limited width. When the last word in the line doesn’t fit the bubble goes to maximum width and then jumps to another line. I wish to trim it to the actual text width. Do you know a solution which is not manually set every single bubble?

We have a number of websites for which we have a standard format (text and appearance) for our company’s cookie banners and ‘manage cookie preferences’ settings modals across them.Now that we are launching a website using Figma Sites, we would like to be able to customise the text and appearance of the Figma Sites cookie consent banner and ‘manage’ settings modal so that they can be more consistent with our standard format.

Being able to define cardinality between objects in a FigJam workflow would be hugely timesaving when trying to capture relationships within workflows. Additionally, this might allow our organization to give up other cloud collaboration apps and use Figma as our primary tool for this time of artifact.

Allow designers to set one frame/section as the default focus so that when a stakeholder like PM/Engineer randomly opens a page in Figma project, they can see the right things designers want them to look at. A lot of times, stakeholders get to the right frames/sections when links with frames are shared. But then they often navigate to different parts of the file and it is difficult for them to see where to look at in a page. Maybe page level thumbnail capability instead of per file?

Auto-Layout has padding (inner spacing), but no margins (outer spacing). Currently the only 2 ways to add spacing is to: Create a spacer element or Wrap the items in another frame and apply gap spacing This creates a lot of unnecessary frames, and sometimes creates nesting so deep it goes outside the layers panel. Not sure if a technical limitation left this out of consideration in the first few versions of Auto Layout, but it would be much appreciated if it were included in a future version as it comes up as a significant limitation many times a day.

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 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

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.

It really annoys me that Figma automatically creates subfolders when you export an element that’s inside a component and has a ‘/’ naming convention. I always have to go back into the folder and delete the folders or rename everything. It would be great to have a simple checkbox toggle in the exports panel to enable/disable creating subfolders, similar to Illustrator.

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