Suggest a Feature

Figma allows to name a Frame. Yet, it would be great to also have a subheading or small description field between the name and the actual frame to specify the content in more detail for e.g. the engineering team. This would help to make the communication of the content more clear without adding text fields above the frame, which also sometimes get lost when you move and copy paste frames to other places.

Currently moving a component to a library is unnesessarily complex. It could be simply: Selecte components to move. Left click. Click “Move to library…” on the menu. A dialog opens and provides a way to select a file and a page in the file.

Using the rest image endpoint, I can get the image of a layer, but in trying to recomposite the layer, do I don’t want the image to include the children within it. Previously I was using the plugin api, and would hide children, export image, then show children. I’d really love if this end point would support this functionally. Thanks!

make working with variables by mindmap, working with table uncomfortable

Hi, is it possible to minimize the toolbar to get a larger screen real estate? I’m using FigJam on MBP 15" and the toolbar takes quite some space. Maybe we can 1-click minimize or hide it from view? Is it also possible to move the toolbar to the left or right side panel?

i need see preview of assets in properties menu

Would be great to enable updating of a variable in a TeamLibrary from a plugin that is running from another design file that has that TeamLibrary already added please. Currently, I can read a variable from a TeamLibrary using: var variable = await Figma.variables.importVariableByKeyAsync(keyVariable); However, I cannot not update that same variable using setValueForMode: variable?.setValueForMode(modeId,value); I get an error: “unhandled promise rejection: Error: in setValueForMode: Cannot write to internal and read-only node. Are you trying to modify a remote style or component?” Can you please enable updating of TeamLibrary variables remotely? Thanks! Martyn Why: When designing at scale with multiple brands, TeamLibraries enable mastering of variables that are used across multiple brands. It would be useful to be able to update TeamLibrary variables remotely, when working with a plugin in a design file from any of those multiple brands, that have that TeamLibrary file added.

To select deeply nested layers, it is necessary to expand the panel far to the right. Please add the ability to horizontally scroll. It looks like users have been asking for this very basic functionality for four years.

It looks like there’s a border or shadow on the left that works fine in a normal window but is mildly infuriating in fullscreen.

Got really hyped with multi-edit and was watching the tutorial on creating components from Miggi. I expected this ability to also be able to create a component within an existing component, but I’m unable to do that. Example: Tabs are made up of individual tab items and a tab group (which may come with extra stuff). I already have the master tab component made, but oh wait, I want to go back and turn the auto layout of individual tab items (aka the tab group) into a component itself to easier manage that sub-component. Unfortunately, multi-edit doesn’t seem to be able to do something like that within an existing master component. This means I would have to create a copy of the tab group outside of the existing master component and then select each layer (at least this can be easily done with multi-edit now) in the variants of the master component I want to paste and replace. This isn’t a perfect solution, because it can override some of my things like constraints or other stuff I didn’

Hi Team, Greetings! I just had a small idea in existing PRD template in Figma: In What and Why areas, the sections: Purpose and Goals should be interchanged in template. Since it gives more clarity in describing about the product promptly and gives exact meaning the specific sections of template. Figma - PRD Template Hope my idea is valid and you would take corresponding action of change. It would help all the users. Thanks team! Best Regards, Anantha Padmanabhan

Hello, I think there would be two useful points to add for interactions. The first being able to select distance from top an element stickies at for prototyping. – A simple use case for this is floating shopping cart summaries that should sticky below the navigation, not the top edge. The second is being able to select an element to be sticky to the top of the frame it is in. – A use case here, simply can be modals or tables that can scroll and need to sticky something afterwards. Final request would be, an add-on or variant on to the second feature above — being able sticky at top of screen (or distance from top) until the parent frame passes that point, at which point, it scrolls up with its parent frame.

please make “change to” option for nested layers, and any other layers, the same way as you do this for swap instance menu. let me select layer in prototype mode, than make interaction, and select “change to” trigger, after it, select layer from swap instance menu from any variant set (just add swap instance menu there) it can make work easier and it may make fewer variants, i will just make every layer that i want to change by trigger on any layer in any variant set or just simple layer, than “change to”> swap instance menu, choose variant i want to trigger (inside one component set) and animation for it (the same as it work inside anyone variant set). without making a lot of variants with swap property option, and all nested layers or variants from another variant set will change to another variant from variant set, where swapped instance from. it can make interactions between different variant sets work codependent

