Suggest a Feature

Hi Figma team,I'd love to see the following three improvements added to Figma Slides:1. Linked slides across presentationsAllow a slide to be "linked" from one presentation into another, so that editing the source slide allows updates it everywhere it's linked. This would be huge for teams that reuse boilerplate content (title slides, team bios, product overviews, legal disclaimers) across multiple decks; right now, updating that content means manually editing every deck it appears in.2. Copy selected slides to a new presentationAdd the ability to select a subset of slides and generate a brand-new presentation from just those slides. This would make it much easier to spin off a lightweight, audience-specific deck (e.g., pulling just the relevant slides to send to a vendor or client) without having to duplicate the entire deck and manually delete everything that doesn't apply.3. "Send slide to end of deck"Add a quick action (right-click or keyboard shortcut) to send a slide to the end o

Request: Add option to import multiple Jira issues at once in native Jira Widget. Story: We started to use FigJam for our team collaboration (±20 ppl). We have feature breakdown in Jira, we need to import Jira issues to board. It is possible to now either insert one by one or whole project. I need something between. Either import this list of issue Keys or import this JQL result. Jira projects usually contain hundreds of issues, so importing whole project is useless. Doing it one by one for 40± issues at a time is real pain.

For audits i am often adding hyperlinks to sections and thought it would be a great feature to be able to add a hyperlink to the heading instead. 

Hi, I wanted to suggest preset colour options for Sections in Figma, similar to FigJam. The default grey colour blends into the default canvas background meaning I always need to choose a custom stroke + fill after using it. It’s an easy task but it breaks my flow to have to stop and change the colour of a section in the middle of whatever I’m doing. To be honest you could improve this just by changing the default colour from grey, but having some of the FigJam presets makes it a lot easier if you have different colour sections for categorisation.

Let us be able to add audio to the slides to give it more life. Imagine that after creating a presentation with your prototype embedded into it and some animations. You can finish it up with some amazing audio!

I already have two set of position information. [984 | 2000] [ms]984 is where my red line is in the time line of animation, and 2000 is the total time available which is adjustable. I would also like to have the position if I select-drag a keyframe from somewhere within the timeline, sometimes it helps to know where I am.

Description:Currently, Figma Variables only support solid colors. However, many design systems use gradients as core brand tokens (e.g., multicolor accent fills, branded gradient backgrounds).Today, the only way to store a gradient as a reusable token is through Paint Styles, but they don't integrate with the Variables infrastructure — they can't participate in modes (light/dark themes), collections, or scoping.Request: Allow Variables of type Color to hold gradient values (linear, radial, angular, diamond), not just solid colors. This would enable:Gradient tokens that switch between themes/modes (e.g., a vibrant gradient in light mode vs. a muted one in dark mode) Full design-token parity with tools like Style Dictionary and Tokens Studio, which already support gradient tokens A single source of truth for all color tokens — solid and gradient — in one placeThank you for considering this!

it’s different from just using history. we are working on a file that was ongoing for years, some of the frames are old, some are new. we want to see what is the age of each screen to understand the timeline of our work. we could scroll back in time and see, but then we would had to jump between times, trying to discover and guess when a screen was created, rather then the possibility of just clicking on it and see the date of the creation

Community / User RoleDeveloper / Engineer using Dev ModeThe ProblemCurrently, when inspecting components in Dev Mode, developers frequently only need a single line of code (e.g., a specific border-radius, box-shadow, or font-size) from the generated Layout or Style text areas.To get this single line, developers must manually highlight the text—which often results in accidental multi-line selections—or copy the entire code block and manually delete the unwanted lines in their IDE. This adds friction, slows down implementation, and introduces minor manual errors.The Proposed SolutionIntroduce the ability to copy a single line of code by clicking its corresponding line number in the Dev Mode code inspect panel.Interaction: Clicking a line number copies only that specific line to the clipboard. Visual Cue: Hovering over a line number could display a subtle "Copy Line" tooltip or a small copy icon to make the feature discoverable. Success Feedback: A brief "Line copied!" toast notification

When I have library updates available for my file, sometimes I just want to apply them to a specific page – not to the whole document. The Updates panel lets you select Current page, and as a result you only see which components of the current page have some update available. All good so far. Now if you want to review changes of a component rather than blindly click Update, you select the component in the list and end up in the second-level, Review updates panel. The trouble is: At this point the Current page filter is forgotten and you can only review all the instances of the document. How can I review one by one the instances of the current page only? Motivation: I would like to always review and update stuff on the local components page of my file, because if I update this first, a lot of updates will propagate automatically to the rest of the file, saving me a lot of work.

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!  

