Suggest a Feature

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.

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.

Problem As a front-end programmer I don’t quite grasp the current concept of so called “Local Variables”. For starters, they’re not local, but global. And the thing with global vars is - they make a big mess, like always. For this reason any programming language considers global vars an anti-pattern. But currently, the only way to make a Figma component “stateful” is to keep its “state” in the global namespace. I use quotes for a reason: there is no real state at all, because in Figma there is no an entity like “state of a component”. This all makes flows unmaintainable and prevents us from transferring components between files and projects, because they get transferred without their “state”. So basically you can’t easily reuse components logic. It also doesn’t provide any level of isolation. For example, if I have more than one instance of the same component, how would I distinguish their variables/state

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

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 exac

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

Currently, you can only set the default mode of a workspace by enabling the library for everyone in the workspace. It would be helpful to be able to set the default mode without enabling it for everyone. The use case we have is that we have two different libraries. One library with all of our theming variables, and one with just the semantic variables we want our designers to use. We do not want all designers to use the theming variables library but the theme is controlled by that library. Can we please add the ability to change the default mode without enabling the library?

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

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.

Figma’s variables feature is a game-changer for design consistency, but what if we could take it a step further? Imagine a seamless connection between Figma variables and SCSS, enabling real-time updates across design and development environments. Here’s how this could work: Proposed Features: Export Figma Variables to SCSS: Designers can define variables (e.g., colors, typography, spacing) in Figma. These variables can be exported as an SCSS file with proper formatting. Example: scss $primary-color: #FF5733; $secondary-color: #C70039; Sync Updates from Figma to SCSS: Changes to variables in Figma automatically update a connected SCSS file. This enables design updates to reflect in development environments, at least in staging or development builds.

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.

Hi! Currently, when you click on a stroke in the right side panel and then Command+C copy it, then go to Command+P paste it on a different layer, the only properties it copies over are the stroke colour and opacity. Would be great if it also copied over the stroke width, position, and side customization 🙂

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?

I’m in a position where I would really appreciate the ability to add meta-fields to objects that would transfer along with SVG exports. (Long story) You could write them under a specific namespace along with other SVG attributes. Besides string values, the ability to store a reference to another object in the SVG would be nice also (i.e. linking functionality between certain pieces) I’m now thinking of a naming scheme to implement these, but a native support would be swell.

Underlines have been broken since I started using Figma when it first came out. It is the only thing that frustrates me (this program is perfect in every other way, seriously). There have been several tickets opened about it that were auto-closed due to inactivity: Text underline "ink skip" Fancier underlines for links Type setting for underline to ignore descenders The basic problem (and I will re-use an image from that first link, thank you @jdb) is that descenders (seen on glyphs like “g” or “j”) are overlapped by the underline in text elements. The top example (wi

We have a typography section when we want to scope variables. What about a Layout Grid section in Scoping mode? Here’s a simple Photo for maybe a better understanding: Wouldn’t it make the work a little bit easier/more comfortable/better? Even if it is just a 1% improvement.

The Interaction details modal is not very tall, making that extra scroll mandatory to set up custom bezier EACH time we create a Smart Animate animation which is probably 100000x a day . It would be a time-saver to just make that modal higher. We use very large screen in our office and this window could be at least 3 times higher and still have space under it 😅.