Share Your Thoughts

seems like a simple thing but yet it cant find them

Section names used to be bigger and more readable when zoomed out in older versions of Figma. Now they are too small to read when zoomed out, which makes it harder to navigate my file by scanning section titles. I'd like the old larger section title size back, or an option to control section title font size.

Hi,Currently, the FigJam formatting toolbar only defaults to bulleted (unordered) lists. Because I mostly use numbered (ordered) lists, converting existing text into a list takes multiple extra steps: Apply bullets to the selected text. Manually change each bullet point to a number. Having a dedicated numbered list option directly in the text toolbar—or a quicker shortcut—would save a lot of time.Are there any plans to introduce direct numbered list formatting in FigJam soon? I’d love to hear the team's thoughts why it wasn’t added explicitly now?Thanks Default option After explicit mention of a number 

Add the new Midjourney model to the Img gen tools

Hi, I think my request is obvious and I bet all pro tier users agree. We really need this. Thanks

Right now under price I can choose All, Paid, and Free. Under “free” I often find items that aren’t actually free but are demos, with limited functionality or times they can be used before you have to pay money. From a marketing perspective I get it, the plugin technically has some free functionality, but if its limited by time or uses, the use of “Free” is misleading. So I think what would be ideal is a new facet, “demo” for all plugins/resources that aren’t fully free.The other request is a filter to offer the option to include or exclude plugins that use AI to perform their function.

When working with large files, I encounter such wasteful actions as expanding/collapsing each selected group of layers.I find it better to perform these actions in bulk. Here is my solution to this problem. Please vote if you are also troubled by this time-consuming process. 

.

Dear developers, please add the ability to define a variable's color based on several other variables.For example: let's say I've decided that the hover state is created using the rule "brand color + 50% opacity of the theme color" (white for the light theme and black for the dark theme). But then the client suddenly decides to change their brand color. It would be really convenient to be able to create rules like this, so that you don't have to change every color manually. It would save a lot of time.  

In massive organisations with tons of projects and documents, we are trying to figure a way to tag them in order to facilitate our job when searching for anything.. The implementation of a tag system would be quite welcome. Here is a sample image of what I mean below :  

When using a grid based system, it would be useful to bump (move) rulers by a set amount. For example if I am designing a UI and I am using a 8px system. It would be useful if I could click on a ruler, press a button (‘b’) and move that ruler by my 8px. You could have a setting called “Grid System px” where I could set the bump amount. That way when I lay out elements by using the rulers I can quickly move them around based on my grid system.

My name is Gleb. I'm a producer at a regional TV channel in Bashkortostan, Russia, and this is my Figma love story. I found Figma in 2022. Before that I had tried several times to learn Photoshop and the tools around it, and failed every single time  I just bounced off them. Then, after everything that happened in 2022, I realised I had to level up my skills if I wanted to earn more and provide for my family. A post about Figma showed up in my feed, I decided to give it a try, and it was love at first sight. The interface was so clear that I only opened a tutorial when I was truly stuck. I remember barely leaving my desk for a week, digging through the software and enjoying every minute of it. Figma replaced everything for me — Photoshop, PowerPoint, Miro, all of it. And a special thank-you for Community. That is where I go for inspiration, where I train my eye and learn from people far better than me. Now, how Figma changed my life. 2025 was financially hard. My wife was pregnant, we

Hi Figma team,I’d love the ability to open multiple selected files at the same time.Currently, it’s possible to select multiple files and perform bulk actions such as Duplicate, Move, or Delete, but there is no option to Open all selected files.This would be especially useful when working on large projects or design systems where multiple files need to be reviewed, compared, or updated during the same work session.Suggested improvementsAdd an Open action to the bulk actions menu. Open each selected file in a separate tab or window. Support common shortcuts such as ⌘+Enter (macOS) or Ctrl+Enter (Windows) to open all selected files.EnvironmentmacOS Figma Desktop AppThis feature would be especially valuable for designers reviewing multiple files every day, making file management much more efficient.Thank you!

So lately I’ve been designing retro mockups and they use pixel fonts. On most design tools like GIMP, Pixel.net, and Photoshop, there is an option to use Aliasing (Disable Anti-Aliasing) for text, making it pixelated (no blurring caused by anti-aliasing) and unfortunately Figma does not have this, which makes me search for Bitmap fonts that only work on specific sizes to accomplish pixel fonts. So I wanted to ask for an option to have Aliased fonts without Anti-Aliasing, to force them be pixelated.

