Share Your Thoughts

Today I learned the move in transition is not supported when trying to create change to actions between variants of a component. This is frustrating as it limits my ability to use component interactions to reduce complexity of large prototype flows. Please fix.   

Right now, Figma’s Slice tool can only export an image of a selected area. Cool, but… what if it could do more?Sometimes I only need to show part of a layout — maybe to explain something to devs or teammates, or just to isolate a section without duplicating the whole frame. But the only way now is to turn the frame into a component, copy it, and resize manually. With Auto Layout, that gets annoying fast.So why not let Slice project the selected area right on the canvas — like a live cropped view of the original content? It’d be great for documentation, visual notes, or floating explanations without messing with the actual layout.Basically: make Slice not just for export, but also for viewing.

Would be useful (and a better UX) if keyboard shortcuts existed for adding rows and columns to a FigJam table. Tabbing (a common method to create a new row in other apps) causes focus to jump to a different item on the page (e.g., another sticky, text box), which is jarring and disorienting when trying to capture information in a group setting; lose your spot, lose your train of thought, focus goes to getting back to the table instead of listening to the speaker. One alternative or starting point could be providing those as menu commands, which opens up the ability for Mac users to define their own keyboard shortcuts using MacOS > keyboard > app shortcuts.

When setting up variable groups for modes, you may need all the same structure (all be it with renamed variable names) I find my self copying a group of number variables then using the same structurce want to apply strings to them (example h1, h1, h3), what would realy help is the ability to convert a group of variables from number to string and back again if need be.

Hi, please make Figma remember my choice when I pick “show as list”. Better still, put it in the Settings. Thanks.  

Some context: I work as an interaction designer in an enterprise org, but I am the only UXer in my business unit (and my country, as it happens). I work with the company’s core UX team, but I'm not part of that team - I’m part of a specific product’s dev team.Our core UX team maintain a component library, which I can (and do) use… but can’t edit - which is fair.  Unfortunately, the product I work on is an outlier and has a lot of unique needs.  I also maintain my own component library for things which are completely unique to this product… that all works well.What doesn’t work so well is when I need a custom variant of a component from the core team’s library.  I don’t need (or want) a whole new component, or the maintenance overhead of maintaining a local branch of their entire component library (if I even can without having write-access to it) - I just need to be able to add (for example) a single new variant to a library component which I can use locally without having to detach thi

Would love if there was a animate like the line draw animation in Keynote. It’s the one thing that’s still missing that I used to use in Keynote.

ProblemWhen building larger prototypes in Figma Make, it’s easy for structure to drift — especially across pages or collaborators. For example, the navigation or layout might get accidentally edited or slightly misaligned, breaking visual consistency. RequestAdd the ability to lock sections or turn them into reusable components. This would make it possible to:  Lock a navigation bar or footer so it can’t be moved or edited accidentally. Define a reusable page layout (e.g., header + sidebar + content area) that stays consistent across all pages. Quickly update all instances when a layout or component changes.   Why it mattersThis would save time, reduce errors, and make multi-page prototypes in Figma Make feel more structured and scalable—especially for teams using it as a design-to-code tool. ExampleLock or “componentize” a navigation section so every page automatically inherits it and stays aligned with the global design system.

The background removal feature in Figma still feels a bit rough, so I usually switch to another editing tool for that part.We use Figma for almost all of our website projects at AI Studios, and it’s been great overall — it would just be nice to see some improvement in that area.  

Feature Request: Per-user layout guidesCurrently, all guides in a Figma file are shared across collaborators. When multiple people work in the same file, guides overlap and create clutter.Request: Allow each user to have private guides that only they can see, with the option to toggle visibility of others’ guides.This would make collaborative design cleaner, reduce visual noise, and let each designer work efficiently without interfering with others’ layouts.

Currently Figma make allows you to have different pages for your prototype. But for some reason when the app updates i dont really have a way to go to the specific page that was changed. For eg. one of my prototypes has a component to provide email before you can move forward. So any time the app updates when i’ve changed any of the pages Later in the flow, I have to go through the entire flow again just to get to that page, and then ask it to make changes, and then we go over it again and again and again. I have seen it in other tools like Builder.io, where it doesn't matter what I change, I can go to a specific page from the page selector at the top. Is Figma going to get one of these? 

