Suggest a Feature

Using overlays greatly reduced the amount of duplications in my frames, still there are flows when I start with an overlay in a given position and would like for it to be swapped with a differently positioned overlay. Currently I do that by targeting a new frame and using a timed overlay opening from that. Looks fine in the prototype, but adds few extra steps/duplications that I’d happily do without.

It would be really nice if I could pop out the variables into their own window. Currently I can only have it as a dialogue in Figma, which means it always overlaps over my design and especially on smaller screens this becomes quite the issue. I often need to see variables and my design at the same time, so moving it to a second monitor (or even on a laptop quickly switching with alt + tab between the two) would be very helpful.

Figma Make is a little bit slow right now, and I end up having to wait quite a while after I send it a prompt for it to perform the action. It would be great if we could have a tone play or some sort of indicator that lets the user know that Figma make is done with a task. This should only happen if Figma Make is not actively being viewed. 

Hey Figma team ✌🏻,Loving all the new features you’ve been shipping lately! That said, me and many others still really hoping for native Lottie support. Right now, using GIFs just isn’t cutting it. They tend to be pixelated, and higher quality versions are often locked behind a paywall. Adobe XD had this figured out a while ago, so I’m curious: is there a reason Lottie integration hasn’t made it to Figma yet? Or is it something we shouldn't expect in future?Being able to use Lottie animations directly in files would take prototyping to a whole new level. Just wanted to share this as desperate designer, who wanted direct Lottie integration more than the illustration feature. Thanks for all the great work you’re doing!

For example if I have a paragraph with a certain style applied, I should be able to override some properties individually such as italic, bold, underline, strikethrough.  I come from the olden days of desktop publishing and this was a core feature of all professional-level software — separate paragraph and character style sheets.I would love to see this everywhere in Figma, but I think an urgent need is within slides. Because in slides we are publishing actual content and it’s a pain to create separate styles for little changes like this. They are also brittle and can very easily be accidentally overridden when reformatting something. 

Adding the ability to create basic charts in Figma Slides would be great. I rely heavily on displaying data in Google Slides to present to the team along with screenshots of our product. I would like to not use Google Slides anymore. Another great addition to add later would be to import a CSV with data or a Google Sheets integration to pull the data from Sheets.

I'm the Design Lead of Design Systems Division. And our organization currently holds 1k members (Figma seats). Several of our design systems are modular and component-based, with one supporting 22 real-time dashboards and a total of 174,000 inserts of core components. These components are organized into groups, each stored in a separate library file. The libraries are linked to organisms (files), which are then integrated into templates. This structure ensures flexibility, scalability, and performance but requires significant time for library updates, occasionally leading to the use of outdated versions.We planned to develop a plugin for semi-auto library publishing/updating to reduce maintenance time and eliminate errors caused by outdated versions. However, the current Figma REST API doesn't support library publishing/update functions, which limits automation possibilities.We kindly request to Figma team to consider adding library “publishing and update” features to the Figma REST AP

It’s great that I can use variables within Text styles, but there’s a large problem with configuring font weight. I want to use number variables for my font weights. Unfortunately, if I want italics, I am forced to use string variables for my weights. Figma clearly has logic to isolate font-weight and font-style from the chosen weight configuration in the UI (as seen in CSS code output), so why can’t I configure these two properties separately and Figma recombines them on the backend to identify the font face to load?

Hello, It’s possible in the future to export a Figma frame’s on editable PowerPoint, like it’s possible on Canva ? I know isn’t the principal functionality on Figma, but I think it’s a new possibility to create 😃

Figma slides is great! One thing that our team has been missing since we’ve been using it is an option to export to .ppt. Our team works a lot on decks for external clients and we would love to use Figma Slides to do that.

In massive organisations with tons of projects and documents, we are trying to figure a way to tag them in order to facilitate our job when searching for anything.. The implementation of a tag system would be quite welcome. Here is a sample image of what I mean below :  

Summary: Allow edits to your local dictionary. Details: You can accidentally add a misspelled word to your local dictionary in Figma, but they don't give you as the user or their support / engineering team to remove it. That misspelled word will just never be spelled checked for you in your added misspelling again. Our engineering team has confirmed that it's not currently possible to remove words that have been added to your local dictionary. They have also confirmed that it's not yet on the road map but the team may address it in a quality week. Help article content: "Once a word has been added to your dictionary, it cannot be removed." is why I'm reaching out for help to get it removed.

The stickers/plugins etc sit in an awful pop up model frame that covers half your FigJam board (if on a laptop for example) so poor UI design for us users. We really need to have the ability to move/hide/reside these and ideally pin them for quick reuse.I initially raised this as a bug with Figma as the Pin Libraries to board (dock) use to be a feature and disappeared from FigJam in the UI3 update - it was still highlighted in their guidance here https://help.figma.com/hc/en-us/articles/1500004290841-Use-stickers-and-libraries-in-FigJam#Pin_libraries_to_board Though my suggestion was locked and cannot be updated and the guidance on that page has been changed.This is a case of UI design going backwards for usability and accessibility so I hope they provide an update soon.I know there was a lot of backlash on the inability to dock/pin in Figma and I imagine users feel the same for FigJam too.Can we please have the ability to resize and/or pin the sticker/library modals in Figjam for easy

