Share Your Thoughts

Our team is attempting to migrate our Sales Team presentations from Google Slide to Figma Slides.Good Things:The design control is soooo much better than Google Slides. It’s so easy to bring in work from a regular design file allowing us to have beautiful slides.  Animations are cleaner and simpler to work with than Google Slides. Although not as sophisticated as Keynote or PPT.  Nesting slides is nice; especially when we made a Master Deck File that houses 100+ slides for the Sales team assemble decks from. Feedback:Linking is currently not a pleasant experience. 1. You can only link text links which underlines the text by default (but you can toggle the underline off). You cannot add a link to objects/images.  2. It is easy to add a slide # links, however if you duplicate a presentation file the links created stay with the original file. So you have to manually change each link again making it super labor intensive. Our team wants the ability to duplicate a sample deck and customize

As a user who does not want to create extra work for my UX team but wants to create workflows and up to date examples that persist I want to be able to“Copy as Linked” - Copy the item “Paste as Linked” - pasted item updates from copied item Replace as Linked” (Ctrl+Alt+Shift+R) Replaced Item updates from copied item So that My UX can use components the way they want and we can keep different pages up to date across figma boards by updating a screen that is the source of truth. 

We have found a lot of efficiency improvements with the JIRA and Confluence widgets within Figma Design. With incorporating more teams into the Figma ecosystem, I’ve found a lot of opportunities for building libraries and design systems and pulling in assets to Slides to build launch decks to share outwardly. We track a good amount of things through JIRA.Would LOVE Jira + Confluence widget support in Figma Slides. Atlassian and Figma work awesome together, but need it across more platforms than Figma Design only

As in chrome or any web browsers, having the ability to group file tabs will allow users that work in multiple projects, to have them organized and easy-to-find.   

The resize handles that appear when using focus view in Dev Mode or mobile preview in Figma Make are very handy. An option to display these when viewing a prototype in Responsive mode would be a very nice and helpful addition.

I know that I can export as SVG from draw.io and then drag and drop in FigJam but this does not allow me to edit. I would like to import a flowchart from draw.io in an editable format. Thanks.

I use nested auto layouts for my tables: The table is an auto layout containing columns, and each column is an auto layout containing cells. I want my table to be responsive, so I set all columns to hug, except the last column, which is set to fill, so that the table spans the whole width of its container. But in smaller screen sizes, if the screen width goes below a certain number, the last column gets clipped/truncated as it’s on ‘fill’. So I set a min-width to ensure it is not clipped. But, right now I need to hard-code the min width. It would be ideal to set the min width to ‘hug’, so that I don’t need to hard-code it or change it every time I update the contents of the last column.

1. Why I’m Writing ThisI’m sharing this as someone who deeply understands how design actually breaks—not in files, but in real products.Figma has already solved some of the hardest problems in our industry: real-time collaboration scalable design systems bridging design and development through Dev Mode But there’s still a gap that every serious team feels, regardless of size or maturity:Designs look correct in Figma, but behave differently in reality.This gap is now more visible than ever as Figma expands into product building, Sites, and AI-assisted workflows.2. The Core Problem (Observed in Real Workflows)Across teams, the same pattern repeats: Designers create visually perfect screens Prototypes simulate only happy paths Edge cases are not explored deeply Developers reinterpret behavior Issues surface during development or after launch This leads to: unnecessary rework misalignment between design and engineering avoidable UX issues in production The problem is not a

Would it be possible to have slots show placeholder UI without having to mouse over, at least at the master component level?Helps to just take a glance at something and understand the layout, also stresses me out to look at something and its just blank 😅  

IT would be great i Text would behave like colors for bulk update , When you ctrl + a. a file all text styles will be selected you can then open a list similar to variants and choose the correct text style to apply to all varients just as you do with colors Why it’s needed LLM like claude code and make disregard text styles but for dev teams using text styles is a must so we , currently we need to select each text field one by one there is not way to select similar text fields.Plugins allow to update the text style in a bulk but not as a text style just as an alerternative text .super important for maintaining clean code .

