Suggest a Feature

Please add Gabarito, a very clean font available on Google Fonts.

When you format a component description (bold text, lists, etc), that formatting is only visible if you hit “show more” on a variant’s description. If you just look at the short version of it (2), everything runs together in one line, no breaks. And if your description is very short - not long enough to trigger the “show more” link - you never see the actual, formatted description, because again, hitting ‘show more’ is the only way to see see the full description. As far as I can tell it’s impossible now to have line breaks in that abbreviated description, which makes it look kinda gross. How I’m formatting this description: 2: what you see in the abbreviated description: 3: You have to hit ‘show more’ to actually see all this

I have some issues when I call the icon from the component, with a different variant it will be mirrored. I have no idea what’s happening.

Simple, easy and straight forward: whenever I create a personal token from Home > Account > Geneate new token the lack of a copy button makes me itchy: Just add a simple copy button inside the input, and make me life easier ❤️

Hi everyone. Is there a way to insert a vector ( a shape, line or icon ) in a text paragraph and make it flow with the text? Some of you might be familiar with InDesign, which has this feature.

Allow to write variables and style names in the fill and stroke input box, without having to go to the styles panel.

A useful context menu item that celverly breaks a textbox up into separated paragraphs inside an auto layout, allowing the user to easilly add content like images etc into a website flow, also making inporting body copy much easier.

Hi Everyone… This is something I came across lately. If you set a master component to reveal the properties of a nested components, it works well until, in the instance, you swap the nested component ( which has indeed a swap instance property ). If you do so, exposed nested component properties disappear. It would be good if the instance retains the ‘expose nested property’ setting even if you swap the nested component. Whatever property the swapped nested component has, it shows if the ‘expose nested property’ setting is ON. I hope it makes sense? Thanx!

Hello there, Figma! Can you do us designers a solid 😉 and let us save our font preferences for those pesky missing fonts? 🥴 … We’d love to see what you have in store for us, Figma! 🎩✨ If you’re in agreement, give your vote to save the designers’ precious time! 😀 👩‍💻👨‍💻👩‍💻👨‍💻👩‍💻👨‍💻🧑‍💻👩‍💻👨‍💻👩‍💻🧑‍💻🧑‍💻

Hello, if we want to use variables and modes to handle UI themes, we should be able to set them everywhere we can set a color. As requested in other topics, we can’t set variables as gradients steps and we can’t also set color variables as shadows. This prevents any try to switch to variables since no one wants to use half colors as variables and half colors as styles.

When entering a srries of variables on the same subject it would be saving time if you could use the tab to switch from name to value, then the enter to switch to the next one of the same variable type. (or as today the tab brings to create variable you could at least allow the keyboard selection of the type)

When you hover over a value, sometimes your cursor turns into a slider. From there you can click and drag and change the values intuitively instead of having to type out the numbers. On the numeric inputs with big labels, there isn’t much of a problem. But when there are no labels to hover over, the area that detects a hover is so small that its really frustrating to nail it on the first try. Here is a video demonstration of the frustration: Does anyone even use the slider function or am I the only one? It’s super useful in my opinion. I don’t have to type the numbers and I can just approximately size it instead. For anyone who have used Blender, a better implementation of the cursor slider is basically what I’m asking for. What do you think?

When presenting ideas, it would be helpful to have a keyboard shortcut to jump to the next section in FigJam. Similar to the keyboard shortcut “N” in Figma to jump to the next frame.

Prior to color variables being introduced all of our design system colors were saved as styles in our shared library. Now with the introduction of color variables, it seems style usage is shifting to be meant for multiple color fills and other more complex fills. For simple, single color fills, Figma recommends we use color variables (this is based on the tooltip in the style picker, but doesn’t seem to be reflected in the official documentation yet). My team has added all of our design system colors as color variables, but now in the style picker there are two sets of colors, first all of our new color variables, then all of our legacy styles. We’d like to delete the legacy styles so there is just one set of colors for our designers to choose from, however deleting a style detaches all of the instances of that style across text, shapes, frames, etc. So that is not a viable option since all of the existing colors across our teams design files will become out of sync with our design sys

right now a stroke is added to the png bounding box rather than the contents while in Sketch and photoshop you can add it to the outline of the contents. Can we bring that (even as an option) to Figma?

It would be good if Figma has a visibility toggle for the variables. It helps to identify duplicate values and makes creating/deleting/simplifying variables workflow faster.

Teams contain projects, but this relationship is not visualized clearly in the Home page because the style and layout of projects is the very same as those of teams (except for the little rectangle): The information hierarchy should be clear, e.g. like this: https://learn.microsoft.com/en-us/windows/apps/design/controls/images/treeview-icons.png

Hey there! I noticed when you’re applying variables to an object property, the variables list doesn’t seem to be sorted in any way. I’ve uploaded a screenshot showing how my variables are set (on an external file), and the dropdown list when I’m trying to apply it to the gap of an auto-layout container.

Browsing files is such a pain. The customizable left sidebar just pushes the responsibility for file management on the user and doesn’t even give them the proper tools to actually manage files. Filtering and customizing collections is fine, but there needs to be an easy way to see the whole world, organized in a nested hierarchy. Too many weird concepts and got’chas. I’m always worried there’s a file hiding somewhere because I’m missing some distinction between a ‘section’ and a ‘project’ or whatever. I constantly flail around trying to navigate the company/team/project/section scheme. Just please give us folders, both above and below the project level, so we can place projects in folders, and we can create folders inside of projects to organize the files within them.

I would love the ability to add sections (like in FigJam) but, in a Figma design file.

What would be great is the option for designers to opt in to use tailwindcss values by default and the possibility of devs to easily export the html markup with the tailwind classes already on it as it would greatly boost productivity and make the overall process even better.

It’s now possible to install an “App Clip” without going to the App Store. For remote user testing, this could be awesome if Figma Mirror could be extended to work with Clips. I could then send a link or QR code, and get my remote user to test the design without the browser nav that is current situation with link sharing. Hope that makes sense? 🥸

I use Timely to track my time on Figma. This has done wonders for me. It can track everything. But it is only tracking in which Figma file I’m currently working - not the page name inside that file. It could be useful if I could toggle this simple ability - so my tracking software could read the tab and get better tracking. Thanks,

As a designer, I need a true read-only share (no ability to comment and input nay information) so that developers working on snesitive project can be allowed to view Figma projects without a concern that sensitive data or information might be brought back through Figma (specifically comment feature being disabled).

Please allow us to attach comments to a specific element. Otherwise, the comments can appear nonsensical because Figma is not aware of the state of the prototype when the comment is made.