Share Your Feedback

I ran into a common Figma Prototype issue:when the first animation uses After Delay (e.g. 10s auto-play for a hero carousel), it doesn’t start in Present mode unless the page is refreshed.Small preview works. Full Present mode doesn’t.The delay never starts, and progress indicators stay frozen.After some testing, I realized this is because the starting frame doesn’t reliably trigger initialization, so After Delay has no real “entry point”.My workaroundInstead of relying on time-based logic on the starting frame, I switched to event-driven triggering: On Mouse Enter (or any explicit interaction) Immediately navigate to a transition frame From that transition frame, start After Delay (10000ms) Then move to the next carousel slide This transition fram

Hi Figma, is there plans to move the right sidebar content so the component properties and the Appearance variable modes are closer together?  Having the Position and Auto-layout sections in between really disconnect the component properties and the variable modes. For smaller screen size or when there’s multiple component properties, the variable modes can easily be fully hidden down, which makes it harder for designers to know there’s additional settings for a component.   

Dear Figma product team, does the UI of UI3 need to be updated again? Compared to the last UI update, many new features have been added. Do you need to update the UI now, from visual to UI to UX? Let me urge you to update it

Can’t say how disappointed I am with the Make function of Figma. Very overcomplicated way to view, modify and export the files. All kinds of exotic explanations of how to possibly view the files of an application, until Figma;s AI itself admits, it’s actually not possible, nor is it possible to export into zip files. Modifying a Make is possible but insanely clunky. Today, I regret to say it’s little more than a prototyping gimmick that may be useful only for early stage ideation.

When creating a component, I might use one setting of the extended collection, however, it always fixes the "Default" mode, which means, if I want to change the mode in an instance, I have to manually pick that mode regardless of it being applied on a parent container.Ex: A Collection with expanded brands, and dark and light modes. If I decide to use Brand X (not the default brand), it immediately applies the light mode, and every time I want to use the instance of that component, I need to manually set it to Dark mode even though the dark mode is used in that specific frame or section.I don't know if this is the intended behaviour, and if it is, I would suggest to consider changing it and always inheriting the mode from the parent unless otherwise stated.

Design files BADLY need a way to organize old and regional design pages. There is so much happening in some files because of globalization that we REALLY need a way to create folders so that people don't get confused and look at old or in design process work.  I would jump off Figma in a heartbeat if another program did the same thing and allowed for such a structure in side of the files.

Right now, when I export a PDF from figma, I expect it to be like a regular PDF from any other software such as illustrator. However, when I look at the internal structure, some things are in an XFORM object, other things are not, text has redundant copies and are masked by other shapes elsewhere in the hierarchy. things in frames are similarly structured in weird ways.This makes it impossible for screen readers to read it, and it makes it impossible for me to use Figma to design stuff for use in PDFs, even though figma does support exporting to PDF. 

After making changes to my library file, two things happen:Sometimes it takes a really long time for the file to recognize that changes have been made and prompt me to publish the library; It takes too long for the library updates to show up in my design filesPlease improve this.

This thread is here for you to share your thoughts and suggestions about the Figma Forum.We’re proud of the work we’ve done so far, but we know there’s always room to make things even better.
Here’s some prompts that you can use:What are your thoughts on the forum makeover of January 2025? What do you like the most? What have you struggled with so far? / What are the top three areas that need improvement? What would you like to see us implement next?If you spot a bug or have any feedback, drop a reply here — we’ll do our best to respond and improve!

I’ve been encountering several recurring issues for quite some time:When clicking a version link copied from a past version, the Versions panel does not consistently auto-focus or highlight the selected version. Sometimes it works, sometimes it doesn’t, and the behavior feels unpredictable. There should be a clear way to distinguish or filter manually created versions from autosaved versions, instead of mixing them together. I work at a bank with hundreds of projects and daily modifications, so a search function is necessary to quickly locate a specific version. Scrolling through a long list of versions is mentally taxing; there should be an option to filter versions by date. I often accidentally try to edit a file without realizing that I’m viewing a past version, as Figma does not clearly indicate that the file is in view-only mode.

