Skip to main content

Suggest a Feature

Got a feature request or product idea? We're all ears!

  • 4,533 Topics
  • 26,467 Replies
4529 Topics
S
Figmate
seniManager, Community Support
posted in Suggest a Feature
READ ME: How to use the Suggest a Feature category?

We’d love to hear what feature requests, ideas or improvements you have in mind for any of the Figma products you are using. Note: If you have feedback on an existing product or feature, head over to the category Share Your Feedback . Sharing product improvements and ideas Our teams look at ideas and feature requests across many different channels throughout the product cycle and it has truly helped make Figma a better product. With that said, we want to make sure we set some expectations for how feature requests, ideas and improvements will be handled in the forum. We cannot make any guarantees or promises that you’ll see your idea/feature request/improvement implemented into the product Our team will merge topics with the same/similar ideas to keep the forum organized Inactive topics that are 12 months or older may be closed or archived to help keep the community organized and healthy Voting on topics At the moment, it is not possible to vote on topics. This is a feature we are revie

5590
S
Figmate
M
Myrto_Stoop1
posted in Suggest a Feature
Custom content slot

Whey I design a dialog component with a content slot, I’ve to create a content component to drag into. Doing this for several slots will declutter my canvas. It would be great if you could add custom content directly within a “slot”, without the need to create a component for it. … Like a dedicated slot where you can add content directly by clicking on it.

2862
Corey_O_Brien
_logeast
_logeast
posted in Suggest a Feature
Add a "slot" functionality to components

My suggestion for Figma is to add a “slot” functionality to components. This would allow designers to create more flexible and customizable components, by adding empty slots or placeholders within a component. Users could then insert their own content or elements into these slots, without having to ungroup or modify the component itself. This functionality would save time and increase efficiency for designers, while also promoting a more consistent design system across a project or organization. I believe this feature would greatly enhance the flexibility and usability of Figma’s component system, and would be a valuable addition to the platform.

639134
Corey_O_Brien
Ryan_Lutz
Ryan_LutzNew Member
posted in Suggest a Feature
Feature Request: New Override Type – "Child" or "Slot"

Context and Problem Figma's current Instance Swap Override is a useful feature for swapping singular instances within a component. However, it becomes cumbersome and time-consuming when applied to more complex design patterns, such as: Managing dynamic content for cards, sidebars, and templates. Creating unique combinations of content within reusable components. Currently, designers must create a new component for each unique content combination, which leads to bloated libraries, repetitive work, and a loss of efficiency. This approach also lacks flexibility for managing dynamic layouts, which are more naturally represented in code through structures like parent-child relationships in HTML or Children props in React. Proposed Feature: Component "Child" or "Slot" Override Introduce a new override type, referred to as "Child" or "Slot," allowing component creators to define designated areas within a component where users can **drag and drop any content**. This feature would streamline th

141
Corey_O_Brien
Aalok_Trivedi
Aalok_Trivedi
posted in Suggest a Feature
Create Folders/Categories/Tags for files

Organization would be immensely helpful if we could create folders for our drafts. I want to be able to organize my drafts into different categories (such as UI kits, Ideas, Wireframe kits, iOS, Android, etc…) so I can find files easily. Right now, the drafts page is a huge jumbled mess and I can’t create Team pages for everything. Maybe something as simple as being able to add ‘tags’ to each file, similar to Zeplin.

73391276
ry.jones
Lena13
Lena13
posted in Suggest a Feature
Enable push/pull of elements below a resizeable component

Hi all, I am wondering if it is possible to enable a “push/pull elements below”-function. In my current case I have an accordeon component that changes size based on what instance is selectet / interacted with. Below this component sloser to the bottom of my screen are texts and other elements that are currently “overwritten” by certain expanded instances of my accordeon. In my previous job I worked with Axure and there one can simply select “push/pull widgets below” when adding interactions to a component and all elements on the screen below will be pushed/pulled by the exact difference in height of changed component. Is it possible to add this option in Figma? (I know I could just add all other elements to my component but this would blow up said component way to much and seems unnecessarily complex)

1663
Mike_Scarpiello
A
Andii_Hei
posted in Suggest a Feature
Quality of Life Improvements for Variables

First and foremost, I’m really enjoying using and experimenting with what I can do with Variables. I have barely scratched the surface but feel like these are obvious improvements that should be included in the backlog somewhere: Ability to duplicate Variables Ability to duplicate a Collection Ability to move Variables to another Collection Ability to move a Group to another Collection Ability to move multiple Variables (between Groups and Collections) Add a description for Collections and Groups (I don’t want to repeat the same thing with slight variations for each Variable) Ability to search for a Variable or Group within the Variables window Ability to move the Mode columns within the Variables window [EDIT] When creating Color Variables, I wished that it remembered the last panel I used to create the previous Variable. This would be useful when I’m creating multiple semantic variables via aliasing [EDIT] Ability to scope multiple Variables that are of the same type Thank you so muc