I don’t want to see some properties or values of any properties, if they are not used in the component. This is making it difficult to use the components. Example: I have a button component with Property 1 (Type: Primary, Secondary) Property 2 (State: Default, Processing) I only want “State: Processing” to be available for “Type: Primary” button. I have created a Variant of “Type: Primary” button with “State: Processing”. Currently the problem is when I use “Type: Secondary” button, I can see “State: Processing” in the properties. When I select it, the button “Type” changes to “Primary”. It would be great if the “Processing” state doesn’t show up in the properties list, since I don’t have that “State: Processing” created in the component Variants.

I’ve been working on a system-driven prototype in Figma where a global control (navbar) manages the state of multiple components (cards).The goal was simple: A button click updates a global state (for example active card) Individual components react to that state Smooth transitions (Smart Animate) happen between states (closed to open) However, this currently isn’t possible in Figma without major tradeoffs.Current limitations: Variables can update global state, but components cannot respond to them in a way that triggers variant changes with animation Smart Animate only works when explicitly defined through interactions such as Change to or Navigate, not when state changes indirectly To achieve smooth animation, we are forced to duplicate entire frames or create complex variant systems, which does not scale What this leads to: Either you build a scalable, system-driven prototype using variables but lose animation Or you build animated transitions but end up with exponential f

Pinning plugins to right-click menu A new section with the plugins you pin (it’s an option when you right-click a plugin from the regular menu). I don’t think I could explain this more. Pinning plugins to toolbar I think it could look something like this: When you would click the icon, the plugin would pop up like in illustrator, only it would have the UI of the plugin. It could only show up to 3 icons and the rest would be in a “more” menu. You could pin 3 plugins. If you do this, two more slots appear, showing the two most recent plugins you used that aren’t pinned but have been added to the toolbar. when an app is pinned like this, you can move it around like normal. However, when you launch it from the top it gets snapped to the top under the icon and the close button would minimise it. If I should make a hole Figma UI redesign, just ask.

Hi, I have a component that has a video (in order to play it in prototype mode). In today’s update, it’s displaying a “video” label and a big “play” icon on the canvas. While I think it’s nice to preview a live video on the canvas, I also want the ability to hide this elements (since they’re not part of the design specs). I was wondering if there’s a way to hide this? (the attached screenshot is a good example of specs that I often attach and I don’t want developers to think that those elements are part of the design).   

I'm looking for a way to implement an interactive 3D viewer in a Figma prototype, and would really appreciate any help or insight. I'm currently facing the following issues:Issue 1:In some demo videos, a 3D viewer UI appears near the end with interactive controls, but it seems to be rendered in an Anima web preview, not within Figma's native prototype view. I’m trying to figure out how to achieve similar 3D object rotation and interactivity within Figma’s prototype mode.Reference Videos: Ref 1: https://www.youtube.com/watch?v=qIC3Mga68hg Ref 2: https://www.youtube.com/watch?v=A3ZPySpuH9o (Reference time: around 8:40) Issue 2:I tried using Spline, but the maximum import limit is 60MB. My model is 105MB, so it can’t be imported. I also couldn’t find any info in the paid plan that would allow for a higher import limit.So I’m looking for alternative tools or methods that can support larger 3D files and integrate with Figma.Tested Plugins: Simple 3D Viewer 3D Widget These only embed sta

The problemFigma's X/Y system always measures from the top-left. This works perfectly for positioning elements near the top or left edge, but becomes a friction point when working from the bottom or right. To place a square 24px from the bottom-right corner, I have to manually calculate the values or use a dummy reference object as a workaround - every single time.Position panel ideaAdd two optional fields alongside X and Y:R - distance from the right edge of the parent frame B - distance from the bottom edge of the parent frameWhen R is active, X becomes derived automatically, and vice versa. Same for Y and B. No new paradigm to learn - just four directional inputs covering all four sides.This is intentionally separate from constraints and Auto Layout. Those solve resizing behavior. This solves static precision placement - a much more common need.Grid origin ideaLet the ruler show dual-origin measurements: 0 at the left and 0 at the right simultaneously, counting inward from both edge

