Share Your Thoughts

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'

​​É 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 

As a user I want to lock the guides so that I dont accidently select or move them. This is frustrating. There are times when layout grids are are the correct tool to use and a time when guides/rules are the correct tool. When you are zoomed out it’s impossible to select elements without selecting or moving guides/rules. 🙂 …to everything turn turn turn turn…

Right now, once you create a Main Component, there is no way to convert it back into a normal Frame/Group/Autolayout. If a component is no longer useful, we are forced to use the workaround: create instance → detach → delete main component. This adds extra steps and slows down workflow. Request: Please add a simple option like “Remove Component” that instantly converts a main component back to its original state.This would save time, reduce friction, and improve cleanup when working with experimental or temporary components.

I’m writing to express my deep frustration with the current limitations of Figma’s Slide Deck feature. As a tool celebrated for its UI/UX capabilities, it’s astonishing that Figma lacks fundamental functionalities that are already included in other design platforms. Key Issues: Absence of Interactive Buttons for Non-Linear Navigation: The inability to create buttons within slides that link to other slides severely restricts the creation of dynamic, user-driven presentations. This is a basic feature in tools like Canva, which allows for interactive menus and branching scenarios. Smart Animation for Linked Slides: Once non-linear navigation is added, Smart Animate should apply smoothly across these links to keep animations consistent. This avoids disrupting animations when navigating non-linearly, ensuring a seamless experience. Enhanced Linking Visualization in Grid

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

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.  

How easy would it be for Figma to have a simple item in the right-click menu (and main menu) for character count or word count? Surely there are plugins like Word Counter, the one that I just tried and it doesn’t work 🤬. And easy enough to do it on the web. But how about I select the paragraph I worked with and see how many words I have? Right there where I am working? Also, if this exists…educate me. 😉

Просто зачем?Буквально каждая функция в вашем редакторе вызывает только этот вопрос.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 :)

Hello, I’d like to raise what I believe is a very reasonable and long-overdue request.Figma is a professional tool, widely used across design and development teams, and charged at a premium rate. Yet, it lacks a fundamental feature for UI design validation: the ability to float a frame or image in a transparent window above other apps, such as a mobile simulator.This is an essential need when comparing a design with a live implementation, particularly in mobile development. Tools like Overlay (which is currently unreliable), ScreenFloat, or even basic screenshots partially solve this—but these are third-party workarounds for something that should be native to Figma.I’m surprised this hasn’t been addressed yet. It would be extremely useful to: Export or pin a frame as a semi-transparent floating window. Overlay it on top of a running app or simulator to check pixel precision. Adjust opacity and t

I would like to be able to selected multiple child components which are all associated with the same parent component and edit their shared nested instance properties across all selected child components.

I know If I use the option key and hover, I get the distance between objects but I would like a feature that shows the distance exactly the way the option key does but without start making a copy of the element. If I start moving it I just want to see the distance to the element above for example. If I do this now it’s going to get to a point where it starts measuring from the copy I’m holding.

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.

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.

Hi Figma team,I’m working with a central design system library that uses variables for colors, typography, spacing, etc. The challenge I’m running into is how to customize those variables per project/client without editing the library file.Here’s the workflow I’d love to have: In the library file, components are built using semantic variables (e.g., Brand / Primary, Text / Default). In a project file, I create local variables with the same semantic structure but mapped to project-specific brand values. I want to be able to relink or remap library variables to my local variables, so that when I update the local variable values, all linked components automatically update. Right now, even if I duplicate the variable structure locally, components still reference the library’s variable IDs