I’m embedding a form and would like to have scrolling on this embed and/or ability for the figma embed to resize on any change to avoid scrolling.

I am extremely excited to motivate for Figma slides for decks, and the ability to use components and even prototypes in here.My one concern is that if a component is used in a Figma sildes, and the component is updated externally, it is not updated in Slides and needs to be re-placed. Are there any plans to make this relationship persistent? Prototypes DO update when placed in Slides.

Hello Figma Community and Team,I'm incredibly excited about the potential of Figma Make and have been eagerly experimenting with its AI capabilities. However, I've run into a significant roadblock when it comes to integrating my team's comprehensive design library, and I'm hoping to get some clarity on the current limitations and what we might expect in the future.Our Setup: A Highly-Structured Design SystemTo provide some context, we've invested a substantial amount of time and effort into building a robust and meticulously organized design system within Figma. This isn't just a collection of components; it's a fully-fledged system that includes: Hundreds of Components: Our library is extensive, containing a wide array of components, from basic elements like buttons and inputs to more complex organisms like cards, sliders, and navigation controls. Meticulous Naming Conventions: Every component, variant, and layer is named with a clear and consistent hierarchy (e.g., input/text/defau

Could you please add the option to show width overlay in figma make, it would really help debug breakpoints when prototyping. Thanks

Just like Microsoft Powerpoint, we should be able to add duration for the transitions between our slides to make it not look like we are in a hurry. Currently, I think the default duration is 500ms and it’s too fast for me. I want to make it gently transition from one slide to another. The animations are great, but if you could also add more transitions, it would make it even more better.

For now the only solution I found is to switch the Image fill to Crop and to drag the edge of the image manually until it flips. This is cumbersome and not very precise because of the overlap of the image’s edges and the crop bounding box edges. A simple set of mirror buttons would be super helpful! Thx!

Just wanted to add a bit more context! Many agencies and independent designers build full visual systems in Figma, then rebuild everything manually in Divi for WordPress. A plugin or native export option could save hours of repetitive work and help preserve design-system consistency.I’d love to test or even provide feedback if your team ever explores a Figma-to-Divi workflow. It could really empower smaller studios that rely on WordPress as their delivery platform.

I would like to be able to apply variables to sweeps, etc. If this were possible, I think it would be possible to expand the dynamic expression of prototype.

A simple option to randomize a pool of sticky notes, without using a plugin. Seems to very useful for researchers. 

Please go back to basicsYou are moving forward too fast, we don't need more drawing and AI feathers, we need basic CSS options that are the basics of CSS web development since the 2000.On top of the list image-background position, object-fit etcAre you going to do something about it?😡

Hi Figma, I wish it were possible to duplicate text style folders, instead of just the text style itself.

The black floating toolbar is really annoying as it covers up what I’m trying to type. Is there a way to pin it? I know that I can run a script to completely remove it each time. However, it’d be nice to have an option to pin it at the bottom.

Hi Figma team!I’d love to suggest a small but meaningful UX improvement. In Figma, many numeric fields can be reset by typing “auto” (such as width, height, or layout), which is great. However, when working quickly, it’s incredibly easy to mistype “auto” as something like: atuo auot uato aout atou utoa or other nearby typos At the moment, Figma doesn’t recognize these variations and simply rejects the input, forcing users to delete and retype again. Considering how common and predictable these typos are, it would be a great UX win if Figma could accept common mistypes of “auto” as valid and interpret them as auto.This would improve workflow speed and reduce tiny daily frustrations without causing any conflict, as these typo variations aren’t used as valid values for anything else.A tiny change, but a quick win to improve designers’ lives ✨Thank you for considering it!

I’ve been using Figma for almost 7 years, and this has been a pain point for me while using Figma to craft UI designs in each of the projects I’ve been through. It doesn’t allow me to reorder the starting point flows I’ve created when more starting point flows are added. As more are added, there arises a need to reorder the way people navigate from sub-flow to sub-flow within an app design in the desired order. Additionally, having the ability to rename a specific flow directly from the present mode would be a plus, so the user wouldn’t have to leave the current context of present mode and go back to the shared workspace to find and rename that flow.I am pretty sure that there are a lot of folks in here in this feedback community must have the same concern as mine. So Figma, I am asking you to make an according adjustment to this and ease our lives. Thank you