Share Your Thoughts

When I add a video to a placeholder and play the prototype, the audio starts playing automatically. If I forget to lower the volume, it can be very surprising and embarrassing—especially when I am in a public place or an office environment.This becomes a much bigger issue when there are multiple videos in a design, such as in a testimonials section, because all the videos may start playing audio at the same time, resulting in a very poor user experience.Adding a mute option in the video preview/upload section would effectively solve this major pain point. In addition, including a “click to play” button overlay on videos in prototype mode would be another strong solution to prevent videos from playing automatically. I believe these enhancements would be relatively easy for your team to implement and would significantly improve the overall prototyping experience.I am a UI/UX designer with over 2 years of professional experience. If there are any suitable openings, I would sincerely appre

Could you add the ability to include the update icon thingy next to those nested instances which have updates available but might not have been update when the initial component update was applied, and maybe add an extra option in the instance update menu to also enable the ability to update the instance and nested instance as a short cut, or at least indicate to the user that there are nested instance updates available that haven’t been update.It makes sense that when you do an update to an instance you don’t want to automatically update those nested instances that the user may have already configured their properties, but it would still be very useful from an in application feedback context that the user is still being informed and communicated when there is a potential nested instance update that can be made but hasn’t been executed by the application.Like it could be as straight forward as have an update icon next the nested instance name on the side panel.

It needs to be easier to zero in on the specific things that were change in a branch review. For example, I have a branch where I add a simple line of copy to one frame. But when I review that before merging, it shows me an entire section without multiple layout frames in it. One of them has the new text line, but how am I supposed to know that? See the screenshot below - I made the additional text bigger so you might be able to spot the difference. But what if it was the same size as the rest of the body text? It would be better if it highlighted the specific difference and allowed you to zoom in/out at the parent/child layer level. Dev-mode has a feature that is a little like what I’m talking about. It’s the “Compare changes” that have been made after marking something as “Ready for dev” feature. Even though this doesn’t always work that well either, this would be more helpful than what is available now for reviewing branches. Dev mode change review

Hello!I encountered an issue today where children of a frame (auto layout or not) who have constraints set of any kind (Top + Bottom & Left + Right shown in video demo) will only grow in increments of 1px. In Auto Layout frames with Fill it works correctly, but not with non-Auto Layout. I think this is a bug! Or if it is working as expected, I think the expectation should change, as it does not meet my user expectation!Thank you!Sam Smith

So, in our design system we want to apply variables to our text styles to ensure consistent letter spacing. Since we want to use different letter spacing depending on the mode (light mode/dark mode), we’d like to apply these variables to the text style and assign different values to them.However, as Figma uses percentages for letter spacing, it’s not really possible to achieve this properly. Variables can’t hold percentages, and therefore we can’t fully make use of this feature at the moment.I hope Figma will soon allow us to choose the format we want to use for letter spacing globally.Does anyone have a solution for this problem?

ProblemWhen working on long-term social media strategies, we need to create both visuals and the accompanying copy. Currently, Figma Buzz focuses on visuals, but there’s no dedicated space to add or manage related text content. This forces us to switch between multiple tools or documents, which increases the risk of losing information and slows down the workflow.Proposed SolutionIntroduce a dedicated text area within Figma Buzz, similar to the text blocks available in Figma Slides. This would allow us to write, edit, and organize copy directly alongside the visuals.Why This Would Be Useful Centralizes all content (visual + copy) in one place Makes collaboration and client approvals easier Reduces context switching between tools Minimizes the risk of missing key information  

When marking up a file with comments (comment tool active), if I hold space and activate the hand tool, when clicking to drag (pointer turns into hand icon) instead of dragging a new comment is drawn on the page. Guessing this is a bug not a feature? Just would like to use the hand tool shortcut without creating new comments - this forces changing back to the move tool to cancel out each time