193732
Desislava_Slavkova
Carlos20
Carlos20New Member
posted in Suggest a Feature
Set grid row height to "hug" contents

I was super pumped to start using grids for my layouts until I learned of one fatal flaw that killed my excitement :( The inability to set a row height to hug is simply a deal-breaker for me. Also no variables support for gaps? really?

1307
Cindy_Wong1
Camila_Amado
Camila_Amado
posted in Suggest a Feature
Navigate to child components

Just like we can navigate to the ‘main component’, I would like a functionality that takes me to all the children of a main component. Or does something similar already exist and I’m missing it?

1975
Colleen31
D
Dan2New Participant
posted in Suggest a Feature
Control variant export naming (especially for icons)

When exporting variant names, the file name becomes a combination of all the variant properties. There is no way to control the variant export name, which is especially difficult for developer hand-off. In this example, I have a back icon variant group (Named “Back”) containing both an Apple and an Android variant of the back icon. If I then go to export the Apple variant as an SVG, The variant export name then defaults to “OS Type=Apple.svg” It would be even worse if I had multiple properties. For example, having two more properties could result in a variant name export as “OS Type=Apple, Direction=Left, Style=Line.svg” This is a very poor naming convention, especially for icons. What I would like to have is the ability to control the name given to each variant export. In the above example, I would like the Apple icon to export as the name “back.ios.svg” and the Android icon to export as “back.android.svg”. This way, our developers can export assets as needed directly from Figma witho

1173548
Maya4
Karsten_Muller1
Karsten_Muller1New Member
posted in Suggest a Feature
Scroll-to action in overlays

As written in the documentation (Prototype interactions and animations) the destination of a Scroll to action can only be an element of the same top-level frame. But with this limitation it is impossible to prototype a common navigation pattern. On one-pagers there are often floating menu for intrapage links. E.g you have an hamburger icon that opens a menu overlay from where you can scroll to a specific page section. This can’t be realized with an Figma overlay because of the restrictions mentioned above. There is a workaround, but it seems that it only works because of a bug: You can set the menu overlay as an child of the top-level frame of the one-pager, define the Scroll-to actions and then move the menu outside the frame (as an separate top-level layer) to show it later as an overlay. By doing this all the Scroll-to actions still work, but when you change an action the target will be rested and the navigation is broken. Working Example Maybe you can remove the restrictions that t

34488
EmberN
Aretha Alves
Aretha AlvesNew Member
posted in Suggest a Feature
Chart Creation Tool

Hi! I would like to suggest a feature for creating and modifying graphs/charts natively on Figma. I design a lot of dashboards on a daily basis and unfortunately, each chart I encounter, I have to manually create and then use them as just placeholders (and sometimes the devs and stakeholders really need to see the real numbers on the designs, and it takes a lot of time to modify them). I would love it if there were a tool on Figma that allowed us to: Create (at least) pie, donut, line and bar charts; Export and import the chart data as .csv; Modify chart data and have it changed in the chart design; Apply styles and variants to the chart design; Enable chart legend. PowerPoint and Adobe Illustrator have this type of functionality, so it would make sense to have it on Figma too.

20
Aretha Alves
A.J
A.JNew Participant
posted in Suggest a Feature
Tables for Figma

It’s the year 2023, and Figma still doesn’t have native table support. I just spent 30 minutes re-jigging all the “cells” in a four-row, six-column fake table because I had to delete one column, add another, add icons, and then manually re-fit/resize all the cells to get things to align properly. I can either fake a table row with a horizontal autolayout, or fake a table column with a vertical autolayout, but it’s still not a table. I want the ability to create a special frame called a Table, that: has an arbitrary number of columns and rows auto-resizes columns evenly based on content width has one or more Header / footer rows can scroll with overflow content (optional) has optional properties for hover / click states (cell, column or row) has optional properties for alternate-line shading can toggle columns or rows to hide as needed can merge or split cells as needed can set text alignment for a column (center, left, right, or currency / decimal) can set to automatically use monospac

158512
Aretha Alves
Blastola Cola
Blastola ColaNew Member
posted in Suggest a Feature
Make Annotations visible to everyone

I was going to praise how neat the new Annotation feature is, when I realized the content is only visible to Dev Mode accounts. Are you serious? I understand you want to limit creating annotations to certain seat types, but viewing annotations should be a viewer-level feature. Come on Figma, there are better ways to convince your users to pay for a subscription. This is such a crooked move.

151840
Willow_Shelley
Yezgi_Baha
Yezgi_BahaNew Member
asked in Suggest a Feature
Ability to add/remove/re-order items in an auto-layout component

This is a reference to a topic that was closed without resolution: Reorder objects in an autolayout component instance. Allow for order overrides Share an idea Reorder objects in an autolayout component instance. Allow for order overrides. Allow users to reorder (drag or arrow) objects inside a component instance that has auto-layout on it. Especially useful for components that have repeated elements, such as a dropdown menu or a group of form inputs, navigation. This would be much quicker than manually changing each of the elements in-between where the current element is and where the new position is. Or for users that don’t have patience and break… I can’t express how frustrating it is when a designer has to detach one of your components simply to add a tab in-between existing tabs or a dropdown option above existing ones. When I build a component I shouldn’t have to create 10 hidden layers as placeholders to make sure that the component works for a design with 2 dropdown options or

9587
Lee Costic
kukapishixdd
kukapishixdd
posted in Suggest a Feature
Allow us to dock/move the new UI3 toolbar

ngl, the new ui3 is pretty good. the only thing i dont like is the toolbar position. im still not used to it. maybe add an option to move it to the top?

6328176
Uhl
George_Yiakoumi1
George_Yiakoumi1New Member
asked in Suggest a Feature
Grid variable gap support

I dunno if this is a bug or an oversight, as it seems very odd that this wasn’t implemented at launch, but can we add variable support to Gap row/column in grid? :)

