Suggest a Feature

This seems like a very large design oversight in Figma Slides. The help article says that “Published changes only apply to new slide decks that are made with the template.” Doesn’t this defeat the entire purpose of having a custom template where you can edit a style and have it apply to your entire presentation, instead of needing to manually tweak a header style on every slide? I expected this to work the same way instances update in Figma Design when you make a change to the main component, but even after publishing changes to a custom template in Figma Slides, my existing slide deck that pulls from that template isn’t updating colors & text styles. The published template changes would only apply to brand new slide decks, which means I’d have to define the template first and then create my slide deck. That completely goes against the general approach to how many of us create slide decks. For example, I don’t make the template before I start the slide deck. I make my slide deck fi

I'd love to be able to transform ONLY selected nodes. For example: rotation, resizing, etc. This can be quite hand sometimes when drawing and using shapes 

I’m working with Figma Sites and its built-in CMS, and I’d like to suggest a feature that would significantly improve the developer experience when using code layers / React components.Feature requestProvide an official React hook (or similar API) to access CMS data from code, for example:const teams = useCollection('teams');orconst { data, loading, error } = useCollection('teams');Why this would be valuable Many developers want to build custom React components (carousels, filters, tabs, animations) that rely on CMS data. Today, CMS data is accessible only through visual bindings, not programmatically. A hook like useCollection would: Bridge the gap between design-driven CMS and code-driven components Reduce the need for manual exports or external APIs Make Figma Sites more attractive for hybrid designer/developer workflows Since Figma Sites already supports React code layers, an official CMS hook would feel like a natural next step.

When a comment is marked resolved, it just shows the filled checkmark icon. It doesn’t say who resolved it and when it was marked as resolved.Contrast this to Google Docs, etc., which shows this information.I already saw:View who resolved a comment and when • 2 years ago • 4 replies See who has resolved or reopened comments • 10 months ago • 0 repliesProblem still stands.We should also be able to see who reopened a previously resolved comment, and when.

Hello, I would like to know if it’s possible to select several words in a text layer, for example to put them all in bold or a different color from the rest, but all at once. Like in Word or Google Doc, I believe the shortcut is ctrl + select the desired words or part of words. It would be useful if it also worked across multiple text layers. I tried all the shortcuts I could think of but nothing seems to work… Selecting words one by one and apply the wanted properties every time feels soooo tedious. Maybe its not a popular request but that would be so useful. Thanks !

Hi there! For design systems, because components can contain other components, it might be a good idea to allow designers to set an “inherit from child” or passthrough option that allows the size to be set by the child component. Right now I think everything is enforced by the parent level, and it can break things (reminds me of my childhood lol .. just kidding - kind of?). Bottom-up works better than top-down in any case :) (see New Scientist, “Why complex systems do better without us”). --And a lot of life is learning to let go lolI have a feeling this may have been reported as a bug in the past, and it may be a technical limitation of HTML itself. It may be worth considering for a future version of HTML/CSS if that’s the case. I notice the “hug” feature already inherits from child in its own way, but sometimes there are defined sizes (not autofit) that need to pass through to other elements. Allowing this setting to flow in either direction depending on the system design would be he

… not fake elements that look like links. The reason why is because someone posted a link to a Figma file inside a Figma comment, and when I tried to open it in a new tab (making sure I’m holding Cmd in macOS, same as Ctrl in Windows), it just opened in the same tab as the Figma file I’m currently viewing. It’s also impossible to right-click the link and get a link-related context menu. It’s not possible to easily copy the link too. Right now what we get is a regular browser context menu. Worst parts are: The draft comment I wrote was completely lost because of this navigation. There was no warning, and it wasn’t saved to be restored later. The back button doesn’t work. It doesn’t take me back to where I was. It just reloads the linked page, and then the back button is fully disabled. I had to go find the previous location myself manually. PS: On that note: Please also reduce the label of long links to be truncated with ellipsis in the middle (max 2 lines).

