Suggest a Feature

I understand the idea behind reorganizing the action bar and making the component settings appear first in the list of actions. Still, it really annoys me that position control changes place every time. I need to make an effort to find it whenever I change the element selection. So I think that allowing users to customize the location of different actions in the right action bar will be useful. This allows you to organize the list as you prefer, making it easier to utilize in future tasks.

Hi everyone! If I am in “presentation mode” and I notice that there are problems on a particular page, I have to go and look it up on the template to fix it. It would be interesting if the cursor we have in the presentation could represent where we are even when we go back to the worksheet. So that we don’t have to look for the page, but know where we are! It would make the work much easier!

Hello! Is there a way to cache a prototype thats embedded in Slides, when presenting? Let’s say I present in slides, click each slide that has a prototype, and load it, and return to the start of my slides. When going back to each slide with a prototype, it has to reload. Instead, can we cache the prototype, once you click it, and if we need to update the iFrame to pull in changes, we can by like some button in slide that says “Update to latest” or something? 🙏

Would be great to give the Updating Assets alert a greater visual contrast as in dark theme, it’s hard to see it appearing.

Hate to say it but wow for a design company the Figma UX is tragic. Just realized that after 2 years of using it one of the docs we have been using is in my “personal” account apparently, and our company account billing stopped? That account is now “locked” So I wanted to find what card it was billing against and… there is NO WAY I can find to figure out how it used to be billing. The ONLY thing I can find after far too much time trying to figure it out is to just add a new payment method?? Seriously. Too painful to even bother at this point. I’ll just stick with the free account until I feel more like dealing with this awful UX.

For the files search, it would be helpful to focus the search within the context of a specific project (or projects). Background: We have projects for each platform (e.g. web, iOS, Android, etc) which are in progress and other projects for features that shipped or were archived. So it would be super helpful to limit the search results within one of those projects that represent different contexts (shipped/archived, active, etc). Anyone else have a similar model and found a workaround? If not, upvote this baby 👍

Standard user behavior (even in such a simple platform) is ability to resize text boxes by both width and height. Feels very limiting right now and as you add more text boxes, you end up with a lot of overlapping boxes because the height can’t be resized after creation.

Suppose there are multiple frames in one frame. there should be an option to convert the frames into objects or rectangles with the same properties.

Could be great to be able to resize element by frame rate, percentage, viewport ratio, etc. aligned with CSS possibilities.

When we select two layers from the top and bottom and press Ctrl + [ or Ctrl + ] to adjust the positions. These two layers should come closer like in photoshop and move upward or down. Unfortunately, these layers maintain their position (with extra layers in between) in the frame and move around.

Problem Description The Issue: When naming frames or layers in Figma with special characters such as /, Figma interprets / as a path separator. This leads to the following problems: During PNG or other format exports, Figma automatically creates nested folders instead of exporting all files into a flat directory. Designers who use / as part of their naming conventions must manually adjust or reorganize the exported files, adding extra workload. There is currently no option to disable or customize this path-separating behavior, forcing users to manually rename layers or rely on plugins. Impact: • Workflow efficiency is reduced, especially for designers who frequently export and manage large volumes of assets. • Using plugins or manually renaming layers can disrupt the semantic meaning and consistency of naming conventions. Proposed Improvements Add an Option to Disable Path Separator Logic • Provide a setting allowing users to disable the interpretation of / as a path separato

While it is possible to stack different stroke colors, they all have the same width, which limits their usability. Adobe Illustrator has the ability to stack several strokes on one object, all with their own properties. This allows for example for lines to have «halos», which can be useful when used in front of busy backgrounds.

For example, let’s say that I have a design system with the following color configuration: If I wanted to change the hue for my “secondary” color, I have to manually go inside all of them and change their hue, individually. I’d love to be able to set a variable “secondary-hue” as for “255” for example, and if I used that in the color picker hue field, I’d just need to change my “secondary-hue” variable and it would apply across the whole variables using that. If you have a technique that functions in current Figma settings, I’d love to hear. Thanks!

UI3 is missing go to main component button is missing, and leads to mistake of creating new component. Can yall bring back the Go to Main component button in the UI? instead of hiding it? This is useful when making updates and refining my designs, where I make updates to main component, then look at locations where it’s applied. I can no longer quickly reference main component.

