Share Your Feedback

I’m experiencing an issue when copying components from Figma Design to Figma Buzz.Steps to reproduce: Create a master component in Figma Design. Copy this master component from Figma Design. Paste it into Figma Buzz. Expected behavior:The pasted component in Buzz should become an instance of the original master component, maintaining a live connection to the master in Design.Actual behavior:In Buzz, the pasted component retains all its properties and structure, but it is no longer linked to the original master component in Figma Design. The connection to the source component is lost.When I make updates to the master component in Figma Design afterward, only changes to nested components propagate to Buzz. Changes made directly to the top-level master component do not sync.Workaround and related issues:A temporary workaround is to manually insert an instance of the master component inside the component in Buzz. However, this introduces additional issues: I can no longer apply Auto La

I’d like to suggest a small but useful feature improvement for overlays.Currently, when opening an overlay, we can only apply a colored background with reduced opacity. It would be great to have an option to blur the background while also applying a color tint (blur + color combined), similar to native mobile UI patterns.

So i stumbled upon the issue that if you post a link to a branch somewhere, and merge the branch afterwards, the link still points to the merged branch. This might cause issues as its not really clear to the developers if the branch is still up2date or not. Maybe there is a possibility to somehow show that this specific branch has been merged ? or even link directly to the main branch?

I created a website using Figma Sites, but the OGP image is not appearing when sharing the URL on social platforms (X, Slack, etc.).URL: https://saionhouse.comCould you confirm if OGP metadata is supported in Figma Sites, and how to properly configure it? 

Hi Figma team,I’m currently exploring Figma Sites for personal and educational projects, and I have a question about the product’s future direction.Are there any plans to support custom domains for Education or Free accounts in the future?For many Education and Free users, custom domains are important for: personal portfolios case studies educational or nonprofit projects sharing work in a more professional way Even if this feature were offered with limitations (for example: one domain per account, Figma Sites only, or as an optional add-on), it would still provide a lot of value to non-paid users.I understand that detailed roadmaps may not be publicly available, but any insight into whether this is being considered would be very helpful for users planning long-term projects with Figma Sites.Thanks for all the work on Figma Sites — it’s an exciting product, and I’m looking forward to seeing how it evolves.Best,

I’ve just discovered this new panel for page ruler guides. With that, I’ve realized that all the guides that I had placed in the past in my files are gone… Most importantly, the new way to interact with them is a massive downgrade from the super intuitive flow there was before, and it’s buggy as hell!Now after I place a ruler, sometimes I can’t move it around with keyboard arrows even though it’s selected (showing in blue). Most of the time, I can’t delete the selected guide with the keyboard, I have to go to the right-side panel and remove it with the mouse. But sometimes, this right-side panel doesn’t even show up on selection (not that I actually want it to show up, it’s just one more inconsistent behavior).Am I the only one experiencing this? Can we just revert back and forget about this mess please? 

Previously, Figma Make let you launch a console for debugging bugs, but this feature was removed after the latest updates. Why? Now you have to publish the app and launch the console in the browser via developer mode, which is extremely inconvenient. Bring back the console!

I use Figma Sites to build websites for companies. Overall, I like it a lot. Pages are easy to create, and links and effects work well with very little effort. However, there are some essential things that I currently miss.1. Usability for non-designersI build websites for clients or colleagues who need to manage the finished website but are not familiar with design tools like Figma.There is currently a CMS feature, which allows text and images to be edited in a table. However, this does not work for all pages. I cannot find a way to make the homepage editable for other users.Ideally, every element that should be editable could be connected to the CMS in such a way that other users can manage the site exclusively through tables, without interacting with the design canvas at all.2. Quality of Life improvementsWhen I create multiple CMS collections, things quickly become confusing. There is no way to reorder collections, and I also miss the ability to create a folder structure.It would b

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 frame acts as a forced “mount”, similar to a lifecycle hook.Why this works Navigate to always re-initializes the frame After Delay finally gets a reliable start point No manual refresh needed before demos It’s not meant to simulate prod

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.

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.

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.  

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

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.