It would be great if dev could export without rounded corners applied and or have some export flexibilities

I use Figma for Mac, and often need to copy+paste the link designer shares on slack.

Hi Figma Team,First, I want to say that I am really enjoying the new AI capabilities in 2026. However, I’ve identified a workflow friction point regarding the export process that I believe could be significantly improved.Below is a proposal for a "Batch Copy" feature to enhance the design-to-canvas workflow:The Problem (Current Experience): Currently, when generating a multi-page web application using Figma’s AI tools, I am required to copy each generated page individually to move them onto my main canvas. This becomes a repetitive and time-consuming task when dealing with complex user flows (e.g., Home → Product → Cart → Checkout).The Solution (Suggested Enhancement): I propose adding a "Copy Entire Flow to Canvas" button. Function: This would allow users to transfer all generated screens/pages of a web application to the Figma canvas in a single action. Behavior: The export should maintain the flow structure, placing the frames side-by-side or in their logical hierarchy on the canv

When working in teams on Figma projects, especially on larger or long-term products, it becomes difficult to manage changes, ownership, and reviews in a structured way.Right now, multiple designers can work on the same file, but it’s not always clear who changed what, or how those changes should be reviewed before becoming part of the main design. This often forces design leads to manually compare versions or rely on informal processes outside of Figma.It would be very helpful to have a Git-like workflow built into Figma, tailored for design teams. For example: The ability to create branches from a main file and work on specific features or sections Clear visibility into who worked on which frames or components and when A pull request–style flow where a designer can submit their changes for review A review step where a lead or manager can comment, request changes, and approve Merging approved changes back into the main file once they’re ready This kind of workflow would make co

If I’m already logged into Figma on my computer, can I just display a QR Code and Deep link my Figma app to that account so I can quickly preview my design? I’m not expecting it to know what project I’m in but that would be AMAZING if it could but I would settle with just logging in for me.

I work on a batch of emails every month. The file is the entire month- different emails in Pages. I would love to save or export Pages into local files so I can save those in the appropriate project folders on my server. 

Why I need it.Our designers create full specifications for components in our design system libraries and use dev mode annotations for our front end dev’s. As a Figma library builder, I use those same specifications to create the actual components for our Figma libraries. I copy sections from the design spec file pages and paste them into a library page to use them to create the library components.The problem is the sections I copy into my component page are loaded with dev mode annotations that I have to delete (no, I don’t want to just turn the view off) and I have to do that one annotation at a time.Can you please add a Delete all annotations command? Obviously a warning would be appropriate, but it would save me some time.Thanks!Ben

The Dev Mode Annotation feature released today is fantastic. However, I find it inconvenient that only one annotation can be added to one element. For example, if I want to explain a change in functionality in the same area of Mobile and Desktop, I may want to add a single annotation to multiple areas.

HiThe bottom toolbar feels a bit like an annoying appendix, always "in the way".Couldn't there be an option to put it on top [example bellow]?  This space isn't used that much, unless you have a lot of files open, which isn't a best practice anyway.And in larger screens, it's a lot of space.And these tools are mainly accessed via keyboard shortcuts.Thanks

In Present mode (prototype mode), it is not possible to edit the flow description.This would be very useful to me, as it is often when I review my prototypes that I notice details I want to add or modify in the persistent flow description. And currently I have to go back to design mode to do that.The flow description helps my viewers understand the context and subtleties of the flow they are looking at, so it is important to provide a thoughtful description (possibly in the form of a user story). Note that I don’t want to use mere comments for that purpose, as comments are designed to annotate a specific part of a frame (not the entire flow), and also they aren’t persistently displayed so they can be missed easily. Anyone with similar need?(Such an Edit function could of course be provided to Editors only)