I’m trying to make our design system easier to search by including alternate search terms/tags in the description of the component, and it’s a frustrating experience. I can’t rename the component itself, because we want to keep naming 1:1 with an existing web framework, so I’m adding in alternate search terms in the descriptions.Using the component description works to an extent, by which I mean that the component will appear… somewhere in the middle of a long list.For example, if I search for “dropdown”, my asset panel results will contain a mix of dropdown menu items, icons with “down” in the name, the actual component I want to highlight somewhere in the middle of this, as well as some assets that are completely unrelated to dropdowns if I have other libraries turned on in the document.Many of our components are nested and contain several items for constructing menus (dropdown/item, dropdown/separator etc.) , and these are often shown with equal or more priority than the core compon

Hi all, ChallengeI regularly need to check all comments on a Prototype and it’s not always convenient to switch to Editor view to see all comments. Currently comments in Prototypes are presented per frame which requires me to scroll through the frames until I find comments.SolutionAdd the Only current page filter from the Editor view to the Prototype view comments list  Or add Show all comments filter What do you all think?Btw, I do use desktop notifications too.

It would be so beneficial to add a “Go to instances” feature to Figma, just like the existing “Go to main component” feature. In crowded design teams, it is so hard to track the use cases of a main component, since a variety of different designers may have used a single component in so many different screens and cases. Especially while constructing or revising a design system, this feature is extremely needed. It would save a lot of time and effort in trying to detect the specific needs and requirement or the necessity of a component.

Hey lovely Figma team! Wouldn't be great if we could click or right click on a design system input/variable and instantly see where it’s used across our files.

Design reviews, ideation sessions for fully remote teams. Right now we have to switch between the video calling app and Figma. It feels more natural to schedule a video call directly from Figma since we already have the real-time collaboration out of the box.