It would be helpful to have a history view of a particular object/asset in a design file where I can right click on it and see that objects history only.

Hi! This might be overreaching and quite niche in its application, most probably only effective for centered-but-truncated Texts like Material 3.0 Tabs (but not limited to it)… Is it possible to add another setting for Height/Width that allows the said object to show a behavior close to ‘Flexible’ encapsulated Flutter widget inside Autolayout? This might be a bit contradicting, but it behaves like Hug and Fill at the same time. When the Autolayout resized from its inherent Hug size, it has two behavior: If the Autolayout size is reduced and the object’s size is also reduced, the object behaves like Fill, as in it will resizes itself according to the space left inside Autolayout. If the Autolayout size expanded, the object behaves like Hug, as in it will retain its inherent (or fixed) size and let the Autolayout’s alignment do its work. As far as I explored, the behavior is exactly like when you set an object’s Max Height/Width to its inherent/initial fixed size (like Hug) but also se

I have built a simple plugin for my organization to generate our best practice Figma file boilerplate. I would love to be able to take advantage of the new page dividers feature, but if I use the API to edit the name of the page to something like ‘—’ it doesn’t turn into a divider like it would from the UI. Feature requests Add ability to create dividers — Figma.createDivider()? Turn pages to divider if name is changed to “—” or similar like in UI

Hello, Currently, when I connect blocks with straight connection lines in a way: Line from D to H overlaps G block. There is no option to connect to a specific side of a block (top, bottom, left, right), like it is with curved connection line: <An error occurred: Sorry, new users can only put one embedded media item in a post.> I propose to add an ability to connect straight lines to points on the each side of a block rather than to the center of a block to avoid overlaps and to better manage connection with straight lines. Please consider this request.

Would be great if I could add a sentence or two of context to files so that, when I’m looking at the thumbnails in the Recents list or looking at files in the sidebar, I had a little more information to help me determine if “that’s the file I need”. Right now, it’s a lot of squinting, opening files, realizing it’s not the right file, going back to the list, rinse and repeat. Little snippet of text would help a lot.

When I upgraded to macOS 15.1.1, I noticed that the plugin area became very small. It seems to be caused by a web adaptation issue, as it cannot stretch to the bottom.

When building components, there are certain properties that I do not want users to modify themselves. For example, in the case of a Button, I only want users to change its state or style by toggling the properties I provide, but I do not want them to directly modify the Fill, the Stroke and so on. Is it possible to add a style locking feature during component creation to restrict users from modifying the styles?

With increasing complexity in projects and design systems often distributed across multiple files I often find myself having many tabs open. In Google chrome, I highly appreciate the “Shift + CMD + A” menu displaying all the open tabs in chronological order, it would also be super beneficial to have this in Figma. This would allow to: Quickly switch between tabs that are the most relevant (most recently opened tabs at the top) Search for a tab Increase usability with keyboard only (current CMD + #number doesn’t scale as well) What do you think about this?

When working on frames containing scrollable content, I often end up having to toggle clipping on and off to switch between editing the content and preparing for prototyping. It would be amazing if we could have an option that made “Clip content” apply only in Prototype mode and not in Design mode.

Working with large design systems in Figma can sometimes lead to heavy memory usage and slower performance, especially in complex projects. To address this, I propose a Child File System in Figma, where child files are separate yet linked to a master file that holds all styles and variable declarations. This concept is similar to WordPress child themes and would enable better performance and management of large design systems. Proposed Features: Master and Child File Relationship: A Master File serves as the single source of truth, containing all styles, components, and variable declarations. Child Files link to the Master File and inherit its styles, variables, and components without duplicating them locally. Selective Syncing: Designers can choose which parts of the master file (e.g., specific components or variable groups) to sync with child files. Child files can override certain variables or components for specific use cases while maintaining the connection to the master fi

For components that have a lot of component properties, it can be a real pain when you add another variant later on. If you have already arranged your component properties into an order that makes sense, adding another variant to the component messes up the order of component properties. So please can Figma respect the existing (user-defined) order of component properties when you add a second variant to a component?