Suggest a Feature

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.

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.

Hi Community, We use Figma (iframe) embeds in our technical documentation extensively and we would like to enable our colleagues to leave comments via these embeddingss instead of visiting the design in a separate browser tab/ window. What’s the proper way to do that? thanks,

I want to be able to define "Min" and "Max" values when the spacing between objects is set to "Auto." This would give designers much better control over responsive UI behavior, preventing the gap from getting too large or too small when resizing containers.

APIs have become the backbone of modern enterprise architecture. From enabling seamless integrations to powering digital products and partner ecosystems, APIs are central to how businesses operate and innovate today. As organizations expand across cloud, hybrid, and on-premise environments, the number and complexity of APIs continue to grow.However, managing APIs at scale is no longer just a development challenge—it’s an operational, security, and governance challenge. This shift has led many US enterprises to adopt managed API services as a strategic approach to streamline operations and reduce internal burden.Instead of relying solely on tools, organizations are partnering with experienced providers to handle the entire API lifecycle, ensuring reliability, scalability, and continuous optimization.As API ecosystems grow in scale and complexity, managing them effectively becomes a critical challenge for US enterprises. Traditional approaches that rely solely on internal teams or tools

Hello, I’d like to raise what I believe is a very reasonable and long-overdue request.Figma is a professional tool, widely used across design and development teams, and charged at a premium rate. Yet, it lacks a fundamental feature for UI design validation: the ability to float a frame or image in a transparent window above other apps, such as a mobile simulator.This is an essential need when comparing a design with a live implementation, particularly in mobile development. Tools like Overlay (which is currently unreliable), ScreenFloat, or even basic screenshots partially solve this—but these are third-party workarounds for something that should be native to Figma.I’m surprised this hasn’t been addressed yet. It would be extremely useful to: Export or pin a frame as a semi-transparent floating window. Overlay it on top of a running app or simulator to check pixel precision. Adjust opacity and toggle click-through mode for interaction below. Is there any official plan to support th

We're on the Organization plan and our team has 600+ design files across 20+ projects. We need to create a local backup of all files in .fig format.Currently, the only way to get a .fig file is through File → Save Local Copy, one file at a time. At this scale, that's not practical.The REST API supports JSON file data and image exports, but not .fig file downloads. There doesn't appear to be any admin tool, Organization-level export feature, or bulk download option for this either.Given that Organization plans are designed for teams operating at scale, is there a supported way to bulk download .fig files that we might be missing? If not, is this something Figma is considering?

Hey there.As you know, we can already apply multiple fill color or apply multiple variable color to a single frame. But we can only apply one “style” to a single frame. The problem comes when you want to give a single frame multiple effect. assume I have a focus ring, and a subtle shadow. my elements might sometimes have shadows, and sometimes have a focus ring, and in some cases, they might have both. for now, if I want to create styles, I need to make 3:focus-ring-neutralshadow-smfocus-ring-shadow-neutralI understand that the logic behind the style was to make layers of attributes (styles) all saved as one name. but in cases you want to mix a few things, you have to save all combinations that you might use. is it possible that to be able to add multiple effect style to a single frame instead of creating more customized styles? Image below shows how “Fill” has a plus button and can have multiple values (Variable or raw value), but Effects, like other “Style” only can be applied once: 

I have multiple sub-flows within my product and I’d like to be able to link to an overall flow rather than a page to help streamline and clean this up. That way, if I change the sub-flow, it can still link to that flow and I don't have to change each link. Is this possible?

Another nice addition would be to connect your FigJam files with related Figma files. So as not to rely on file naming. Creating links between the two would allow for easier navigation and discovery from others in the team.

Describe the problem your experiencing and how your idea helps solve this On both chromebooks and traditional computers PWAs are hugely useful for reducing browser chrome to maximize the app experience. Additionally they can provide significant performance benefits, even enabling limited use of the app while the user is not connected to the internet. It would be great to see official PWA support added to the app. Additionally the PWA could likely replace the need for the Android app (use TWA instead) and iOS app.