Hi everyone! Maybe I’m missing something, but is there a way to copy the currently selected padding token, similar to how interactions can be copied?I’d like to copy a token that is already applied to one component variant and then paste it onto another variant—or any other object with a compatible property—that currently has a regular numeric value or no token assigned.At the moment, I can’t find a way to copy the selected token while the token list is open. Is this already possible somehow?  

 Hello! Congrats on your big update. Btw while I really enjoyed trying the Figma agent to build my own Plugin tool, it was frustrating to know that I have no way to share it with the team. I guess that it's because it's beta version? If you don't have a plan to make it sharable in a foreseeable future, i would prefer building plugin externally for our team rather than these tools. Thanks for reading! 

As AI coding becomes part of the design-to-code workflow, I think there is a new type of information that belongs in Figma: Implementation annotations. Today, annotations can only be added by people with edit access to the design file.This works well for design explanations, but not for implementation guidance. Imagine this workflow:A designer finishes the UI.Later, a developer reviews the design before implementation and notices several places where additional implementation context would help an AI coding agent generate much better code. For example:This Frame should be implemented as a scrollable list. This component should use virtualization. This area should stay fixed while the content scrolls. This value comes from the current device model. This text should truncate after two lines. This image should preserve its aspect ratio. This section should use the shared DeviceCard component. This layout should become two columns on larger screens. None of these change the visual design.T

I’ve created a detailed set of design guidelines for my product, covering layout structure, spacing, naming conventions, responsive behavior, component usage, interaction patterns, and platform-specific requirements.However, I haven’t found a way to make these instructions part of the Figma Design Agent’s persistent default context.Custom Skills are helpful because they can package reusable instructions and remain available across files. However, they still need to be explicitly invoked in each conversation. Libraries and attached guideline files also need to be added as context manually, while Figma Make’s guidelines.md is scoped to an individual Make file.I’d love to see a persistent context system for the Figma Design Agent, with multiple levels such as:Personal context — preferences and conventions applied across all of my files Team or workspace context — shared standards automatically followed by everyone Project or file context — product-specific guidelines applied to every agen

The features added to Figma in the past few years (FigJam, AI, Motion) is creating lag and additional complexity for a tool that was historically lightweight, collaborative, and easy to build UI for developers. While I love the innovation, I wish I could turn off all these features so they don’t create unnecessary cognitive load while I’m working. Thank you for your understanding.

Hi, I stumbled across this issue as I wasn’t able to read the comments of the master file in the branch. I always need to switch back and forth to incorporate feedback from reviewers and this is very annoying.

I love the new “Ready for Dev” status option on Sections, but would love to add and use other statuses relevant to my process. For example, it’d be great to have a “Ready for Design Review” and “Ready for PM Review” statuses so that everyone knows where things are at.

Hello Figma! I can not change the direction of the Autolayout on the instances of a component. I can not understand why such a great feature is disabled on the instances and why not allow us to overwrite it? There are so many incidents that I would have wished to be able to change the direction of the Autolayout in the instances of the component but right now I have to create multiple variants. 😦

We have a Design System with parent components composed of nested instances. Both parent components and nested instances are in the file “A”. To avoid having thousands of components available within the Assets when publishing the library, the nested instances are hidden with “.” at the beginning of their names. The problem: When using the component library from file “A” in file “B”, everything works fine. The issue arises when a nested instance from file “A” requires an update. Firstly, it does not allow me to publish the nested instance update without removing the “.” from its name, and I also cannot publish the parent component containing the updated nested instance. If somehow I manage to publish the parent component, file B will prompt me to update it, but the updated nested instance does not receive the changes made. Is this a bug? Or what is the correct way to work, update, and publish nested instances so that they always receive their updates without cluttering the Assets librar

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.

I have a problem where I have noticed that when a designer detaches a design and it is using hidden components within it, that it ends up decoupled from the library… I was always under the impression that since it is a component in the library, that if it was detached it would still be able to receive updates via these hidden components… I have realized this is not the case.I think a new feature request should be made to allow hiding the components from the asset panel view (which is what people actually want from the hiding feature) without losing the link to the library.If the feature intent is to not publish these components at all, I am not understanding why when we detach, why those hidden components don’t detach as well? This is what gave me the false notion that they would still be able to receive updates, since they are still an attached component -- but attached to the wind it seems...Design system maintainers are not looking to not fully publish these components, but instead