We’re building a plugin that runs part of the workflow in FigJam and the next step in Figma Design. Today, plugins are scoped to the current file/editor type, so moving users to the next step is awkward. What we want to doFrom a plugin running in FigJam, programmatically switch the user to a linked Figma Design file, ideally without asking the user to manually open another file and relaunch the plugin.What happens todayThere’s no reliable way for a plugin to open/switch to another file + editor type. openExternal() with a Figma URL is not a reliable fallback in the desktop app: it often just focuses the app and lands on Home/Recents rather than opening the intended file. The result is a broken UX: we must show instructions like “open a Design file and relaunch the plugin”, which is confusing and feels unprofessional. Why this mattersA large class of plugins need to orchestrate multi‑step workflows across FigJam and Design (discovery → design, mapping → wireframing, etc.). Without a sup

I love sections because they easily help organize content, but they become less powerful as compared to a traditional group without the power of auto-layouts. Adding new content to a section always involves slowly moving everything else around (usually down) and having to always resize it manually. Having the option of toggling on/off something like auto-layouts for sections would really boost productivity!

It would be so useful to have a zoom to: width of the frame/page. It’s one of the most used views for “scroll design”. And also, when zooming in to fine tune a detail, you want to zoom back to the previous one, alternating between them with the same shortcut - what about ALT-Z? instead of zoom out with click - less used.

Hi everyone! I’ve been using Figma for quite a while, even before Figma Slides came out, and I often used it for presentations. One feature I relied on was animations—especially hover effects, like changing an image on the right when hovering over text. However, I can’t seem to find that capability in Figma Slides. Does anyone know if there are plans to add hover effects or similar animation features to Figma Slides? Or maybe there are alternative solutions? I’d love to hear from the community or the Figma team. Thanks a lot!

Hi everyone! How we can make design systems more self-documenting and easier to audit, especially for larger teams working on accessibility and consistency. It would definitely automate our tasksMy Idea:A Visual Variable Heatmap overlay in Figma that shows the usage frequency and distribution of: Color tokens (e.g., how often a specific color is used across frames) Text styles (e.g., font size, weight, line height combinations) Spacing tokens (e.g., padding/margins used most often) The heatmap could be toggled on/off per page or per component library, using soft color overlays (like low-opacity via styles) so it doesn’t interfere with design perception.I have seen a few benefits of it:Quickly identify inconsistencies (e.g., when a token is “official” but rarely used)Highlight potential accessibility gaps (like overused color contrast pairs)Help decisions on refactoring or retiring outdated stylesShow team members what’s used most often, which helps onboardingWorkflow example: Enabl

Automatically add page numbers to the selected slide in Figma based on Slide position. Maybe we can select any text and give it the numbering option?

Right now, the “Update from main file” modal is the least helpful modal imaginable:No indication of what or where the conflict is. All I see is a zoomed-out view of my “Layout & Content” library page with nothing highlighted or listed out anywhere. And with this information, I have to choose whether to keep these changes or keep my branch. I manage a design system for a team of 10 designers, split up into 3 pods. This is a nightmare every time.Items with changes should be highlighted, and those changes should also be listed on the left-hand side.Edit: And would you look at that, I chose to keep the branch, arbitrarily, and the next screen actually shows me what the update involves! Why wouldn’t this be on the first screen? (I’ve edited out the content for NDA reasons) Now I actually have to go back to the previous screen and choose again if I’ve made a mistake. 

There’s an issue I keep encountering every time I have to work with vector icons - you cannot have a flat, fully linear no-fill icon which has dots in it. You have to have two separate layers - one linear with just a stroke and no fill, and one which contains all the dots as filled circles without a stroke. This makes it hard to control transitions and is overall annoying. Please consider adding the option to create single-node dots that would be controlled by the stroke variable only, like a line of length 0, so that we wouldn’t have to add circles to linear icons. P.S.: or just make sure that the fill colors are preserved across instance swaps regardless of the amount of layers and aren’t reset to the inserted element’s default color, destroying my transitions. That would work too. At the moment instance swaps only consistently work with single-layer linear icons.