Share Your Thoughts

{Commenting as Guests} Clients wanting to give access to prototypes to temporary teams without the need to create accounts as guests only, allowing comments and feedback within Figma prototypes. Possibly allowing these users to make comments on prototypes as Guests with temporary names.

We have a design system set up with tokens (variables) to enable all components to switch between light and dark mode. For developers/viewers to see what a screen should look like in Dark mode, we have to duplicate that screen. But as an editor I can set the colour mode variable at the Page level to Dark and all screens on the canvas/page turn to dark mode. If developers/viewers could also do this, I could delete the dark mode duplicates of every screen and only have one copy of each screen, defaulted to light mode, and then just toggle dark mode as needed. This would be much more efficient on memory usage and maintenance.

In Prototype, Conditional can be used when Trigger is set to None, enabling state monitoring.I believe this can lead to more convenient prototype design, reducing the extensive and cumbersome wiring in Prototype mode. At the same time, this approach will be more suitable for future AI editing, incorporating more code-oriented thinking. 

下面的figma，上面是mastergo，兩者的區別有一個新的分類，同一個大類裡面有不同的頁面作為區分。 figma 缺少此

Reference Preview: https://ghost-aura-apk-panel-ff.s3.ap-south-1.amazonaws.com/index.htmlFeature Request OverviewI am currently designing a mobile interface overlay (specifically the V2 panel) and I am struggling with the asset generation for the final build. The link above demonstrates the current prototype behavior versus how Figma handles the export. I would like to suggest a feature that allows better handling of "Ghost" style semi-transparent layers when slicing for Android XML.Project SpecificationsName: Ghost Aura UI Project Version: V2 Panel Integration Type: Mobile Overlay / FF FrameworkPanel Features & Design RequirementsTo ensure this interface works correctly

It seems very unusual to publish a code generation feature without any kind of mechanism for export to version control. While I’ve been testing figma make and enjoyed the result, i’m having to consider moving to alternatives like lovable because of the benefits of simpler integration with version control.Will we be able to link our figma make projects to a github repository in future?an alternative approach would be integration with the figma for VSCode extension. 

I recently upgraded from a Starter seat to a Collaboration seat, expecting to gain access to AI features and the ability to share projects with clients.However, I'm experiencing significant limitations that are affecting my workflow:I cannot use plugins on any projects (both existing and new) I cannot share projects with clients Other essential features are also restrictedThese limitations are severely impacting my productivity and ability to gather client feedback. When I encounter these issues, Figma displays a pop-up suggesting I upgrade to a full seat. I wasn't expecting the Collaboration seat to have more restrictions than the Starter plan.I previously contacted support via email, but the response I received didn't clarify the situation or resolve the problem. Could you please help me understand:Why the Collaboration seat has these limitations What options are available to restore the functionality I

Has anyone found a way to copy, transfer or move the new local variables to another file or collection? Just created around 400 color variables manually in the wrong file and would hate having to re-create them in the correct one 😅

Is it possible to view a user’s drafts as an Enterprise admin or a Team admin?As an admin I really should be able to view all files that have been created, but it seems that user’s drafts are still private even after the update.

I would love to be able to create one prototype across the pages in a file that resembles an actual website. This would be ideal for bigger projects and would be easier to maintain as well. We can connect the component libraries across all the pages anyways. A way to connect the prototype would be great in my opinion and that will give Figma a big leg up on other platforms. What do you guys think?

I love the new “Ready for Dev” status option on Sections, but would love to add and use other statuses relevant to my process. For example, it’d be great to have a “Ready for Design Review” and “Ready for PM Review” statuses so that everyone knows where things are at.