I just used up 300 credits for it to try to use the fast apply tool and fail and then tell me to do it manually - This was just a find and replace of a field name across a few data files. With the 3000 monthly cap - ill get 2 days worth of work.  

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’m shocked, to be honest and you guys should consider changing it. I just tried to get the local variables and use them in my vscode project. 

I am writing this after having lost time on rewriting annotations multiple times because lost after clicking outside. The problem occurs mostly when wanting to get back to Move tool by clicking the icon in the toolbar. Replicate:Press Y or choose Annotation tool Click the frame on canvas Type your annotation Do not select category Click Mov tool (or any tool) in the toolbar (or select a layer) Annotation is lostI would honestly expect that the annotation gets preserved, same way it is preserved when clicking in the canvas.Otherwise, it could be preserved in edit mode, but yet not saved, like when I continue to interact with properties sidebar or scrolling.But not lost.

When viewing styles as a read-only seat/license, there’s no way to view the values used in the style. This applies to text styles, color styles, and effect styles from what I’ve seen. Hitting the settings button for a given style just opens a popover with a preview image and a repeated name for the style. The export button doesn’t seem to do anything, either.   

Folks, if we want to draw clean paths in Figma you need to give us an easy possibility to join different path strokes with each other. This is literally the only functionality besides (rarely) using picture to vector feature that I go to Illustrator for. But it is necessary I’m sure this has been discussed but that I need a 3rd Plugin like “Join Paths” for the most basic functionality can't be right.If anyone else struggling with this please leave a comment or any interaction with this so it actually gets seen.Best,Jannik 

I’m Head of Design, leading a team of ~10 designers who work across ~20 files at any given moment.Lately, I’ve been missing tons of comments because there’s not a clear way to see notifications about which files have comments that are unread vs. which files do not have unread comments. Here’s how it should work:In the tab bar, a new “Triage” tab where you can automatically switch between files where you have unread comments. Once you click on a file that has unread comments, it opens “Comment mode” where you can review the comments. Alternatively, you can “mark all as read” Finally, the Mac app should have a Badge counter that displays a count of the # of files that have unread comments. That way, you can never miss a comment. ⭐ This simple, new workflow would save me from missing comments from my team. Please, Figma - it’s time.

Displaying the frame in the interface was a terrible decision; it made the interface very cluttered.

WHEN - will Make be able to read the very design system tokens, primititves semantics and componenets that third party applications already can? I love the platform but this is such an own goal for anyone really clued up- when and why is this not allready implemented? Whats the point in figma make ifw e can’t control the design system and connect design system primitives,semantic and componenets with wrappers around shadcn components etc without doing it manually.For anyone with a modicum of development knowledge this is crazy ommission. It puts me off recommending figma. I might have to resourt to my own custom ontoligies and the daft thing is claude etc reads the darn tokens and renders to production so that kind of also knocks figma make out of the game own goal number 2. Someone please please tell me I am wrong. This seem a massive hole in capability which shoulld have been a main reason for building make to start with doh...

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, destr

Come on Figma, it's just about adding the options into the menu. I now can translate from Czech to English, but not from English to Czech, because the option is not there in the menu. Same goes for Hungarian, Romanian, Bulgarian, etc. 

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

We need support for Alt text for images added in Figma Slides. This is a major issue for us. We are using Figma Slides to create presentations and those presentations must be accessible to our co-workers who are blind or low-vision, and to set a good example for other teams.

I want to create a PDF export of my Figma files. But I need a solution to also include my annotations from Figma. Is that something Figma can support in near future?

I’ve been working on a project using Figma Make and I’ve noticed that after a while, Figma Make AI just does whatever it wants to even when I specifically tell it not to in the guidelines.md or even in the prompt specifically.I get messages from AI like this:******The user is very frustrated because I completely violated their explicit instructions to only fix the logic issues and not change the UI. They're also pointing out that there are errors in the console that show I broke things. Let me analyze what went wrong.The user is absolutely right - I completely failed to follow their clear instructions. They explicitly said they liked the UI the way it was and only needed the logic fixed.I think the best approach is to:Acknowledge the complete failureAsk them for guidance on how to restore the working versionPromise to make only the minimal logic changes they originally requestedNot make any assumptions about wha