I keep punching in the same preferences for how files should be displayed in home/project/org view. It would be good to have a json or something that can just save the config. its kinda rediculous how unintuative the files and folders are set up, I get where this is comming from and what its aiming for, but at least offer option for a more intuative folders structure, easy renaming, maybe alias files, drag and drop/force open paths… cream if simply cli shell input somewhere, I mean what are we even doing? what legacy are you preserving with the lagged ‘starred files’ sidebar and million folders that can only have one parent and no children? I would even just opt out of your egosystem with the figma files intact… if that were possible. maybe you are working on the next big thing and this is just backseat driving, regardless, this has bugged be the fuck out since it launched and twise more with updates that made it even worse (you could at least in the beginning double click on folder in

The design of websites using AI in Figma Site is quite ambiguous. While designing React applications with AI is relatively smooth through Figma Make, it remains complex and unclear on Figma Site.

I tried making an AI called “Flow” by having the AI design the basic UI and the basic code and asked it to be inspired off of CluadeAI. I asked the AI multiple times, and it kept on pointing out its mistakes over and over again. This was very poor work and I was kind of angry and frustrated that Figma markets it so well but then asks you for credits. Here is a screenshot I sent it.Screenshot that I sent to it as a base to use for the UI.And- here is what it made. Also note: this was made when my credits were about to end. What the AI made.Not only is this a copyright violation, it is horrible.

When I export images/photos that were placed in FigJam file, all photos export with this thick white border. Is there workaround so that the images export as if in normal Figma design file, ie, without the border?

Maybe there’s a workaround I’m not aware of — any help would be appreciated.I’m trying to create a card component with text and an image. The tricky part is the image: it should be flexible – keep the original nested component size and support different aspect ratios across component instances (for different breakpoints). Now in the main component, I use an image placeholder for the visual. However, when I swap that placeholder with a real image in an instance, the image always conforms to the placeholder’s dimensions instead of preserving its original size/aspect ratio. I tried different auto-layout options but nothing worked.I’m looking for a way to build this so that the image resizes based on it’s own dimensions and aspect ratio, rather than forcing all images into the same fixed size.Another possible options would be for the image to always fill the card width, while the height adjusts automatically based on the image’s original aspect ratio. Is something like that achievable with

I’m noticing to make much of anything with variables, I’m creating a lot of collections that use mostly aliases. After selecting the alias source I mostly have to keep these connections in my head. It would be nice to open up all these connections in a node editor view to either make updates or check for mistakes.

Hi,The new grid feature is nice for general layout, but if you where to allow properties to be assigned to the hug/fill/fixed values of colums/rows as well as to the addition/subtraction of columns/rows and to row/column span- the grid would become much more powerful. This would allow me to create one grid component that is controllable using properties instead of having to create multiple custom grids depending on the content of the grid in a particular module/page of an application. You can obviously nest grids, which is something I’ve explored to try and solve some of this- where each cell contains another grid- but If one can dream I would also very much like to be able to have individual auto-layout settings for each cell in a grid (including grid) as well as being able to treat the column/ row as its own individual container e.g. place components in each cell of a row but then also place another component in the actual ROW.We have a file explorer type grid in our application. Tod

TLDR; Figma should stop rewriting the entire code document every time a minute change is requested. So far, I'm incredibly impressed with Figma Make. It definitely has its limitations when it comes to deeper logic, but it has been doing a fantastic job of helping me to rapidly prototype up some of my designs, and I'm excited for where it is going. The way that entire code documents are being rewritten is one of those AI code agent growing pain items that are now becoming obsolete when working with tools like Cursor where they can be negated by creating a rule that explicitly asks to avoid the practice. I would love for there to be a similar feature available in Figma Make to allow me to prevent entire code rewrites for every little change that I request. 

  Currently, an interaction (e.g., a button click) on an object can only have one destination per trigger type. If a designer wants to use the exact same object in two different flows (e.g., a "Happy Path" and an "Error Path"), they are forced to either: Duplicate the page, breaking the "Single Source of Truth" principle and increasing maintenance. Use (page)components and instances, not ideal. Use Complex Variables/Logic, which is powerful but overcomplicates simple flow branching and makes the "Prototype Settings" unnecessarily complicated. RequestA feature where a component can have multiple destinations for the same trigger type depending on which 'Flow Starting Point' is active. 

So, my company has a card component which may have 3,4,5 or whatever number of columns is needed - the same for rows. However, I cannot build a straightforward component without either: a) instead of using grid (the way the devs usually do), using regular autolayout with a bunch of max/min/fill properties. b) creating a huge megazord component with all the variants we´d need or  c) resorting to detaching.  It´d be really useful to be able to toggle rows and columns on a component instance to create really customizable and powerful components.  Would be very useful not only for cards but for things like tables (eg toggle the whole column with checkboxes or with actions) .

Is Figma ever going to allow us to collapse/expand pages in the sidebar? What about text-wrapping layer names?

I’d like to suggest adding support for viewport-based height (for example 100vh) in Figma Sites. In many real-world design scenarios, especially for web and responsive layouts, designers need a page or a specific section to always take the full height of the user’s browser viewport. Currently, this requires workarounds with fixed frame sizes or manual resizing, which breaks responsiveness and does not accurately reflect how layouts behave in production. Tools like Framer and Webflow already support viewport units, making it easy to design hero sections, full-screen onboarding, landing pages that adapt to the user’s screen height. Having a similar option in Figma, such as setting a frame or section height to “Viewport height” or “100vh”, would greatly improve accuracy, responsiveness. This would be especially useful for: Full-screen landing sections and heroes Onboarding and single section screens More realistic responsive previews without manual resizing  I believe this feature wou

I really need adaptive font sizing for text inside fixed-size text boxes, especially for Buzz.Here’s the use case:We create a creative for social media. We then create multiple sizes of that creative using auto-layout, constraints, etc. After that, we generate Bulk Create versions in different languages.The challenge is that text length varies significantly between languages - for example, French is often much longer, while Japanese can be much more compact.It would be incredibly helpful if the font size could automatically adapt to fit the fixed text box, similar to how text behaves in PowerPoint or Keynote.This feature would save a huge amount of time and effort, especially when working with multi-language creatives at scale. I believe many teams would benefit from this.Thanks in advance — really looking forward to this improvement. 🙂