Share Your Feedback

Hi Figma team,I was really disappointed to see that Iranian universities are no longer supported for the Education Plan. For many of us, Figma has been more than just a tool; it’s been our main way to learn design, collaborate with classmates, and dream about building a career in this field.Losing access feels discouraging. We’re just students who want to learn and grow, and it hurts to feel excluded because of where we live. Education should bring people together, not separate them.I hope you can reconsider this decision or at least find a way to keep Iranian students included. Having equal access to learning tools like Figma means the world to us. Thanks for listening and for everything you’ve built to inspire the design community.

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.

We just wrapped the big announcements at Config, and we know there’s a lot to take in.This thread is your space to share reactions, ask questions, and let us know what you're excited about (or still curious about) with regard to Figma Draw. Our team will be actively reading and sharing relevant takeaways with the product team. What we’d love to hear from you:What aspects are you most excited about — and why? Where do you still have questions or want more clarity? Anything that didn’t quite land for you yet? A few quick reminders:If you need help with a specific account or file issue, please get in touch with a specialist on the Support Team. A note on Community Guidelines: Posts that veer off-topic or become unproductive may be moderated to keep the focus on the product at hand. Keep feedback focused on Figma Draw — this helps everyone follow along.

We work on large display but Figma UI doesn’t adjust and shows minuscule panels for Text Styles, Library, Font lists, etc…. See related post below: 

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 

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.  

We just wrapped the big announcements at Config, and we know there’s a lot to take in.This thread is your space to share reactions, ask questions, and let us know what you're excited about (or still curious about) with regard to Figma Make. Our team will be actively reading and sharing relevant takeaways with the product team. What we’d love to hear from you:What aspects are you most excited about — and why? Where do you still have questions or want more clarity? Anything that didn’t quite land for you yet? A few quick reminders:If you need help with a specific account or file issue, please get in touch with a specialist on the Support Team. A note on Community Guidelines: Posts that veer off-topic or become unproductive may be moderated to keep the focus on the product at hand. Keep feedback focused on Figma Make — this helps everyone follow along.

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

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. 

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!

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...

When testing out the new grid inside components, I noticed that there is no option to hug the content vertically. We use instance swaps in things like footer for our designers and it’s not ideal for them to have to manually resize. Would be great if this new feature hugged, otherwise we can’t really use it in a lot of our components in our design system we thought it would be good for.

It looks like impossible to change the gradient direction?  the gradient is popping over where i have to drag it from and i can’t find out how to change it 

can we have option to switch from desktop, tablet and mobile when prototyping from figma design, similar to figma sites 

We just wrapped the big announcements at Config, and we know there’s a lot to take in.This thread is your space to share reactions, ask questions, and let us know what you're excited about (or still curious about) with regard to Figma Buzz. Our team will be actively reading and sharing relevant takeaways with the product team.  What we’d love to hear from you:What aspects are you most excited about — and why? Where do you still have questions or want more clarity? Anything that didn’t quite land for you yet?  A few quick reminders:If you need help with a specific account or file issue, please get in touch with a specialist on the Support Team. A note on Community Guidelines: Posts that veer off-topic or become unproductive may be moderated to keep the focus on the product at hand. Keep feedback focused on Figma Buzz — this helps everyone follow along.

I was very excited to hear that grids were coming to Figma. CSS Grid was introduced years ago and brought with it many things that flexbox was incapable of doing, so I was hoping for a similar level of new capabilities here, and I genuinely cannot believe that this feature is being shipped in its current state (even as a ‘beta’). This is a very long post, but I feel like this feature has been implemented so poorly that it legitimately sows doubt in Figma’s capabilities to deliver features in the future.Inability to ‘hug’ contents Both rows and grids themselves are unable to resize themselves to match their contents (‘Hug”). Row heights must be either “Auto” (1fr) or a fixed height, meaning that if you want your rows to be sized per their elements, you’ve now manually defined each row height in px (not even a variable value), and instead of getting a clean CSS output, now you have however many rows defined in exact values, destroying any chance of scalability. This alone makes this fe

Your software is a masterclass in how not to design an interface.I click one element, perform an action, then click another element to do the exact same thing, and the entire layout collapses.There is no way to diagnose what happened because your options auto-hide. There is no feedback, or clarity. Nothing but broken workflows.Stop trying to be clever. Stop chasing some illusion of minimalism that serves literally ZERO purpose.Hire developers who understand what predictable, reliable interfaces look like. For three decades, core UX standards have guided every serious design tool on the market. Your team ignored all of it and delivered a product that feels like fighting a shopping cart with a broken front wheel.You bury essential tools under layers of useless clicks while plastering non-critical stuff front and center. It is mind boggling.And your documentation is as useless as your interface. Answers are vague or incomplete. There’s no explanation as to WHY something does what it does

Hello Figma Community and Team,I'm incredibly excited about the potential of Figma Make and have been eagerly experimenting with its AI capabilities. However, I've run into a significant roadblock when it comes to integrating my team's comprehensive design library, and I'm hoping to get some clarity on the current limitations and what we might expect in the future.Our Setup: A Highly-Structured Design SystemTo provide some context, we've invested a substantial amount of time and effort into building a robust and meticulously organized design system within Figma. This isn't just a collection of components; it's a fully-fledged system that includes: Hundreds of Components: Our library is extensive, containing a wide array of components, from basic elements like buttons and inputs to more complex organisms like cards, sliders, and navigation controls. Meticulous Naming Conventions: Every component, variant, and layer is named with a clear and consistent hierarchy (e.g., input/text/defau

Figma Make is great for creating animations and interactions, but it’s pretty annoying that it ‘improves’ the content all the time. I work with real content that is complex. That complexity is part of the problem I’m trying to solve, so it doesn’t work that Figma deletes it and proudly proclaimes that this is better for the user.In my second attempt I created the animations and interactions first. Then I tried to insert the real content piece by piece (‘replace this paragraph for this paragraph’). That also did not work; Figma Make still changes the structure and rewrites the content. (And not only the content I’m working on but in the whole page..)So.. is there a way to prevent this?

Why is Component Configuration hidden in the toolbar now?It used to be directly visible in the toolbar, but now it’s tucked away behind the “More options” menu. Our team works heavily with metadata in our asset libraries, and having to click the extra menu every single time gets really frustrating.Was there a specific reason for moving it?

Hello Figma Team,I am currently creating tables using a table plugin in Figma.Inside a frame component, I place text components and adjust their size to fill the cells. However, whenever I tab into the cell, the text component gets deleted automatically.Even if I intentionally type and then delete characters, leaving the text field empty, the text component is automatically removed. Because of this behavior, I cannot build a proper table template.At the moment, my only workaround is to insert a space character to prevent deletion, but this causes frequent mistakes such as accidentally starting text with an extra space. This is not an ideal solution.It seems this is not a plugin issue but rather Figma’s default behavior of auto-deleting empty text components.Suggestion:If a text component is placed inside a frame (e.g., a table cell), it should not be automatically deleted when empty. This would allow users to create table templates more effectively without resorting to hacks like invis