Suggest a Feature

Formatting like H1, bold, etc. currently aren’t reflected in the hover state of components in the Assets tab. The minimum solution to the problem would be at least not to ignore line breaks.

I would like to be able to bulk edit component descriptions. For example if the descriptions are structured with headlines that are consistent across all components, I’d like to be able to edit those shared text elements in bulk, instead of going through hundreds of components individually.

We have been managing our design system(s) for Desktop, Mobile, and TV applications in Figma for some time now and the experience overall has been great (especially with the updated Auto-Layout model) but one thing that has been extremely difficult to manage are design tokens. When I say manage I actually mean we are not using them because there is no solution to do so between Figma and our actual developer component libraries (Apple TV, iOS, Android Mobile, Android TV, HTML TV, HTML Desktop, etc…). We would love to more widely support themes in our apps and at a minimum use tokens for colors, spacing, font weights, and more. This would not only dramatically help with design speed and consistency but allow developers to more easily translate the components and layouts to real platform components (if you could inspect or export the tokens). Here are a few key items that are quite difficult without first party support for tokens. Color Themes: Without tokens you have to rely on color s

Like in Sketch it would be great if you could get the pixels from a selected object to a hovered object.

Can the transparency be easily set in the color variable when referencing colors here? This is highly desired and we hope it can be supported.

The new component details pane looks awesome, and being able to switch between variable modes is neat. However, switching between say ‘light’ and ‘dark’ mode becomes non functional unless the background behind the component is also able to change. Would be nice to be able to link it to surface-default variable or similar.

When using the prototype features, variables are a great way to allow dynamic designs. Unfortunately, using variables like this gets very unwieldy very fast. Consider this example: I have an radiobutton component, which has a boolean “checked” property. Based on the radio button, I want to change the variant property of a button, which has the variant property “style” with values “inactive”, “active”, and “disabled”. So on each radio button, I need to define something like this: On click: Set Variable “radiobutton-1-checked” to “true” Set Variable “radiobutton-2-checked” to “false” Set Variable “button-state” to “inactive” Even with this minimal example I need to set three different variables so that each component gets its correct state. It would be so much easier if one could apply an expression in place of a variable. Then one would only need to set one variable e.g. “enable-button” to “true” and instead apply the expression “enable-button equal to true” or “enable-button equa

Managing plugins is cumbersome. Your bookmarking doesn’t sync across personal and business accounts Your bookmarks aren’t set to default Some bookmarks appear in the side panel, others don’t There’s general inconsistency in the bookmarking experience Plugins aren’t categorised (which makes discovery hard)

This help page says Any text before the first / will become the component name. Every extra / level will create a new property. Well I waste a lot of time deleting properties and restoring the name after the slash / after I create a variant. I use Slashes for maintaining an Atomic System. This way, it looks like Figma doesn’t want me to have atoms, molecules and cells. 🤷

the text suddenly disappeared.each click will be restored, please help to solve the problem

When exporting frames, can we export the text-only, as opposed to the files being nested into 5 layers? For example, if i am downloading an icon-svg with the frame name to be design system/icons/arrow-up, i don’t want the exported asset to be nested into 3 file layers to reach the asset. Same goes for labeling frames with dates using /. Just want to download the asset with their name intact

It would be really cool if you could merge multiple sticky notes contents with a shortcut. Or to take bulleted lists within sticky notes and convert them into multiple notes.

Please allow us to quickly create a local master of a shared component and replace the current instance with that new local version. Requiring a detachment before making a new component loses all of the variants, etc. of the original component.

Love the new Tables option and it really helps organize and track work. However, being unable to use sticky notes, shapes, community widgets etc in tables prevents it from being used with the rest of FigJam potential. Would love to see this feature be available.

Sometimes text do not fit into default shape size. Such shapes feature ellipsis and a drop down to expand the shape. It would be great to see full text on hover in such cases, as you might not always want to expand the shape.

Main problem: I often accidentally press cmd + t when i want to just replace content with cmd + R. This is frustrating since this opens the New file window. I always quickly press Cmd + W to close the window and get back to work, but this is not taking me back to my working file but instead switches to a (random?) file in my tabs. So two problem here: Cmd + T is too close to a often used shortcut (Cmd + R). Cmd + W doesnt take you back to previously active tab

