Share Your Thoughts

Currently, developers working in Figma Dev Mode cannot search or filter through variables in the variables table. When working with design systems like Gator that have hundreds of design tokens developers must manually scroll through extensive lists to find the specific variable they need.

I would love to group Figma tabs and then relabel that grouping to keep my Figma organized across different clients. 

My team loves to brainstorm, and we do it by each jotting down our own ideas separately, and then revealing, sharing, and converging on those ideas when we’re done. We love tools like EasyRetro that let us hide our own cards until we’re ready for the big reveal, but it’s not as fun and visual as a product like FigJam. I’d love for us to be able to make sticky notes with the text hidden from my teammates, and then unhide the text on those sticky notes all at once when we’re done brainstorming

Is it possible to specify an objects center of rotation. I cant for the life of me find it anywhere. You could do this relatively easy in sketch.

When I try to interact with Figma using touch or pen input, certain UI elements, such as plugin windows and scrolling through lists, do not work as expected. The issue occurs on a Surface Pro 11 X Elite running Windows 11. Steps to reproduce: Open the Figma native app on the mentioned device. Attempt to scroll through a list or interact with a plugin window using touch or pen input. Observe that the UI does not respond correctly. Expected behavior: Touch and pen interactions should seamlessly work for all UI elements, including plugin windows and list scrolling. Device details: Device: Surface Pro 11 X Elite OS: Windows 11 Please investigate this issue as it significantly impacts usability for devices relying on touch or pen input. Thank you!

How can I change settings of video fill to speed play faster? will that be supported or added anytime soon?

Figma sites doesn't seem to support Figma Draw brushes, will that be included in the upcoming updates?

It would be awesome if we could get access to copy and paste data in the Plugin API. We’re looking at creating a product which allows users export from our site to Figma (ideally through the clipboard) and the current ways of doing that involve some gnarly scripting I’d rather avoid. If there’s another solution that would be awesome too! To be more specific the endpoint would be used like let copyData = figma.selection[0].copyData so we could copy that into users clipboards on our site.

Hi Figma Team,I’d love to see an enhancement to FigJam that allows videos (and GIFs) to autoplay, play simultaneously, and loop continuously. This would be an amazing addition for creating video moodboards where multiple videos can be displayed and automatically played in sync. It would allow users to create dynamic and immersive visual experiences directly within FigJam, perfect for design inspiration and collaboration.Thank you for considering this feature!

Hey Figmates! After using variables for some months now i´ve come to a conclusion that that three levels of variables doesn´t suit every project. Or at least my projects, when it comes to theming different product pages. Until yesterday i used primitives, semantics, and themes as suggested by many users, as a proper setup. But, it just felt too bounding.You can easily just use the the primitive and semanitic level. With Modes as the theming.But, now its a bit frustrating. In the appearance menu, its to set menues – theming and semantics. Its unchangeble. The “Theming” now its linked to the semantics menu. I changed the setup to have an easier workflow, without being too specific with the naming in the theming process.Any thoughts on this?

When you create a prototype with the Open overlay interaction to trigger a bottom sheet, it works well, until you actually want to put that prototype in a slide. Once you include it in a slide, the Overlay uses the slide as its parent, not the phone screen, so it appears from the bottom of the slide, making the interaction very unrealistic. Using ‘manual’ position doesn’t solve it, because you still see the modal appearing from the bottom of the slide.To solve this I’ve created an interactive component that fakes the appearance of the sheet by using Smart Animate, but it’s so much work for such a simple use case.Would be great to get a solution for this, as I assume many people are embedding prototypes in presentations.Note: when I say slide, I’m not talking about Figma Slides, but the classic slides we’ve been using before that.Thanks

Please bring back ui2, it's very hard to work with Figma right now actually. Instead of a gradual change, everything changed all at once. There's no need to make things more complicated than they need to be.I've always been a big fan of Figma. It's so easy to use and it's a pleasure to work with. After spending some time getting to know Adobe's various features, I've found a product that's as easy as it is delightful. Whether I can creating both banners or designing pages, this product makes it a breeze. I learned all the features and capabilities in just one day in UI2!Now, with the new UI3, working with a simple project is lengthened many times over. I just wanted to let you know that the menu on the right is very tricky to use. It's working with frames, and the position of objects inside has become inconvenient and very long.I would really appreciate it if you could bring back the UI2 selection. I'm struggling with the new interface for the third day and can't get used to it.I had n

​​É uma coisa boba, mas seria bom vcs arrumarem, na parte do stroke q eu posso selecionar o tipo de borda da linha, ao selecionar o contorno se é borda arredondada, retangular e etc, ta certinho, porém na parte de selecionar a linha ela deixa invertida, seleciono uma direção ela me entrega o contrario, isso é coisa pequena mas pra quem tem toque é foda kkk 

There a lot of new features coming to Figma every Config, like a Figma version of Powerpoint or Illustrator. But this forum is full of requests related to issues people face building UIs.Here are some recent Figma updates that are really amazing:Keep aspect ratio Reorder variable modesThese features cannot be replaced with plugins or external apps, and they save a lot of time for large projects. But, it took years to implement so much requested concepts. And now, with the new “Grid” feature (which is very much needed) — same situation: it is unusable in its current state. And there’s no hope it will usable when out of beta (as it was with variables). Don’t get me wrong, I really like accessibility check in the new color picker. But this can be done, a bit slower, with a plugin. And, there are lot of basic things, that cannot be done at all:to set a prototype size per flow. Why can’t I have my desktop mockups on the same Figma page as my mobile mockups? to use component variants for sta

