Suggest a Feature

Hello, I am reaching out to express the need for a feature that allows direct duplication of pages to another file within Figma. Currently, the process of duplicating content by copying and pasting between pages is not only time-consuming but also becomes cumbersome when attempting to duplicate multiple pages to another file simultaneously. I believe a feature that enables direct page duplication to another file would significantly enhance our workflow and efficiency. Such a feature would save considerable time and effort, especially in scenarios requiring the management of large projects with multiple pages that need duplication into different files for organizational or collaborative purposes. Is there any plan to develop a feature that facilitates duplicating pages directly to another file? This functionality would be highly appreciated and could notably improve productivity and usability within Figma. Thank you for considering this request. I look forward to any updates on potentia

Hello folks! First of all, thanks for all the great work you constantly do on Figma. It’s really an amazing tool and keeps getting better and better. ❤️ With that said, I would like to point some issues with the “Review updates” tool, mostly related to how Figma theme interface sometimes make things unusable. 😅 1. Enable user to toggle background color. The images above are from exactly the same component. As you can see when we have the dark interface theme enabled, it’s impossible to even see the component in order to review it’s changes. As you can image, the same is truth in case you have light colored components at the light Figma interface theme. The simple solution / patch here is probably add, near to “side by side / Overlay”, an option to toggle the preview background color. If you really want to go MVP, you can simply change the entire Figma theme with this toggle, kinda like a shortcut of “Preferences > Theme” menu. 2. Hidden elements that need upda

Add a Reassign button to the Library Update Dialog to allow specific bulk re-mapping of styles, Components, and Variables. 

Need for an dialog to confirm a variable collection deletion.

Hello everyone,I just removed all interactions from the prototype by mistake when working on a project. 💀I right clicked on the Prototype page because I was having trouble connecting a section. Clicked on “Remove all interactions” thinking it would hide them temporary so I coud have a better view. I almost cried when I realized all the conections were lost. Why did the system didn’t even ask for a confirmation?!When I realized what happenned it was too late, I tried everything but no Ctrl + Z or Version Story could solve it. I tried to re-connect it all but I had a meeting in 1 hour. Of course I wasn’t able to fix the whole project… I believe it should totally have a confirmation modal or something similar to a warning, it’s a delicate decision for the user to delete everything and from what I’ve seen it keeps happening to many designers.Please share your thoughts with meAlexa

Hey, I’m working with a team that’s switching from Miro to FigJam, and they primarily use Miro as a Moodboarding tool.I’m wondering if there’s a good way to select multiple images and match their size – we’ve found the “scale better” plugin in the plugin store which can do this, but don’t like having to cmd+K and type its name each time we want to do this.If there isn’t, I think this would be a really good feature to add.

I am using Figma Make extensively as a Product Manager to co-create interaction frameworks and prototypes with AI through multiple iterations.This workflow exposes a critical gap that blocks real-world delivery.Context: AI collaboration naturally creates many intermediate states However, not every generation should be treated as a deliverable version At certain points, I need to explicitly confirm:“This version is good enough to be frozen and delivered as V1.01 / V1.02.” Current pain points: Figma Make provides generation history, but no concept of a user-confirmed fixed or tagged version There is no way to attach structured notes or delivery comments to a specific confirmed version The only workaround is screenshots, which: Break interaction context Disconnect from the prototype itself Significantly reduce communication efficiency with developers My need is very specific: I do NOT want every history step to become a version I DO want: The ability to freeze a

Hello, It would be immensely useful if I could see a list of all components (with variant indication) and variables used per page / file, and be able to compare that to the entire list of components / variants / variables available in my design system. This way it would be easy to spot any unused component / variant / variable in the design system and purge it. Thanks

We need better image handling tools including: original scale percentage (+reset); the ability to copy images out of frames; non-proportional scaling under Crop. It needs to match InDesign’s at least.

Hi, I would love to have the option to draw with the Marker tool in the android tablet application. I know it is possible on iOS tablets, but it isn’t possible on Android.

Hi,I have a button component set with a text style of “body large”.With all differents sizes, styles and interactive states, I have currently around 100 variants for the button component.I want to add a new text style “display small” as an option for this button.If I want to add the text style as a component property, I currently need to add another 100 variant, right ? And another 100 variant if I want a 3rd text style option ?It would be great to have a possibility to do it better natively.

Hi all 👋 I’m working with a Description List component built using CSS-like grids in Figma (term + description per row).Each row is sized to its content, and the overall component height is also set to hug contents. However, when I hide a row (e.g. term + description), the container height does not automatically resize to the remaining visible content.Instead, I have to manually resize the container, and I end up seeing purple grid lines below the visible content. What I would expect (and what I’m used to with other components) is that the container immediately shrinks when content is removed or hidden. Questions: Is this a known limitation when using grids in Figma? Has anyone found a workaround for this? Or should this be considered a feature request so hidden grid rows no longer affect container height?  Curious if others have run into this as well 🙂 I’ve attached a short video showing the issue: Thanks!

There’s the ability to select ever-deeper child components by clicking enter to go down each level. I propose that when a user is in Prototype mode, this behavior should select all the prototype connections. This would allow you to make a large selection and change all the shared parameters of the prototype connections (for example, changing the ms duration of all smart animates)

I’m working on a large scale design systems audit, where I’m building a custom dashboard to supplement the Library Analytics feature. We want to link to specific views of the Library Analytics feature, such as a particular component’s insertions. This doesn’t appear to be possible now.Our tool does some specialized things that wouldn’t make sense as general Figma features, but Figma’s own analytics feature will always be the best option for universal tasks, so it would be great to point our users to it.