If I have two files and I can’t decide which file an object/frame/pageg should live in, I’d love to be able to embed a live/syncing view of the frame into another Figma file. I imagine it working like a PS Smart Object where you can double click or something similar to jump to the original to edit it if needed. Right now, my best option is adding a button widget or link to the frame. You could almost do something similar with components, but I feel like it’d end up clogging up the component libraries if used for this purpose. Thoughts?

I have an idea for a new Figma feature. DEAR FIGMAAA, Please make the name of a variant visible above the frames of the components. See screenshot what i mean for concept. I think it will help designers and developers a lot. Current situation is you only see the names of “normal” frames and single components …

It would be ideal to have a comments feature WITHIN the merge review dialog. Similar to other code version control tools (like Chromatic for Storybook), it would be ideal to be able to have a discuss/comment area in-context of each updated element in the merge. Currently, the work around seems like that people have to first find exactly what it is they want to comment on (listed in the Merge dialog), and then go to that object in the file/page/canvas, and comment there? The downfall of that is those comments on the canvas get lost with the merge/branch. In addition, having a description accessible for each branch after it’s been merged, would be beneficial too. Similar to this request: See branch description after the merge Thanks for the consideration, and I recognize that this feature is very complex!

I believe the section’s reaction to mouse is inconsistent. If the entire section is visible on screen, it is highlighted on mouse hovering anywhere inside the section, and it is selected on mouse click. If no section edge is visible on screen, it is not highlighted on mouse hover, and it is not selected on mouse click. But if any edge of a section is visible on screen, it is not highlighted on hover, but it is selected on mouse click. I’m so much used to clear the current selection by clicking on the whitespace, this is a second nature to me, and I do it without thinking. The current section behavior makes me constantly check if the section got selected when my intent was to clear the selection. Considering that every other selectable canvas object in Figma is highlighted before being selected, you can always tell if a mouse click is going to select that object. Section makes an exception here for no reason.

I hope that within a file, one or multiple frames can be set to ‘visible to me only’. Regardless of whether the person who created this frame is the original creator or a past editor, any frame they establish and designate as ‘visible to me only’ should solely display to them and not be shared with other collaborators. Please take into consideration challenges related to changes in user permissions, as well as issues of file duplication, cloning, and how this type of module might be compatible. Apart from frames, the same applies to pages within the file. However, the number of pages is constrained by your policy of allowing only three free pages; it might be worth assessing its commercial potential. Lastly, I’m looking forward to the smooth launch of the ‘visible to me only’ feature for frames and hope it will be available for free use. 希望在文件内，某一个或多个frame“仅自己可见”，无论创建此frame的人身份为创建者或曾是编辑者，自己创建并设置的“仅自己可见”frame，将只对其自己展示，不对其他协作者公开，请考虑用户权限变更或文件复制克隆等问题，以及该类型模块如何兼容。 除frame外，文件内页面pages也同理，但是页面

Addition to the current variables Add and manage multiple sharing links for different modes Restrict mode view access per link (e.g. a client is provided with the link that has their brand theme mode) Great for white labelling

Why can’t I connect to the team component library after creating a new project?

AUTOMATIC FIGMA TUTOR 💡 Create a step by step interactive Figma tutorial from a Figma file or component Similar to: ScribeHow (creates tutorials by tracking what button was clicked in the website) but in Figma Pros: create tutorials for a certain component using its version history from contributors (Figma community or others) easily follow step-by-step tutorials of trendy design components in Figma points & highlights which button to click in Figma along with an AI text generated instruction share interactive Figma tutorial with others Impact Increase the number of tutorials, tutors and contributors in Figma Easy access and sharing of tutorials to the public Market Opportunities easy creation of tutorials meant an increase in number of Figma tutors selling interactive Figma courses possibly on the Figma community or on this “imaginary social platform” Possible Issues: Unnecessary changes may be recorded and might hinder tutorial process Some changes may be lost in

Currently when the gradient window is open the shortcut doesn’t affect the object, so it could be used to flip the gradient instead. In some scenarios it could also be useful to flip vertically. Both shortcuts could work on bitmap fills too.