Section names used to be bigger and more readable when zoomed out in older versions of Figma. Now they are too small to read when zoomed out, which makes it harder to navigate my file by scanning section titles. I'd like the old larger section title size back, or an option to control section title font size.

Hi,Currently, the FigJam formatting toolbar only defaults to bulleted (unordered) lists. Because I mostly use numbered (ordered) lists, converting existing text into a list takes multiple extra steps: Apply bullets to the selected text. Manually change each bullet point to a number. Having a dedicated numbered list option directly in the text toolbar—or a quicker shortcut—would save a lot of time.Are there any plans to introduce direct numbered list formatting in FigJam soon? I’d love to hear the team's thoughts why it wasn’t added explicitly now?Thanks Default option After explicit mention of a number 

Add the new Midjourney model to the Img gen tools

Right now under price I can choose All, Paid, and Free. Under “free” I often find items that aren’t actually free but are demos, with limited functionality or times they can be used before you have to pay money. From a marketing perspective I get it, the plugin technically has some free functionality, but if its limited by time or uses, the use of “Free” is misleading. So I think what would be ideal is a new facet, “demo” for all plugins/resources that aren’t fully free.The other request is a filter to offer the option to include or exclude plugins that use AI to perform their function.

When working with large files, I encounter such wasteful actions as expanding/collapsing each selected group of layers.I find it better to perform these actions in bulk. Here is my solution to this problem. Please vote if you are also troubled by this time-consuming process. 

.

Dear developers, please add the ability to define a variable's color based on several other variables.For example: let's say I've decided that the hover state is created using the rule "brand color + 50% opacity of the theme color" (white for the light theme and black for the dark theme). But then the client suddenly decides to change their brand color. It would be really convenient to be able to create rules like this, so that you don't have to change every color manually. It would save a lot of time.  

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 :  

When using a grid based system, it would be useful to bump (move) rulers by a set amount. For example if I am designing a UI and I am using a 8px system. It would be useful if I could click on a ruler, press a button (‘b’) and move that ruler by my 8px. You could have a setting called “Grid System px” where I could set the bump amount. That way when I lay out elements by using the rulers I can quickly move them around based on my grid system.

Hi Figma team,I’d love the ability to open multiple selected files at the same time.Currently, it’s possible to select multiple files and perform bulk actions such as Duplicate, Move, or Delete, but there is no option to Open all selected files.This would be especially useful when working on large projects or design systems where multiple files need to be reviewed, compared, or updated during the same work session.Suggested improvementsAdd an Open action to the bulk actions menu. Open each selected file in a separate tab or window. Support common shortcuts such as ⌘+Enter (macOS) or Ctrl+Enter (Windows) to open all selected files.EnvironmentmacOS Figma Desktop AppThis feature would be especially valuable for designers reviewing multiple files every day, making file management much more efficient.Thank you!

So lately I’ve been designing retro mockups and they use pixel fonts. On most design tools like GIMP, Pixel.net, and Photoshop, there is an option to use Aliasing (Disable Anti-Aliasing) for text, making it pixelated (no blurring caused by anti-aliasing) and unfortunately Figma does not have this, which makes me search for Bitmap fonts that only work on specific sizes to accomplish pixel fonts. So I wanted to ask for an option to have Aliased fonts without Anti-Aliasing, to force them be pixelated.

Hi everyone! Maybe I’m missing something, but is there a way to copy the currently selected padding token, similar to how interactions can be copied?I’d like to copy a token that is already applied to one component variant and then paste it onto another variant—or any other object with a compatible property—that currently has a regular numeric value or no token assigned.At the moment, I can’t find a way to copy the selected token while the token list is open. Is this already possible somehow?  

 Hello! Congrats on your big update. Btw while I really enjoyed trying the Figma agent to build my own Plugin tool, it was frustrating to know that I have no way to share it with the team. I guess that it's because it's beta version? If you don't have a plan to make it sharable in a foreseeable future, i would prefer building plugin externally for our team rather than these tools. Thanks for reading! 

As AI coding becomes part of the design-to-code workflow, I think there is a new type of information that belongs in Figma: Implementation annotations. Today, annotations can only be added by people with edit access to the design file.This works well for design explanations, but not for implementation guidance. Imagine this workflow:A designer finishes the UI.Later, a developer reviews the design before implementation and notices several places where additional implementation context would help an AI coding agent generate much better code. For example:This Frame should be implemented as a scrollable list. This component should use virtualization. This area should stay fixed while the content scrolls. This value comes from the current device model. This text should truncate after two lines. This image should preserve its aspect ratio. This section should use the shared DeviceCard component. This layout should become two columns on larger screens. None of these change the visual design.T