00
George_Yiakoumi1
Martin_Marinov
Martin_MarinovNew Participant
asked in Suggest a Feature
Multiuple strokes and stroke offset

Can somebody explain to me what is the point in having multiple stroke layers when they: SHare the same size Share the same offset And another question is is there any way of doing offset to a stroke or drop shadow? I really need this for our focused state in our design system and what I found was only wanky workarounds...

00
Martin_Marinov
Shukri_Brewer
Shukri_BrewerNew Member
posted in Suggest a Feature
HUG or FILL mapped to a variable?

Is it possible to map the HUG or FILL to a variable. It would be great to not only assign particular width values, but also set the width to either hug or fill the container.

4426
Tascha
Polina Cheremisinova
Polina CheremisinovaNew Participant
posted in Suggest a Feature
Add text replacements for naming properties and variables

As a user of variables and variants - I'm really tired of writing the same words a hundred times in every new project when I create and name typical elements. It would be great to have some sort of auto-suggestion (like on phone keypads or programming apps) or text replacement for typical elements like buttons, devices, component states (hover, disabled, etc) and so on. Right now I'm using the macbook's internal function, but I don't like this solution because it bothers and irritate me outside of figma :) For now, I'm using abbreviated versions of words to speed up the naming process.

00
Polina Cheremisinova
Meghan_Rose1
Meghan_Rose1
posted in Suggest a Feature
Add searchbar to variable panel

When you have alot of variables it would be nice to be able to search for specific things

156531
Carlo_Gaudreault
evgenypyvovarov
evgenypyvovarov
posted in Suggest a Feature
Stop automatically adding FigmaAgent to Login Items

I don’t use Figma all the time, I don’t want it to run anything on startup. It’s frustrating to manually remove Figma from Login Items, since it automatically adds itself there again. It would be nice to have at least an option to disable it in settings, or even better - remove that functionality at all, since it’s not user friendly. I want control over what and when the apps do at my workstation. P.S. If it’s needed for updates check - I’m more than okay to update on app start

1195881
Patrik Sjöberg
Eli
Eli
posted in Suggest a Feature
Stroke offset

It would be very useful to have the ability to offset a stroke. For instance, in the case of the focus state for buttons and other components. Currently, there is a workaround, but it is not very convenient as it requires us to manage shadow and transparent stroke. This is especially inconvenient for a large library of components and complicates developer handoff.

11839
Matze
Thomas_Nabelek
Thomas_Nabelek
posted in Suggest a Feature
Use inverse of Boolean variable to show/hide layer

This has been mentioned here: Hide layer using variables - #5 by Andreas_Braendhaugen1 Invert boolean variable for layer display - #14 by Desislava_Slavkova Inverted Boolean Property - #2 by drewcovi_usb but those topics are all closed. I am looking for the availability to HIDE a layer when a Boolean variable is TRUE and SHOW it when it is FALSE. So, the inverse of the default/current behavior. I want to do this without using components. Use case: When a variable is true, show one frame. When that same variable is false, show a different frame. I can get basically this by using two different variables: but it would be more convenient to be able to do it with just one. Just give me a Boolean toggle when the variable is used to say if the variable should be inverted or not.

249723
Yuanrui_Li
Ryan_Leichty
Ryan_LeichtyNew Member
posted in Suggest a Feature
CSS Outline and Outline Offset

Figma should add an outline and outline offset property similar to the properties in CSS. This is useful for focus styles among other things. Currently, there are a number of approaches that you can take to achieve a similar effect, but neither is ideal: Drop shadow: one problem with using drop shadows to create a focus outline is that you have to have a fill. Absolutely positioned frame: you can add an extra frame within an element that’s absolutely positioned and apply a stroke. This isn’t ideal because you’re required to add an extra, unnecessary frame to every element that you want to add an outline to.

130310
Aretha Alves

Solved topics

Trending tags

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings