Suggest a Feature

Negative delay is a cool idea in prototyping when you need to start next action BEFORE current is ending, so next starts in 100ms before current ends

One important feature is missing = Merging cells 😦 Is this feature included as an improvement in the near future?

When exporting variant names, the file name becomes a combination of all the variant properties. There is no way to control the variant export name, which is especially difficult for developer hand-off. In this example, I have a back icon variant group (Named “Back”) containing both an Apple and an Android variant of the back icon. If I then go to expo

Currently exported .PDFs out of Figma are not accessible, because the text is flattened as images. I would like to request an option for exported .PDFs to have editable text. This would be a game changer for our team to move off of Sketch! 😃 (Sketch allows for .PDFs to export with editable text, but Figma does not)

 Summary A way to merge two or more Figma Make files together — similar to how video editing tools let you combine, split, or cut clips on a timeline.The problem When working on complex SaaS prototypes and flows, I often end up with multiple Figma Make files that each contain useful generated content. Right now, there's no way to bring them together without re-prompting from scratch — which means repeating context, losing time, and risking inconsistent output.The idea A merge or "stitch" feature where you can:Select two Figma Make files and combine them into one Preview the contents of each file (like a video timeline view) before merging Choose the order, split points, or which sections to keep — without having to re-generate anythingWhy it matters For product designers working on multi-screen SaaS flows, being able to build up a prototype from modular

I know there’s an option to hide the components from a linked library by prefixing them with a “_” or a “.” but I also have components within my file that I don’t want to see on the search results. Is there a way to achieve this?

Hi! First of all-- congratulations on the release of CMS! I’m already super excited to create stuff with it and I’ve been playing around with it this morning. Hereby my humble feature requests for the future of CMS!Categories and tags with separate pages for their content. Search and date picker (for events) functionality. I would love to see component swapping supported inside CMS, so that I can pick a different component per CMS article if I want to highlight it on my list with a special component for example. (A feature like this would be ~ incredibly ~ powerful.) Or/and, the ability to change page variables in a CMS item, so you can for example change the colors of the page based on the variables set in the item. The ability to connect CMS fields to the SEO, so you can attach a meta description and social sharing image to each CMS article. The ability to hide CMS items from lists but still have them in your database and vi

Organization would be immensely helpful if we could create folders for our drafts. I want to be able to organize my drafts into different categories (such as UI kits, Ideas, Wireframe kits, iOS, Android, etc…) so I can find files easily. Right now, the drafts page is a huge jumbled mess and I can’t create Team pages for everything. Maybe something as simple as being able to add ‘tags’ to each file, similar to Zeplin.

In figjam especially people commonly sketch out diagrams with lots of freeform lines used as arrows to point to things, sometimes as they talk about them (both when brainstorming and when annotating). It would be a really nifty feature for advanced users to be able to automatically have a line get converted into an arrow. Could also see this relevant in Figma too.I think everyone can maybe relate to the pain-point of having to either go into the setting to choose the arrow end-style for a line you just drew (a little finnickey and breaks flow if drawing to explain something on a screen-share) or else you manually draw the tip of the arrow each time for each line (doesn’t look good and if you want to move the arrow you have to select both the arrow tip you drew and the line itself)

Would be good if there was some way of exporting comments to a text file without the need of a Plug-in, helps build documentation

Hello,An admin-level dashboard for Figma AI analytics would be invaluable, giving us the visibility needed to:Measure Business Impact: Track adoption rates and usage to satisfy our internal reporting requirements. Drive Strategic Adoption: Identify which AI features are most popular and which teams are leading adoption. Support Our People: Celebrate team members who are regularly engaged with AI and identify users who may need more support to get started.

I have this use-case:All I want to do is ask the Figma AI to “Populate the same colour styling based on the syntax above, to the syntax below”.This is super easy for AI to understand.It should be in Figma already. There are so many example like this where because of the way the Figma interface works in relation to product UIs, some things take a disproportionally long time to do - e.g. “change all these pill components to this new one”.  

There have been many times where I’m trying to compare the color values between two or more objects. However, every time I select another object the color panel disappears so I have to click on the swatch again and try to remember the values from the previous object. Sometimes I’ll just take a screenshot of the color picker values and paste them back into Figma but that’s not fun at all. One possible solution would be to make the color picker remain visible if the user ‘unpins’ it (ie. drags it away from the right panel). Then they could select the next object to see the color values and then close the picker when they’re done.

Figma: If you’re used to working in another design tool, you may find it strange that your text styles in Figma don’t include traits like color or justification. Although it could take some getting used to, hopefully the benefits of this approach will quickly become clear. Well, no it didn’t. And strange indeed. In addition to getting used to, it takes a lot of time to to change the color every single time I create a new text element, because our text color is not black. Having a default color saved with text styles would be SO. MUCH. EASIER. I see no reason why the color can’t be in there and also be changed when using the style, if necessary.

Is there any plan to be able to create the gradient itself as a variable? For example, if I wanted some themes to have a solid background variable but others to have a gradient?

Switching to the Enterprise license and would like the ability to assign a user to multiple workspaces. I see there is an option for folks to be invited to teams in different workspaces, but it would be more efficient if we can easily add and see how many workspaces folks are assigned to. In our organization we do a lot of cross collaboration, across the workspaces.

It is possible to make the Who can view setting default to only show people in my org. Having it default to Anyone on the web makes it easy for people to make public concepts they shouldn’t

Of course it is easy enough to lock layers but I think that it would be helpful to be able to lock pages in a fashion similar to the layers. I often place root (master, main, og?) components on a separate page and it would be nice to be able to lock these pages to keep items from moving around without intention.

Can we submit a feature request for Figma to improve its PDF export settings?Currently, PDFs exported from Figma are very large in file size, and end users are unable to use editing tools. I need exported PDFs to remain searchable and editable for legal needs, which is not functioning well in the current format.Additionally, it would be helpful to export multiple pages without relying on a plug-in. Having to use a plug-in adds an extra step to the process.Adobe XD generated smaller, cleaner PDFs that preserved searchability and edit functionality. This is one feature I genuinely miss from XD.

As a freelancer, I often need to share files with developers, however, not all clients have a paid account and I don’t want to have to pay for a new seat for every developer who needs access to Dev mode or ask my clients to pay for Figma.

Chad Bergman announced in November 2025, during the Schema by Figma 2025, that the Figma tokens export is “completely aligned with the design tokens specification.” However, we later discovered that most composite tokens such as typography, gradients, and shadows are not yet supported, despite being in the stable revision of the specification in Design Tokens Format Module 2025.10.No clear future plans or roadmap for the export feature were communicated during the conference, which leads us to believe that we won’t receive any updates until the next keynote.Is support for composite token export planned in the near future, or do we have to stick to third-party plugins for now to obtain production-ready design token exp

Hi everyone, Are there plans to support native JSON import/editing for variables and text styles, similar to what Token Studio does?One concrete use case: generating a full typographic scale (with sizes, line heights, naming etc.) from a structured JSON and importing it directly into Figma. Right now, creating or updating a large scale manually can be time-consuming and error-prone. As more teams generate tokens programmatically (and increasingly with LLMs), being able to automate the insertion and update of variables and text styles natively would save a significant amount of repetitive setup work. Is this something being considered for the core product?thanks in advance </3

Currently in text styles, we can assign variables to nearly all values except for list spacing, is there a reason for this?

As written in the documentation (Prototype interactions and animations) the destination of a Scroll to action can only be an element of the same top-level frame. But with this limitation it is impossible to prototype a common navigation pattern. On one-pagers there are often floating menu for intrapage links. E.g you have an hamburger icon that opens a menu overlay from where you can scroll to a specific page section. This can’t be realized with an Figma overlay because of the restrictions mentioned above. There is a workaround, but it seems that it only works because of a bug: You can set the menu overlay as an child of the top-level frame of the one-pager, define the Scroll-to actions and then move the menu outside the frame (as an separate top-level layer) to show it later as an overlay. By doing this all the Scrol

Hello, I have a student (education) account on Figma, which should include all the Professional plan features. However, the option to enable Figma AI tools in the team settings does not work for me. Does anyone know if AI tools are available for education accounts, or how I can properly enable them?