Share Your Thoughts

While working to build out our design system with variables, it seems like there isn’t an easy way for developers to view a full list of all variables built into the design system without having edit access to the design system or without the variables being put into a different reference system like a notion page as the master file and have Figma reference those values.

To enhance flexibility and optimize workspace organization, it would be beneficial to allow users to move the windows for variables, prototypes, and plugins outside Figma’s main interface, positioning them freely on the desktop. This feature would help users better arrange their workflow, especially for those using multi-monitor setups or needing a cleaner and more focused workspace. Imagine being able to place the prototype window on a secondary monitor while working on the main canvas, or keeping a plugin window open without it interfering with your design. Additionally, these windows could remember their position, reopening in the same spot during the next session to ensure a seamless user experience.

Editing comments quicker with up arrow to go back to the comment box once it’s been sent

On a regular basis, whenever I have to move a file, I click on “Drafts”, thinking that it will let me move the file. But, this takes me to all Drafts, which I understand is probably the desired state for when the file is in a correct project folder. However, this drives me crazy every single time that I try to move something from drafts, which happens regularly given I create files outside of projects most of the time. Would love consideration on changing the Draft state for moving. 

In this case I have the same component duplicated four times to have five placed instances total. When selecting one of the inside pieces, Figma highlights those same pieces in other parent instances. But there’s no way to select those things Figma’s highlighting without intermediate steps like searching by name. Clicking them all one by one in this example isn’t too bad, but doing it with some nested component across a dozen prototype screens is pretty bad. It’d be really cool if I could hit some keyboard shortcut or a quick action to go with the existing “select all ” options. (Select all with same instance doesn’t work, it selects all the parent components instead of the highlighted pieces) With it already being highlighted, it feels so close yet so far.

Hello,I’ve been and building with Figma Make which I find very impressive.By iterating, a lot of files has been created and many are not in used which leads to pollution and model confusionCan you build an UI in the interface or give possibility to the AI to delete files? 

STOP MOVING THE TOOLS AROUND THE CANVAS, CHANGING THEIR ON-LOAD DEFAULT VIEWS, AND GIVE COMMUNITY AN ACTUAL PLACE TO LIVE OTHER THAN EVERY SINGLE PLACE YOU’VE TRIED. HOLY CRAP HOW ARE YOU GUYS GOING IPO? YOU CANT EVEN MAKE A SINGLE DECISION AND STICK WITH IT FEATURE REQUEST: CONSISTENCY AND RELIABILITY. I DONT USE POWER TOOLS THAT ARENT RELIABLE, SO WHY SHOULD I USE A PIECE OF SOFTWARE THAT DOESNT RELIABLY HAVE THE FUNCTIONS I NEED IN ONE SPOT

Currently what we make in “Figma Make” is not directly editable in figma design tool. To change anything we need to command which makes the design worsen often. So we designers need to have the power to copy/move/cut from “Figma Make” design and paste it in the figma design tool , to iterate and tweak faster.

We deals with editing of photoshoot, website,and app design

Recently, I needed to create some typography based graphics in my website project, I did not find any option to align the text to pen paths or shapes. It would be a must feature in Figma as the usecase prevails for many designers out here and in many projects. Yes, there are some extensions available but they are limited in functionality, do not provide necessary mechanisms. Please upvote this of you have came across to the same need.

Flow chart process mapping is good. Adding line jumps would make it great!

Using string variables as a “CMS” across multiple teams is great to achieve consistency in ux writing/labels etc. If only it was possible to use markup within the variables. Because sometimes i run into a textbox where I want to format part of the string as bold, italic, underline … the usual suspects. With the way string variables are currently set up I can not cover this case with them. Hence, it wold be great if some kind of markup support was added. Marry Christmas ;]

Our design system leverages mix blend modes for hover states so our icon buttons appear on any background color and remain accessible, without needing separate hover–on-primary, hover–on-secondary, etc tokens. We use multiply for light theme, and screen for dark theme. It would be really awesome if we could apply blend modes directly to the color variables, OR support blend modes as variables in general. Our current work around is to apply the blend mode directly on each component variant, but this requires us to define separate light and dark theme variants. would be great if we could use variables here to have it automatically switch between light/dark.

Automatically add page numbers to the selected slide in Figma based on Slide position. Maybe we can select any text and give it the numbering option?

Config 2025 release broke my designs with Grid!And it could be an upgrade, if:Grid could HUG CONTENTS (row, column, grid itself) Rows, columns and cells could be resized (fixed value, %, colspan/rowspan, flex-grow value) Switch between flex wrap (items jumping to next row) and grid

Team,Why can’t I use a component set as an overlay and specify the variant I want to choose? Friends? Please. Otherwise, I have to make an instance that just sits there strictly for overlay. Same thing with  navigate to, really. Disorganizes the file and makes it “heavier” than preferred. Please, fix this.

The versioning in Figma Make is available, but since the AI cannot maintain consistency if there is a way to list and name these versions, it will be easier to fix the mistakes and issues.

Add the ability to select which properties to publish of a component and of a nested component. One use case for this is State in many components such as Button. State has Default, Hover, and Pressed. These states don’t need to be published, they are purely used for prototypes. I don’t want to clutter the properties list for consuming designers. Disabled and Error are created as Variants with “true” and “false” values. There’s no need to publish State property. Original idea here requested by XavierV

As a designer using a design system and searching or swapping a component instancr, often a term you search pulls up other components not in line with what you want because of a similarity in name. The most common culprit are icons.It would be great to do a quick negative filter like in VSCode with find and replace when looking for components to swap or insert to negate a group of components. This could also be a quick hack to cut out other active design systems from the keyboard.

Would be nice to limit this permission to developers only, while still allowing other roles to view files. It is about time Figma improves the role and permissions management. We need dev roles or more granular permission settings.

We’re working on a larger Component library that includes non-published components (components with the prefix _ or .) as base components in order to simplify large, complex components. We intended – in some specific cases – to offer regular components as templates, that a designer would then have to detach and work with a bunch of base components to build the desired design. What we have come to realize with this approach, however, is that these non-published components don’t receive updates from the library when they are updated in the main library. Is this intended behaviour? We basically have the option to simply publish these base components as regular components, but that of course would mean cluttering up the assets overview with a bunch of modular components.

As a designer I would like to record my prototype screen or export it as a gif so I can use it in presentations and send quick examples in the team group. It would be great to have the same feature then Principle to record or export the prototype to gif. Does anyone have the same need? Is anyone using a plugin or workaround to help solve this?

It’s currently too easy for contributors to make small changes that go unnoticed by maintainers. Especially in large files, there’s no way to track exactly what changed. Enforcing that the main file cannot be edited unless you branch will allow maintainers to view exactly what has changed and require reviews of contributions.

I wish there was a right click option if Figma that lets you select any item on your canvas and lock it to sticky, so the reference can follow you as you pan around, just a simple “make sticky” and you can still move it around if you need to adjust where it is “sticky” from. aaagh.

Currently trying to pan with spacebar is not working in many scenarios because other areas of the app are “in focus”. This is super annoying because you always have to click inside the canvas to get focus to be able to pan again. However, this selects or deselects elements which is almost never wanted.Even when in prototype mode and an interaction is selected, paning doesn’t work, even though the focus is in the canvas area.Also super annoying, when clicking on a comment, the focus goes directly into the reply input. So pressing spacebar to pan results in a comment consisting of a lot of spaces.This is super annoying and costs a lot of time accumulated during the whole day. Please make spacebar pan work always! No matter where you focus is, as long as the mouse is in the canvas area. Or at least include a setting to control the behaviour.Thanks!