Is there any work currently being done to allow a mobile navigation in a hamburger menu for Figma sites.None of the navigation blocks have this option. in the mobile component and even when I create components with an overlay interaction, the overlay will not appear when I use the component in Figma sites no matter what I try.This is a pretty big limitation to one of the most common patterns in mobile UI.Is there any way to accomplish this that I am missing?

We'd like to be able to create a new named version within the version history of document via the REST API. For our use case, we export data out of Figma to be consumed by our internal app, and we'd like to make sure that there is a named version associated with that export so that in both Figma and our app we know the state of the document at the time it was exported.

Lately I’ve noticed that when I have several nested components, I would only like to be able to modify some and not all. This would allow the component that draws on other components to have efficient adaptability in its contextual use. I am setting the variables for the Button component using variables and would not like the size property to be exposed so that the component has a desired behavior based on the active variable.

Dear Figma users! I was wondering if I could make a suggestion. When you create a component like a button and you have nested instances, like the button text (which is an atom component) would it be possible when you nest it to choose only the properties you want to have included in the button component? In my case, some of the properties are duplicated, like the state of the text (default, disabled) and also the state of the button, and I would like to only have the ‘fill in text’ property available in the right-hand side panel. I would like to select which of the properties of the nested component would be available in the main component. What do you think? Is this something you might find useful in your work?

Currently, Figma allows exposing properties from nested components, but all properties of the nested component are exposed together. There is no way to selectively expose only specific properties.ProblemIn many real-world design systems, this becomes limiting.Example: I have a Button component with a nested Icon component. The Icon component has: icon-size (variant) icon-instance-swap (instance swap) In the Button, I only want designers to change the icon (instance swap). I do not want to expose the icon size, as size should be controlled by the Button design. With the current behavior: Exposing the nested Icon forces all icon properties (size + swap) to be exposed. This increases cognitive load and breaks component constraints. Why this matters Design systems often use building-block components Not all nested properties are meant to be user-facing Designers need guardrails, not full internal control This leads to cleaner APIs, fewer mistakes, and better adoption

I’d like to suggest the ability to expose fill properties—specifically image and color fills—as editable component properties in Figma. Use Case: In designing components like cards, avatars, or thumbnails, it’s common to have a placeholder image or color that needs to be customized per instance. Currently, to change the fill, I have to drill down into the component’s layers and manually adjust the fill, which is time-consuming and prone to errors.  Proposed Solution: Allow fills (both image and color) to be exposed as component properties, similar to how text and instance swaps are handled. This would enable users to change fills directly from the right-hand properties panel when selecting a component instance, streamlining the workflow and improving efficiency. Benefits:  Simplifies the process of customizing components with different images or colors. Reduces the need to navigate into component layers for simple fill changes. Enhances consistency and usability in design systems.

I cannot find an option to remove color from a chip in gradients. Figma needs to add the ability for users to select “no color” for gradient chips. This feature has been available in Illustrator for years and is essential for creating transparent gradients that interact with their background. In the attached screenshot, I am unable to achieve what I need because I have to select a color chip. I want to be able to fade that last color and create a gradient between the blue or green on one end and no color on the other, so that, whatever background the gradient is over, it uses that background color. Instead, I have to create a separate asset for each background color that I want the gradient to interact with. This would be elegantly managed with a single asset if Figma allowed choosing a “no color” chip in gradients.

I would love to see some improvements for the translate to feature: Be able to set default language maybe even create a favorite collection of languages. I often have to create three language version and it would be useful to have quick access to them. Add a ‘Do another translation’ button to the succes window. Now the only option you have is to undo or close the window. In order to re-use, which I often have to due to the selection limitations, I have to go back to the feature menu and look up the feature again.

When I swap overlays, I expect “On Click > Back” to swap back to the previous overlay. But it doesn’t work like that. I suggest adding a “Swap overlay back” action. It will help in cases when several overlays lead to another overlay and the specific previous overlay is known only while interacting in a prototype.