I would be nice to have the Device settings specific to each Flow Starting Point so I can keep Desktop/Tablet/Mobile on the same page.  

Просто зачем?Буквально каждая функция в вашем редакторе вызывает только этот вопрос.1.Зачем при копировании текста в одном слое сохраняется не только его содержание но и форматирование? Я даже не представляю кому может понадобиться функция скопировать текст вместе с его размером и жирностью при копировании какого-то одного отрывка - тот кому пришла в голову эта “удобная фича” видимо очень одарен интеллектом2. Зачем в редактировании регистра помимо функций Appercase и Lovercase у вас есть 3-е абсолютно бесполезное редактирование которое только и делает что первые буквы слов заглавными? Она нахрен не нужна если ее не перерабатывать, ПЕРВЫЕ БУКВЫ ДОЛЖНЫ БЫТЬ ЗАГЛАВНЫМИ А ОСТАЛЬНЫЕ СТРОЧНЫМИ иначе это просто бесполезная и нерабочая хрень!!!3. Как у вас работает выделение слоев на разных фреймах? Почему когда я на одном фрейме выбираю фото и пытаюсь это сделать внутри другого я не могу заранее угадать что будет выбрано??? Это просто дикий рандом, то значит выбирается весь фрейм, то какая-то

I have a component library that I want to add support for accessibility. Some of our components need to have HTML tags of alt=“” and aria-label=“”. I would like to have these in Figma for our writers to add content. I’ve looked at a ton of Figma to code plugins, and have tried using text properties, but with no success. Any ideas?

Please simply support the Code Syntax of Variables more holistically in DevMode. Especially in Annotation Properties(!). We recently started making use of the code syntax of variables, but unless it is widely support, it does not seem to be very beneficial for our developers.

As a consumption side of the design system in Figma, it is very hard to realize there’s more information inside the component descriptions. It is like, I didn’t know the team has link documentation there that’s useful for my designs.  It is hard to know that a couple of text lines are clickable and that they contain more than just text. 

The user story is as simple as “As a user of figma design when using the AI tools such as `boost resolution`, `edit image`, `remove background`, I would like to hear a sound feedback when the job is done, so I can do something else while waiting for it to complete and be more productive” I don’t know you guys, but I like the AI features a Lot, and I’ve been working a lot specially with the edit image for videogame placeholder assets (it’s amazing), but I just don’t want to stare a the screen for a 2 minutes doing nothing, I would like to leave it working and do something else. I hope this is a super simple feature you guys can make, it would be good :)

SummaryEnable Figma Make users to preconfigure the default code output framework (e.g., Angular, Vue, React) and set organizational coding guidelines that are automatically applied when generating code.ProblemCurrently, Figma Make defaults to generating React code. While prompts can be used to switch frameworks or enforce custom rules, this adds repetitive manual steps for every session. Our teams have established rules and standards (framework choice, naming conventions, linting rules, accessibility standards, etc.) that we want consistently applied from the start.Impact Designers and developers must repeatedly remind the system of our preferred framework and rules. Inconsistencies can arise if someone forgets or phrases the prompt differently. Slows down adoption because teams want their code to be generated within their established ecosystem by default. Proposed Solution Allow users to define a default project configuration for Figma Make (framework, package manager, language ve

I'm so pissed off by FIGMA MAKE!!FIGMA MAKE used to be very smart, quickly understanding any requirements I asked for. Lately, however, it's been incredibly clumsy! I've been given a lot of requirements and then constantly making random changes. I find this experience incredibly poor! I'm so angry!

Hey there, I’ve created a branch and added a component to our library. So far so good. Then I accidently moved an instance of a component a bit, so that in the “Branch Review”, it says “Node Reordered, Position, Rotation, or Scale changed”. And yes, that’s true. Even though, nothing has changed. I missed to it CMD + Z to revert it, so now when I want to merge, I have to merge it even if I don’t want, and then push a library update of this modified pattern. My suggestion would be the same as we can do it in VS Code for example. Before commiting something, you have the ability to “Discard changes” meaning that all the changes you made in this commit will be removed and the component will be in it’s main branch position/state. That would be helpful for not having to merge something you don’t want/did only for testing purposes.

Before: After:I want the edge I’m adjusting (the right edge) to snap to grid. So the answer is not “Turn off Snap to Grid”. Figma, when the user is making an adjustment to A, just make adjustment A. Do not go head and make adjustments to other random things B, C, D...

Hi there,I’d like to propose a feature that allows individual sections to exist within a parent section, with the ability to collapse and expand them via an accordion-like function. The default state would be closed—similar to an index—so that child sections are only visible when expanded.Currently, it’s challenging to guide developers to the correct layers because the default open view doesn’t always reveal all sub-sections, which can make navigation and referencing less intuitive. This feature would help improve clarity and streamline collaboration.