Skip to main content

Share Your Feedback

Your opinion matters! Tell us what’s working (or not).

  • 294 Topics
  • 1,477 Replies
294 Topics
S
Figmate
seniManager, Community Support
posted in Share Your Feedback
READ ME: How to use the Share Your Feedback category?

Figma’s products have been developed to add value to users and we continue to want to hear what you have to say! That’s why we’ve created this category - a dedicated category where you can post your feedback, both positive and constructive.

Here’s a few points to bear in mind in the Share Your Feedback category:Please keep the discussion constructive, and follow our Forum Guidelines and Code of Conduct Our team will merge topics with feedback on the same subject Inactive topics that are 6 months or older may be closed or archived. We’ll make sure that our product teams have seen the feedback though before closing the topic.

Note: If you have product ideas or feature requests, head over to the category Suggest a Feature.

2510
S
Figmate
Tom Reem
Figmate
Tom ReemFigmate
posted in Share Your Feedback
[Config 2025] Figma Buzz is here — let’s hear what you think! 🐝

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.

81059
Janinha
click_Mao
click_MaoNew Member
posted in Share Your Feedback
UI3 Feedback

What I can’t stand the most is that the panels of the new UI can’t be attached to the edges. They leave some gaps, wasting the space to display the main design and operation area. And visually, these gaps are also distracting my attention. The toolbar at the bottom also interferes with the main operation space, especially if its color is the same as my design draft. By the way, is it just for the convenience of novices to move it from the top to the bottom? If someone who uses Figma more frequently, he will use shortcuts instead of mouse clicks to trigger these functions. So I hope that adjustments can be made in time in the official version of UI3, otherwise these redesign will seem like a subjective conjecture of someone who doesn’t use Figma much.

6876425
Heidi Mikolajczak
Pablo_Sara
Pablo_SaraNew Participant
asked in Share Your Feedback
No auto-layout for parent frame?!

Hey guys, I was playing with Buzz and after pasting one of my assets, the auto-layout property is gone! It seems auto-layout is not supported on the parent frame, or is this a bug? If it’s not a bug, there’s no use for us. We create hundreds of Newsletters and ads with auto layouts which flow automatically depending on the content.Also will the collaborators be able to swap instances of a symbol on a design and hide items? Thanks!

233
Ana Pradas
design3kintech
design3kintechNew Member
asked in Share Your Feedback
Figma Sites - Webpages Canvas

The Figma Sites Webpages Canvas, Has a max height, I can’t continue modifiying the work.  

00
design3kintech
Andreea Tilihoi
Andreea TilihoiNew Member
posted in Share Your Feedback
New Figma Update Removed Spacing Input Between Elements

Previously I was able to manually change the spacing between equally distributed frames or objects  even though the items were not in an auto layout. Now that functionality is gone and I can only edit the spacing manually or by using the pink interface between items - which makes it harder to get specific numbers.

00
Andreea Tilihoi
Kelyan_Chaumet
Kelyan_ChaumetNew Participant
posted in Share Your Feedback
New update changed the Figjam stickies color, and I don't like it

The most recent update changed a few things in Figjam. First, they added a lot of new “shapes” (which is just a rectangle with an icon inside), and added a couple of new default colors. HOWEVER, they also changed the base colors for stickies!They are now way paler, with washed out, low contrast colors. I’m sure it was supposed to make them look both like real sticky notes and to increase the contrast between the background colors and the text for accessibility reasons, but I feel the colors don’t contrast enough at all between one another.I use colors a lot to help with identifying specific sections or types of notes, I often use every color of stickies available to distinguish between specific uses of each (like taking notes during user tests, each color representing a scenario).Unless custom colors are finally made available for stickies in Figjam, I think they are going to be way more annoying to use for me from now on.  

25919
Frank_K
C
Cynthia SarkisNew Member
posted in Share Your Feedback
Annotations Positioning

Introducing annotations is great, they’re super helpful ✨ That said, the lack of flexibility when it comes to their positioning is quickly counter intuitive. They end up overlapping with other elements, which can make designs harder to read and manage—especially when multiple annotations are stacked in the same area. It would be incredibly helpful to be able to manually drag the annotations component to reposition it (e.g. top, bottom, left, or right of the target element), while still maintaining their link to the relevant object.   

642
sandra_lcld
E
EtchNew Member
posted in Share Your Feedback
Annotations Feature

