Suggest a Feature

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.

Every time I use bulleted text, the actual bullet point is a slightly indented and doesn’t perfectly align with the left margin. Are there any additional way to have greater control text indentation and control hanging bullets? Plug-ins? Thanks.

Favourite fonts will be shown on top of the list, while the rest of it will be shown below the favourite list. We should also be able to remove and add while viewing the fonts on the font list.

This is relatively minor, but I think it would be convenient to place an eyedropper tool here (shown in mockup attached) to make it easier to access. Looks like there would be space for that… Maybe you already thought of this and rejected it for some reason.  I love Figma!outer eyedropper access 

I publish complex files about video game UI.I see my files being used and notification bar doesn’t allow me to see all names or visit those people profiles (if there is one).Seeing real names and profiles would help me feel more real connection to those who use my files, and it will keep me motivated to create more of them.Clicking on notifications just navigates me to the file page, and there are none lists of likes, uses available.  Could we have lists of likes, uses of our Community files?Maybe like in Instagram or Behance 

Hi TeamThis is must have feature in figma! With the power of AI, Uizard Wireframe empowers to digitize hand-drawn wireframes in seconds with the click of the button. It can transform designs in to clickable prototypes with ease.https://app.uizard.io/This video explains the feature -  

Hi there.I create a new thread because this one is closed: Like many, I do my resumé with Figma. And I’ve seen that the text exported PDFs have undesirable spaces inside the words.Example:Copy/paste this text and you get:“with 2 0 + years of e xperience”, which is wrong!! Of course, the MKitFPDF plug-in solves some problems but brings some others, without to say it’s not free.Did someone got a real fix for this?

When using Auto Layout for an entire page flow, not everything is spaced equally. For example, imagine a page like: Toolbar Heading Paragraph Input Button To put all of these into a single Auto Layout and give equal spacing to all of it is not typically how it’d work (eg, Toolbar + Heading might be close together, but more spacing around above and below the Input). To use the benefits of Auto Layout, I wrap these objects into their own Auto Layout frames and then use the padding within these nested frames to create the spacing between elements. It’d be great to be able to apply margins to objects (like text frames or other frames) without having to first nest them into their own individual frames. This would be closer to how CSS typically works as text elements (h1, h2, p, …) don’t need to be nested in a div to have margin added to them.

ProblemIn Figma, comments are not preserved when duplicating pages, frames, or sections. This creates a major gap in workflows where teams need to iterate on designs while maintaining a record of client feedback.This has been a long-standing request from the Figma community for years, and continues to be a significant pain point.Real-world use caseIn a typical client workflow, we:Collect feedback directly in Figma via comments Duplicate a page or create a new version to begin revisions Need to reference and resolve original feedback as changes are implementedCurrently, duplicating a page removes all comment threads, forcing teams to either:Manually recreate comments (time-consuming and error-prone), or Constantly reference a separate file/page, which breaks workflow efficiencyImpactThis is a huge pain point across our entire organization, especially in fast-paced agency environments:Slows down iteration cycles Increases risk of missing or misinterpreting feedback Creates disconnect bet