Is it possible to view a user’s drafts as an Enterprise admin or a Team admin?As an admin I really should be able to view all files that have been created, but it seems that user’s drafts are still private even after the update.

In prototypes, comments do not scroll whenever you scroll the page.This can be fixed by getting the mouse-wheel scroll and moving the comments for each step either up/down (/left/right on horizontal scroller).This would at least give the illusion of “sticky” comments which many people need. The most robust approach would be to save the location of a comment in scroll-able boxes by index/coordinates. This feature is a MUST to be able to communicate with clients efficiently on larger projects. Best regards,LM from rechenwerk,Essen, Deutschland

Been playing around with the “expose nested properties” feature currently in beta. One of the great uses of variant properties is the ability to batch edit property values on multiple selected components. That use doesn’t carry over to exposed nested properties (yet I hope). Demo file to help When selecting one component instance exposing nested properties, said properties display fine. Add another instance of the same component to your selection (using Shift+Click), and the nested properties outright disappear from the right panel. I haven’t seen this issue raised elsewhere! Do you experience it too?

To help organize nested instance properties in the properties panel, it would be great to have them collapse inside their parent component in the list. E.g I have made a component with several cards. The card component allows me to turn on and off the title, text, image, and button. I can also change any of the text from the properties panel. → When I use an instance of the component in my designs, I must scroll through all the open nested properties before I can edit card number 7. If I were to see an accordion with cards 1-7 with their nested instances hidden beneath, it would be less confusing and much quicker.

One of the key pieces of functionality of Slides competitors (like Canva or Google Slides) is the ability to share a slide deck with anyone, even those outside of the Figma account. Here’s my use-case: Made a slide deck in Figma Slides Want to share it with my whole company and with external stakeholders (e.g. our Board) These people don’t have Figma accounts I can do this very easily in Canva or Google Slides But it seems I have to manually invite everyone into the file in Figma slides

I encountered an issue as I was building a prototype.When going into the prototype mode, we have the option to change the scaling to be “responsive”, which allows anyone who access the prototype to view it at full screen size, regardless of their device dimensions, which is great.  However, fixed position elements, such as a bottom sticky drawer, do not go responsive. They do not stretch left and right together with other scrolling elements. When looking at the alignment options, it looks like “left and right” and “scale” are disabled. That’s why it doesn’t go responsive. If we could enable the  “left and right” option for fixed position elements, so that my bottom drawer can be responsive and stretch to full screen width, that would be great..

Enable Figma Links (page/selection/node) in prompts for Figma Make.Figma Make should be able to connect to our design files and reference the design instead of relying on an image. Using Figma URL into Make and it can read the structure and styling directly Figma Make should be able to detect Code Connect (like MCP) and use React components

It would be great if, when I insert a component from a Figma library in Figma Make, I could use Figma Code Connect to retrieve the actual design system code linked to that component.

I design complex systems, often with a plethora of various states of a screen where content changes from zero to hero. Let’s say, I have a screen that is 1440 x 900 – it contains all the menus and some tabular content. Now, within this screen, I need to display the details of the table row in a sidepanel displayed above she table. And I have two states: The first state is the zero state, with a 50px high header, 100px of content, and a 50px action bar pinned to the bottom. The second one contains the same 50px high header, 1000px of content, and a 50px action bar pinned to the bottom. Now, for the first one, I need to set it to FILL the parent frame vertically, while for the second – I must make it HUG the content. I can also set the sidepanel manually to 900px of height (or: min-height), and make the content FILL it, so that the bottom bar is always pushed to the bottom – that is for the first state, while the other one needs to HUG anyway. With the header, the action bar, and t

Hi Figma Team,I’d love to see support for boolean properties applied directly to variants in components.Currently, boolean properties can only be applied to objects inside a variant (for example, to toggle icons or text). But there’s no way to control the variant itself with a property.Practical example: I have a Button component with multiple variants (Primary, Secondary, Disabled, etc.). I’d like to add a boolean property called “Has Fill” that would let me toggle the background color on or off across all variants. Today I need to duplicate or work around this by editing each variant separately, which makes the component library harder to maintain. Having boolean properties at the variant level would simplify libraries, improve consistency, and reduce redundant variants — especially for teams working with complex design systems.Thanks for considering this enhancement. It would be a real productivity boost for advanced Figma workflows!

THERE IS SPACE RIGHT NEXT TO THE INPUT. JUST PUT IT THERE. I HATE HAVING TO CONSTANTLY SCROLL DOWN ALL THE WAY WHEN SETTING UP MY TYPOGRAPHY VARIABLES. PLEASE.THANK YOU.

Hey @figma you know what would be dope? Having the image field as a component property allowing us to just replace the image without having to go into the layers…even better if it would save the fit or fill setting