The annotations feature is nice, but it’s pretty frustrating that you’ve chosen to only allow editors and developers access to them.I frequently have a need to share annotations with other stakeholders (developers, support, other product managers and designers). By implementing them in the way you have, you’ve excluded product managers with view access from seeing my annotations. Most of the PMs I work with only have viewer licences which means they are unable to see them.My alternatives are that I use Comments instead of Annotations (which is a misuse of Comments for developer and interaction notes IMO) or I spin my own and make components of them.Please make annotations visible to all users; not just editors and developers.

482
sandra_lcld
Tom Reem
Figmate
Tom ReemFigmate
posted in Share Your Feedback
[Config 2025] Figma Make is here — let’s hear what you think! 🎨

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.

43213
Eric_Alm1
Daraa Team
Daraa TeamNew Member
asked in Share Your Feedback
Navigate to vs. Change to

I finally figured out (I think) where my prototyping pain is coming from. I think maybe most users would use navigate to in order to navigate between dashboard pages, but I am using change to w/i instances of a large complex component set … with variables. I think my approach is more dynamic, but of course takes up more memory. And, navigate to has some limitations in terms of carrying a prototype across files.  Can Figma consider making variables x prototyping x navigation more robust/dynamic while not destroying memory?

40
Daraa Team
Tom Reem
Figmate
Tom ReemFigmate
posted in Share Your Feedback
[Config 2025] Figma Draw is here — let’s hear what you think! ✍️

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.

70634
Kate Davydova
Richard_Bennett1
Richard_Bennett1New Member
asked in Share Your Feedback
No min / max width options for a frame with new grid auto layout?

Maybe I’m missing something (and I know it’s in beta right now so I’ll manage my expectations accordingly), but it doesn’t seem like you can set a min/max on a container with the new grid auto layout option? It seems like such an odd decision to intentionally remove it for no good reason (that I can see) I wanted to ask and see if everyone else is missing this or if it’s just me?              

301
Tom Reem
Figmate
Tom Reem
Figmate
Tom ReemFigmate
posted in Share Your Feedback
[Config 2025] Figma Sites is here — let’s hear what you think! 💻

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 Sites. 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 Sites — this helps everyone follow along.

147354
Bryce_Driesenga
Amber_Salyer
Amber_SalyerNew Member
posted in Share Your Feedback
New - Grid and Hugging Content Vertically

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.

1756
Purrgil
Michal_Ordowski1
Michal_Ordowski1New Member
posted in Share Your Feedback
Layer panel - can't collapse layer on screen edge click

TL;DR: Could Figma please extend the hitbox for the expand/collapse layer button (the chevron to the left of layer name) to the left edge of the screen?Hi. The hitbox of the button used to expand/collapse a layer in the Layers panel does not extend to the left edge of the screen. The hitbox is overall very narrow - not even 16px wide?This increases the precision needed to press the button - and requires precision in a situation where just generally throwing the cursor in that direction, for it to automatically stop at the screen edge, would require so much less attention.I don’t see any good reason to not extend the hitbox to the edge, since it’s already a dead zone where there’s no interaction. 

30
Michal_Ordowski1
Richard_Silcock
Richard_SilcockNew Member
posted in Share Your Feedback
Left hand navigation - UI3 is terrible.

Hello, I’d like to share some critical feedback on the new UI3 asset panel, as it has significantly disrupted my workflow and, I believe, undermines some of the core organisational benefits Figma has always offered. 1. Loss of nested sectionsIn UI2, the Assets panel allowed nested subsections based on 'Frames' within a page on the design system (e.g. “Inputs” → “Main Component” and “Component Blocks”), so you could keep building-block elements separate from your primary component.   UI3 now flattens everything into a single folder, regardless of how many 'Frames' containing sub-components you have. For files with dozens of related components, this makes it very difficult to locate the exact asset you need without constant searching. This old method used to allow me to organise my components in an easy way. Allowing me to just select my design system > Select Inputs > Select Main component. While now I have to select my design system > Select Inputs > Search and find my main

110
Richard_Silcock
Panwei
PanweiNew Member
asked in Share Your Feedback
About Figma slot function。I very much hope to have such a feature.

Enhancing Component Flexibility with Slots: A Real-World Scenario"We often find ourselves needing to edit content within a component instance without detaching it. While a 'change once, update everywhere' approach for simple variant states is great, we really need more flexibility within those instances."Understanding the Power of SlotsThe Slot feature introduces a powerful new component property acting as a designated placeholder within a master component. This allows components to achieve both rigorous standardization and dynamic flexibility. Designers can now freely swap, add, or remove content and structural elements inside a component instance, all without ever having to detach it.When combined with Auto Layout and other Component Properties, Slots make components significantly easier to manage and far cheaper to maintain. This approach is particularly effective for use cases involving diverse content, frequent content updates, and high reusability, like those found in enterprise