Hi designers! Our perceived lightness does not correspond well with the lightness attribute used in HSL and HSV, despite those being the most user-friendly and imaginable color pickers currently around. LCH is a color model that improves this perception while keeping the usability and imagination as a picker, and it’s currently being rolled out to browsers as we speak, and it completely solves the perceived brightness - for CSS. I think LCH (or LAB, which is similar) is a game-changer for digital artists and designers, and adding it as a color model to the Figma color picker would save a lot of time discovering colors and iterating on them. Is anyone else interested in this? Do you know about LCH/LAB? What do you think of it? I have found a LCH plugin that helps the issue but it’s obviously not as useful as adding LCH to the actual picker in Figma. Very interested in your thoughts. Cheers!

It’s annoying that I can’t cancel “mark as success” comment functionality with cmd+z. Consider adding this feature, that would be so useful to have control over it.

Hello there, I was in process of wireframing and really thought that it would be a really great idea if, in the shapes icon, we have a “wireframe square” to create automatically squares with those 2 lines doing an X. I think that other programs like InDesign have this feature, but I think it would be really useful in Figma as we also diagram a lot in this program. Another idea is that, in the fill options add another one with those two lines. This way we could easily change this fill with an image while doing the high fidelity or final design. Here an idea about this concept.

Hi! I would love to be able to edit the properties of different components at once. For instance, if I have two components that share some properties (Same name and values), I would be able to edit the properties of both instances at once.

As there are only three options, a dropdown just hides options and adds friction, and if this step was removed I it could save a lot of time over the course of a project!

Hello community and Figma developers, What about adding a selection pannel with media display when changing variants of a component ? I think it would be helpful to visualise the images/icons/illustrations when choosing among a wide range of variants from the variants list. What do you think of this ? it could be a great plugin idea otherwise

Our team shares out Figma files with clients so that they can comment changes on the file itself, however the access can get a little out of hand when we are in the process of updating and client/s are on the file commenting. It would be handy to have a toggle feature that temporarily locks a file (only allowing access to select accounts - designers and devs). Possibly even having a lock feature or hide feature on individual pages within a file, so that other files can be viewed while others will not show up.

I have very extensive prototype actions in my Figma files, whereby a lot of prototype interactions point to a UI element that sits much further away in my file. Whenever I want to edit that UI element (to which the interaction points), I need to move all the way over there (by following the blue line), which takes me considerable time taken together. My work in Figma would thus benefit a lot if there was a way to quickly jump to that UI element. Could this be a feature in @Figma_Moderation Thx

keyboard shortcut request for FigJam. if I have a line selected in FigJam and do ⌘-b it should make the line thicker (or thinner if line is already thicker)

I know there have been threads regarding this before but none of them seem active at the moment so I wanted to bring it up again. This is a major pain point when working with design systems that are intended to match code 1:1. As an example, I got a component that has an “id” text property that is supposed to apply to a nested text label component in one state, and to a nested button component in another state. Using the “expose properties from nested instances” cannot be used in this case because the property would not persist when the state changes. When using a modular design system it is also quite common that the original property belongs to a sub component of a sub component, making it very inconvenient to use the “expose properties” approach. Additionally, passing properties is a common pattern in code. Features like variables in Figma pave the way for building component libraries that more closely match code. But that also increases the need to be able to set up components and

our design team frequently work with the User Journey Map template in the app. The range of features within the product is impressive, however, we have identified some areas for improvements that could enhance the utility and performance of the app. Dynamic Addition of Rows and Synchronization of Notes: Current Issue: We encountered an issue where notes already posted do not synchronize when we add rows to the table. Suggestion: It would be beneficial to have a feature that allows us to group or ungroup specific notes with the frame of the table, giving us the flexibility to move notes around freely. Adaption from Miro’s USM Template: Current Issue: The current template lacks a feature that automatically shifts all other associations when a task is added in between. Suggestion: Similar to Miro’s USM template, we believe it would be very convenient if the tool could shift other linked tasks automatically when a new task is added in the middle.