Your opinion matters! Tell us what’s working (or not).
Recently active
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.
Hi Figma team,I'd love to see sorting preferences persist across sessions in the Projects view. Currently, every time I navigate into a project and return to the home screen, the sort order resets to default.Our team numbers all projects (01, 02, 03…) to maintain a clear workflow overview. Having to manually re-apply alphabetical sorting every single time is a small but repetitive friction point that interrupts the flow.It would be great if Figma could remember the last used sort order, ideally per user or workspace. This seems like a relatively simple improvement that would benefit many teams who rely on consistent project naming conventions.If this is already possible and I'm missing it, I'd love to know how.Thanks for considering this.Best,Justin Eleveld
I started to try using agents to help find some holes in the my designn system but I asked it to make a simple one variable change and it disconnected everything variable in my whol design system. Losing hours and work. It could not fix the problem. I will not be using figma agents again. Has this happened to anyone else??
Did Figma do a rug-pull with Agents recently? (< 2 weeks) Previously, with the exact same level of detail and instructions in prompts, I was singing Agents praises. This week it won’t follow simple instructions and each time admits it’s not paying close enough attention. Did Figma make a conscientious decision to downgrade underlying LLM?Based on recent utility, I’m better off doing it all myself. Not even out of Beta yet and already garbage.
I was waiting half a day to get access within Figma to a file… and I saw I had 3 emails telling me to accept access OMFG WHY!?What for? I used to work with Figma Enterprise and there was no “acceptance” if you asked to edit… it just turned on to be edited voila… And what’s with the time of waiting for actually getting access after the person agrees on the other side?
I’m working with a team on a large project, and we have a complex file structure. Removing the file previews has made it much harder to navigate our file system. Each group of files has its own color; previously, you could just glance at the main screen and understand where to go or see the file name in the preview. With only the folder icon and name, it’s much harder to remember where something is located. Please give us the option to revert to the previous interface with clear file previews.
Everything is already mentioned in the title 🙂.These may already be planned features, but having the ability to animate changes in size and weight using variable fonts would be a real must-have for Figma motion. I’d also love to see support for SVG morphing animations, allowing users to animate the transformation of an SVG’s shape by editing and animating its anchor points and handles.
Not sure if we like the current placement of the new Agent features. It sits right over active screen elements while working, so the chances of accidentally clicking it are super high and pretty annoying.
I am building agents that are generating lots of designs, and I need to be able to organize those designs automatically instead of them just kind of gallivanting in my drafts.
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.
The management of seats is absolutely terrible. We have unused seats, and there is no way in the user interface to remove them to avoid being charged in the next billing cycle. If this is automatically not charged, it is not explained anywhere. The most terrible experience I had managing subscriptions after 25 years of actively using internet.
Why did Figma choose to remove the type size from the panel.Not a good move. We create styles H3,H4, etc figma used to display: Body copy - 14pxNow… we have to click on style to see what the dimension. Not a good move. No one memorizes what size and line spacing H2 could be…You tried to make the panel minimal and ended up adding extra unnecessary clicks. Knowing a type size is crucial. Bring it back to surface please.
The bottom part of the icon feels too visually dense — all the elements blend together, which creates a lot of visual noise. This makes the icon hard to distinguish and difficult to find quickly among other desktop icons. I think simplifying this area or improving the separation between the elements would make the icon much more recognizable at a glance.
When I have a typography style applied, I want to be able to change to a pre-saved option as easy as I can do it for colors. Now if I detatch the typography style, I want to be able to apply another style right away. I think what can help is to show the “library” select component when clicking on the “apply styles” icon button. When I click there I expect to see Text styles I have saved. However, the ones that are shown on my image I didn’t create and the only one library added to this file is not he first option being displayed. It is so frustrating and difficult to find the ones I have save and added to the library.
Hello, good day.I’m experiencing serious issues with the new Figma UI update. Many essential tools — such as padding controls — are missing or hidden.Please do not enforce this new version. The previous UI was much better, clearer, and far more efficient for designers.This new version has no advantages, feels confusing, and makes our workflow significantly harder.
I’m posting this as a former paying subscriber because the usability problems became frustrating enough that I cancelled my subscription.My main issue is not what Figma can do — it’s how unnecessarily difficult it is to continue existing work.I’m using Figma for an app project, and something as basic as reopening the same project, finding the correct working file, returning to Figma Make, and locating the AI prompt workspace has repeatedly been confusing.The biggest problems I’ve experienced are:Figma Design, Prototype and Figma Make feel disconnected. It is not obvious how to return to the same Make/AI workspace I was using previously. Similar project cards make it unclear which file is the real working project. Navigation changes depending on which part of Figma you are in. Important controls are hidden or difficult to discover. I regularly spend time trying to find my own project instead of working on it.A user should be able to open Figma, see their active project immediately, clic
📣 Don’t make the same mistake we did in attempting to clean up some projects by taking advantage of nesting folders 🚨If you move a top-level folder from your “All folders” section into another folder, then realize you actually want it back at the top level (perhaps due to the inherited permissions not being suitable, or just because you re-thought your organization strategy) there is apparently no way to reverse this change.You would think you could drag the folder back onto the “All folders” option in the sidebar: Nope! Or perhaps up to the team name that shows at the top of the page… Nuh Uh! Maybe right-click > “Move…” on the folder will offer the “All folders” option, maybe even under the “All” tab Negative! We looked through all the documentation and best practices guides we could find and this appears to be a fully-unmentioned gotcha 😖The AI support agent “helpfully” suggested manually re-creating such folders back at the top level, reapplying permissions as desired, and fin
It seems a little weird that you can’t copy a link to a layer within a component instance. I understand why this might be technically difficult, but it has been a real pain point for our engineers recently who would like to be able to point their AI coding tools to layers or frames inside components and who aren’t attuned enough to what’s going on inside the layer hierarchy to know why they can copy links to some things but not others.
Yet another UI update that ruins the workspace.Now a whole column width is reducing the workspace size, created to accommodate one AI agent button that I have no interest in using. You’ve moved the library and assets to a less usable place because you couldn’t figure out how to add the AI agent somewhere else? How can I roll back this change to the version that actually worked?
Figma, Auto jump to next comments when previous comment is resolved is frustrating to use. Most of the times when we resolve a comments we tend to look and ponder on screen if we want to add any new comments. When it auto-jumps we need to search for the section again which is really bad experience. Please look into this.
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
I don’t know why did figma launched sites if they wanted to bury it somewhere in the corner and not look at it as a product. I have gone through multiple reviews of people from Reddit to Youtube and everyone is saying that the product is super immature right now from SEO to CMS to animations. So the question is when is the team going to improve it to a point that people that work on Figma can stay on Figma for other work as well?
根据用户习惯默认锁定缩放比例
The shortcuts Alt+B and Alt+N are prone to accidental triggers. Since the two keys are adjacent, mis‑hits are fairly common in real‑world operations.The core issue lies with Alt+N, which triggers "New File", and the high recovery cost after an accidental trigger: when you accidentally create a new file and close the window immediately, the blank sketch remains. Users have to navigate to the file directory and delete it manually via the right‑click menu.In my view, the root problem is not the accidental triggering itself, but the severe consequences and high recovery overhead it brings. It generates unwanted files that require extra cleanup steps, which easily interrupts the ongoing design workflow.Here are several proposed solutions:Reassign either Alt+B or Alt+N to reduce the risk of mis‑hits between adjacent keys. For blank documents with zero edits, do not save or generate files by default upon window closure. Enable custom shortcut configuration, allowing users to avoid key conflic
使用Agent频繁遇到无法访问PingFangSC字体的限制,希望可以解决
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.