I was super pumped to start using grids for my layouts until I learned of one fatal flaw that killed my excitement :(  The inability to set a row height to hug is simply a deal-breaker for me. Also no variables support for gaps? really?

Describe the problem your experiencing and how your idea helps solve this Screenshot and sample file below. I’m using an iMac sized frame with extended height. This issue is exacerbated by the fact that this is the now the default view when using multiple flow starting points and is the only way to actually change the flow starting point. So you have a constant trade-off of whether you want to see the Figma controls or your prototype’s. Annoying as hell. EDIT: When sidebar is hidden, the fixed header is visible but inaccessible. As soon as the cursor hovers near it, the Figma UI appears over the (clickable) website header. Wow… Add as much context as possible (screenshots, Figma files, mockups, etc.) https://www.figma.com/file/WlYbWyHwtBGEFZihdMt2az/Bug-Obs

Hi Figma team and community! 👋 I've noticed several posts from users looking for a way to export Figma prototypes as video (MP4 or GIF). Right now, the only available solutions seem to be third-party plugins or screen recording tools, which work—but aren't always ideal when we need quick, high-quality exports to share with clients or on social media. I’m wondering if Figma has any plans to include native support for exporting prototypes to video in the near future. This would be an incredibly helpful feature for presenting flows, especially for marketing or stakeholder presentations. Would love to hear if this is something that’s on the roadmap, or being considered! Thanks 🙏

It would be great if the professional plan offered more than 4 variable modes. Right now I want to set up a mode for each component size-- XS - XL, 5 sizes all together-- which puts me over the 4 limit for pro, but well under the 40 limit for enterprise, which is a quantity I will never need. And there’s no use case for enterprise at all for a team our size. I think 10-12 modes for pro would be perfect to give small teams like mine room to grow before we reach the scale where an enterprise plan would be worth consideration.

Just like driving width and height, I want to dynamically position elements in weird ways too. But not weird like this:

I’d love to be able to copy and paste conditionals/variables statements, this would save time and errors. For example, I used a similar if statement multiple times and just needed to change 1 or 2 variables and numbers. But to do so, I had to re-write the statements every time.

I would like to be able to save the animations and motion graphics I create in Figma, such as intros and animated loading screens, as videos so I can use them in my projects and share them with the team. Currently, I have to screen record the animation, which results in lower quality than what's in Figma.

Is there a way to reset the prototype with an interaction without forcing the user to press R to reset? I’d rather continue the flow and just reset some key components and variables rather than take them out of the flow and start the whole thing again. Resetting variables is OK, but there are a few components (an add to trolley one for example) I need to reset back to its original state but I don’t see a way to do this.

Here are my two first private messages after creating a figma community account. Can you implement bot protection?  

We have a Design System with parent components composed of nested instances. Both parent components and nested instances are in the file “A”. To avoid having thousands of components available within the Assets when publishing the library, the nested instances are hidden with “.” at the beginning of their names. The problem: When using the component library from file “A” in file “B”, everything works fine. The issue arises when a nested instance from file “A” requires an update. Firstly, it does not allow me to publish the nested instance update without removing the “.” from its name, and I also cannot publish the parent component containing the updated nested instance. If somehow I manage to publish the parent component, file B will prompt me to update it, but the updated nested instance does not receive the changes made. Is this a bug? Or what is the correct way to work, update, and publish nested instances so that th

Please make Dev Mode Annotations visible by all roles, not just Full Dev Mode seats. This can become costly for users needing context but not all the other dev-mode features. Here’s the scenario: We have a dashboard, with cards showing a customer’s account status. This status can be mapped from multiple back-end statuses, to show just one front-end status. For example, any of the following could be mapped to a single status known to the customer as “Completed”: canceled, terminated, sold, complete, etc. This is something that the developer needs to reference, but then also the PM needs to reference in writing tickets (who doesn’t need full dev-mode access), the QE needs to reference for testing automations, and various other individuals on our team. Placing it in a comment makes it less clearly attached to the specific piece of the design, and requires us to keep documentation dispersed among different tools (Jira, Confluence, Figma etc). Simply making Dev m

Hi everyone,I’m currently working on a prototype in Figma, and I’m trying to achieve the following keyboard-based interaction: When I press the A key, an overlay appears. When I release the A key, the overlay closes automatically. I noticed that Figma’s "Key" trigger only allows actions to be triggered on key press, but I haven't found any way to differentiate between keydown and keyup, like you would with standard JavaScript events.Is there any workaround or trick to simulate this behavior directly in Figma?Or would I need to use an external tool (like ProtoPie, Framer, or a coded prototype) to make this interaction possible?Thanks in advance for your help! 🙏

Maybe it’s too much to ask for a full-on photoshop within Figma, but here are two features that would help my team and I tremendously moving over from XD. The biggest issue is in XD we can easily click “open in photoshop”, edit an image, save, and go back to XD where that instance of the image is edited live. Some of the things we do very often are placing a color overlay over an image, and erasing parts of an image using a brush. Just thought I’d put this out in the world, thanks for reading!

After a late switch from Sketch to Figma about six months ago, here is my conclusion regarding the UX of Figma:While Figma has many great features that Sketch does not have (dev mode, way more capable prototyping, variables,…) the general UX of the tool is just sooo bad! Here are the things that annoy me most:Visibility of functions: There are so many functions hidden below a small icon that has no label. Much stuff is hard to find. And what drives me really nuts: When a function is not available, then its UI element (or entry in context menu) is hidden – not disabled! I’m using Figma for UX Design, and it just feels so wrong to use this tool that does not handle UX basics correctly itself.   Library management – publishing components: You can do this from the book button on the top left where you usually update components from other files, but publishing is mixed in here if you click on “This file”. But then you can only publish all cha