130
Panwei
Morris_Craig
Morris_CraigNew Member
asked in Share Your Feedback
Constant memory issues since UI3

Is anyone else running into a lot of memory issues since upgrading to UI3?  Seems the memory management is worse than it used to be.Getting memory limit errors on files that seems much too small to justify them. Had an issue where I could not merge a branch back into main due to running out of memory.  Even running the operation on a PC with 96 GB of ram (yes, ninety six) did not fix the problem (what? HOW?!) I just tried to disconnect a bunch of frames from their component masters (with a lot of nesting) and the operation failed.  First it asked if I wanted to reopen in recovery mode.  Then the interface just went away and left me with a blank window.I use a lot of nesting to make my mocks responsive, and I build everything from components so I can use properties to configure each one how I need.  My approach has always been hard on Figma and performance regularly ground to a halt, but this behavior feels new.  Is anyone else dealing with new and more frequent memory issues lately?

181
y_toku
Figmate
ori_benyishay
ori_benyishayNew Member
posted in Share Your Feedback
New Annotations feature

This is great! Thank you very much!Also measurment  

27816
Sydnie Fultz
rubiniandco
rubiniandcoNew Member
asked in Share Your Feedback
Binding number variable to a component's text property

I have a numeric input field as a component, and its value is set as a text property called value. Pretty simple stuff, right?For prototyping reasons, I want to bind this field's value to a number variable, so I can add/subtract to this value when I press a button somewhere else on the screen. Also pretty simple stuff, right? Well, apparently not. Turns out I just found out that we can't bind number variables to text properties for whatever reason — they don't even show on search results. And since there's no component property of type number, this simple prototyping scenario I'm trying to achieve appears to be impossible. Meanwhile, if I simply remove the value property from my component, then select the plain text layer with the value and try to bind it to my number variable, voilá — now it works. Except it doesn't, because now all my fellow designers will have to manually select and edit their numeric input field's values every time they use this component.So my suggestion here is e

862
César Morel
UX-design-at-Workflow
UX-design-at-WorkflowNew Member
posted in Share Your Feedback
Forum search shall be capable to: Search in title/body, highlight matches in results, filter by open/closed issues

A productive feedback software fosters productive feedback culture! What I experienced in your Forum / Issue Tracker:✅ The forum guidelines recommend “Search before you post”. ❌ But the search function is currently very mediocre!Please make sure that one can least…Decide in which fields search shall match: Title, Body, Fulltext. (e.g. Github in:title) Highlight where the query matched in your the search results . To quickly grasp relevance. Filter by issue status: Open, Closed. You have that data per issue, make use of it! Screenshots of the current experience: 

101
UX-design-at-Workflow
Bev
Bev
posted in Share Your Feedback
Auto-layered objects outside a frame are hard to select as a whole! + other issues

I don’t think this used to be a problem, but since the new update it’s now full of bugs and I really miss the old UI. The bottom menu is a waste of space, just put it back in the top and let us use the short cuts! I have a habit of creating components outside a frame and I noticed that recently, it’s super hard to select objects grouped by auto-layout! I’m forced to put the whole thing in a frame just to do this or it will drag out individual element eventhough they’re all inside an auto-layout! Another thing about ‘Shift + I” shortcut for inserting components is that it will always prioritize inserting inside an auto-layered object closest to my cursor rather than where my mouse key is pointing, EVERY SINGLE TIME.

50
Bev
Lukas Willin
Lukas WillinNew Member
posted in Share Your Feedback
Move or Add "Spell Check" Settings to the User-Settings-Dialog

Hi, I have been searching to disable the “Spell Check”. While the Online Guide explains it clearly where to find it, intuitively I wouldn’t expect it there.To me, Spell Checking is either a user-setting or a preference of the application, not specific to the document or whatever I’m currently editing. I would suggest either moving or adding the “spell check” to the user-settings dialogue or the application-preferences.Option AOption B Let me know what you think Regards Lukas

01
Lukas Willin
UX-design-at-Workflow
UX-design-at-WorkflowNew Member
posted in Share Your Feedback
Meta: Feedback to the forum itself

Every good forum usually has a “meta” category where to submit shortcomings/proposals on the forum software itself.Due to lack of this I will post my Meta suggestion into the closest available category, which is:  Share Your Thoughts → Share Your Feedback.But I recommend you to create such a category, which is a best practise.

00
UX-design-at-Workflow
Terms & ConditionsCookie settings