Suggest a Feature

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:

Custom Happy Meal Boxes are a perfect packaging solution for restaurants, fast food chains, and food businesses across the USA that want to attract kids and families. These boxes are designed to be both functional and visually appealing, helping brands create a fun dining experience. Made from high-quality cardboard, kraft, or eco-friendly materials, custom Happy Meal boxes are sturdy enough to hold burgers, fries, snacks, and small toys securely. With advanced printing options, businesses can add their logo, bright colors, cartoon themes, and promotional messages to enhance brand visibility. In the competitive USA food market, attractive packaging plays a key role in influencing customer decisions, and customized Happy Meal boxes help companies stand out. They are lightweight, easy to carry, and can be designed with handles for convenience. Many brands

I’ve already started using the new slots and I find them amazing, but I think it’s very limiting to prevent the use of grid layout. 

I often need to update component instances on a specific page without affecting those on other pages. However, Figma currently requires me to go through every instance across the entire file, which is frustrating — especially when working with versions and wanting to preserve old designs. While the "Review Updates" panel could help, it actually makes things worse because instances are not listed in order. For example, instance 1 of 34 might be on Page 3, while Instance 4 is on Page 1, making it incredibly tedious to track and update only the relevant ones. A "Update on Current Page Only" option would be incredibly useful, allowing users to selectively update instances only on the active page, without affecting other pages. This would greatly improve workflow efficiency, especially for large projects with multiple design versions.Please make this a feature.Thanks!

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)

I regularly need to work with screenshots of webpages, which can be a couple thousand pixels tall. I need these images to be actual size. Can’t do this in Figma cause it automatically scales large images down. I know there’s a plugin but this seems like a silly thing to rely on a plugin for, there should be an option native to Figma that lets us shut this function off. Or give us an option to scale the image back up to the original dimensions? (even if the quality’s going to get wrecked) This has been such a huge thorn in my side! Please & thank you!

Hi Figma developers! It turns out that exporting Figma fonts in JSON format provides the result that looks smth like this: "style": { "fontFamily": "Quattrocento Sans", "fontPostScriptName": "QuattrocentoSans-BoldItalic", "fontSize": 72, "fontWeight": 700, "italic": true, "letterSpacing": 0, "lineHeightPercent": 100, "lineHeightPx": 84.375, "lineHeightUnit": "INTRINSIC_%", "textAlignHorizontal": "CENTER", "textAlignVertical": "CENTER" }, for a page like this:

Hello, it would be nice to have the option to insert floating components inside text (like Emojis). Use case would be for signs or infos in complex dashboards. Its a hustle to do this now manually and also set kind of boundingboxes to sync different heighs of text and component. Regards

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 idea

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.

Hey there! I was also wondering if it is somehow possible to include also the layer of variant controls to be exposed or hid! I often have cases where I need to nest base components e.g. an icon wrapper providing me with the ability to select certain sizes, or color overrides and boolean props of an icon. I am now able to expose all of those or none, but I can’t restrict the users to only be able to select just some of those. What do you think about it?

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

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

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.

When I select and drag a slide in the sidebar of Slides, I expect it to be duplicated, just like it would be in Keynote, Google Slides, or like any other object in Figma or other apps.Every single time I work on a presentation, I option drag to duplicate a slide, then accidentally overwrite content that I needed.

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.

The official Figma MCP server currently supports Design files and FigJam, but not Figma Slides. This is a significant gap.Use case: We use Claude Code with the Figma MCP to generate designs programmatically. Being able to create and populate Figma Slides decks via MCP would be a game-changer for our agency workflow -- we produce dozens of presentations per month (pitches, case studies, client reports) and want to leverage AI to draft them directly in Figma Slides.What's missing:create_new_file only accepts "design" and "figjam" as editorType -- needs a "slides" option use_figma / get_design_context should work with Slides files (reading and writing slide content, speaker notes, layouts) Ideally: slide-specific primitives (add slide, reorder slides, set slide transitions)Why it matters:Figma Slides

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 sca

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 t

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?