I have a Figma Slide deck that I have been modifying for a few months that is being refined as I move through the project.Because the slides link is live and reflects current changes, it is hard to make edits to these slides post-meeting as there could always be audience members who are looking to reflect on something specific that was shown. I could export as PDF but I would lose all prototyping.I wish there were audience versions or a way to hold and deploy changes! 

My iPhone takes screenshots at 1179 × 2556px, which is @3x. The native resolution @1x should be 393 x 852px.But, Figma imports my iPhone screenshots at 589.5 × 1278px, seemingly assuming that the images are Retina / @2x. Can I change this setting somewhere?

The hug update to auto layout grid is a great update, but still lacking some critical features for creating data tables. It would be extremely helpful if we had the ability to assign fill colors or strokes to an entire row instead needing to add to create a cell component with the fill or stroke added to that. The issue with that is if you had content in a cell that needs to wrap to multiple lines, you would need to adjust the height of all the cells in that row to fill so that the color or strokes line up. I would also be helpful if we could control an entire row or column with variables. I am creating a table component and we have an multi-level header row that is optional so we need the ability to toggle that row on and off via the props panel. Another small addition that would be useful is on right hand panel where you see the full list of all columns and rows, allow us to change the order of them in that section. Hoping you continue to iterate on this feature. Thanks

I work in an agency with a team wanting to create a Slides template for our studio decks. However, as far as I can see, only one designer can be the owner of the template and therefore edit it. Everyone in the rest of the team can only use it.This is a huge limitation as that single designer always has to be available to make updates, and if we want to add some new slides with layouts useful for our deck, then nobody else can make those additions. If that designer is on holiday or leaves, we’re stuffed!This could be a huge barrier for us moving agency decks into Slides, however much we love it, compared to InDesign or Keynote.Please Figma, make everyone in the team be able to edit Slides templates!Are others out there running into this same limitation?

I would love to be able to change the default fill / stroke color / and corner rounding of sections within Figma. I find myself spending a lot of time adjusting sections after initial creation to the way I like them throughout my files.

Figma 슬라이드를 사용 중인데, 내가 현재 작업하고 있는 슬라이드 페이지에는 현재 상태가 표시가 되어있지 않는 듯한 UI 입니다. 좀 더 또렷한 상태로 확인 가능하면 좋겠어요. 다크모드여서 그런것인가 싶기도 합니다.하지만 전체 화면 모드 색을 피그마때문에 바꿀 순 없으니 개선이 되면 좋겠어요.슬라이드 페이지를 작성하는 데 시간이 걸리기 때문에 시간이 오래 걸리게 됩니다. Google 슬라이드를 칭찬했을 때 지금 가장 좋은 점은 점이라고 생각합니다.

We need a feature that enables counting and reporting of annotation labels for team metrics.In our workflow, designers leave comments on Annotations and apply one of multiple possible labels. For metrics and reporting, we want to: Aggregate counts per label (e.g., Interaction: 12, Accesibility: 7, etc.) Understand the distribution of annotation labels over time/projects to improve our overview and tracking.

Hi Figma team,I wanted to share a small pain point I keep running into — and maybe a solution.As a UI/UX designer working on complex SaaS and mobile projects, I often end up with Figma files that have dozens of frames across multiple flows. Despite careful naming, it's easy to lose track of what’s ready for dev, what needs review, or which version belongs to which client.Lately, I’ve found myself wishing I could just tag frames — like #ready, #needs-feedback, or #v1.2 — directly on the canvas or in the left sidebar.Something lightweight, like sticky labels or even a built-in tagging system, would make navigating and collaborating inside Figma so much smoother.Right now, I rely on naming hacks or color-coded backgrounds, but it gets messy — especially when the file grows.I imagine a world where I could quickly filter or search for #mobile or #dashboard and instantly jump to relevant designs.Thank you for building such a powerful tool already. I just thought this small improvement could

Hi Figma Team, While working across multiple design systems and cleaning older project files, I’ve noticed a recurring friction point in the Color Styles panel: Figma does not support searching color styles by their hex values.This small limitation creates a surprisingly large productivity gap for designers and teams. The Core IssueCurrently, the Color Styles search recognizes only the style name, not its underlying hex code.But in real workflows, hex values are often the most direct, reliable reference point — especially when working across old files, new token systems, or unlinked fills.Evidences  Why This MattersHere are a few common scenarios where hex-based search would significantly improve workflow efficiency:1. Faster Updating & Mapping ColorsWhen aligning older files with a new design system, designers often copy a hex from the canvas and expect the matching style to appear in search — but it doesn’t.2. Easier Reviewing of Junior Designers’ FilesJuniors sometimes use direc

It seems very unusual to publish a code generation feature without any kind of mechanism for export to version control. While I’ve been testing figma make and enjoyed the result, i’m having to consider moving to alternatives like lovable because of the benefits of simpler integration with version control.Will we be able to link our figma make projects to a github repository in future?an alternative approach would be integration with the figma for VSCode extension. 

Hi everyone,I’ve been working with the Figma API and noticed that while FigJam mind maps can be created via the UI, there is currently no official API support for programmatically creating or manipulating mind maps in FigJam.I would love to see an API that:Allows creating a Mind map programmatically Allows adding/removing nodes and connecting them Supports retrieving an existing mind map structureAt the moment I can only manipulate text nodes and connectors, but not the Mind map UX behavior itself.Is there any plan to expose a Mind map API for FigJam? It would greatly help in plugin and workflow automation.Thanks!