Suggest a Feature

I think this annotation feature is great, but the documentation isn’t well written. It gives the impression that users with view-only access can see annotations, which is not the case. It would also be very useful to extend this feature to viewers such as PMs or clients, so I can easily show them how a button or function is supposed to work. 

Let us multi-select folders, to more easily re-organize after the new “Folder” implementation. Trying to sort all customers into “A” “B” “C” etc.. folders, and having to drag one-a-time is.. well.. not optimal. (this regards both click and drag + right-click and “move” option) While viewing “all folders” in list-view: Sorting gets refreshed everytime I move out and back in to “All folders”. From alphabetical to “Last modified”. Annoying. After moving x-amount of folders, it stops working. I need to go to “draft” and then back to “all folders” view and then “sort by alphabetical order” to start sorting them again. (bug?) First thoughts and experience with the new feature. Really glad to see folders introduced to Figma( finally! :) )

Hello there, I am currently having issues viewing the guides on my design when the brand colour is pretty much the same as the guides. Take a look at the screenshot. A suggestion for the guides colour:

Hi Figma team, It would be great to add the ability to ‘Reset playhead’ in the ‘State’ section of a prototype interaction. I’m currently working on a prototype for a carousel banner. I’m already using the ‘After delay’ and ‘On click’ interactions to make the carousel change slide automatically, and to allow the user to manually change slide. The transition of slides is animation, so it’s not possible to set the playhead to 0 on these triggers as it would be visible during the transition.  Each slide have a motion animation that should restart when landing on the slide, but since I’m already using the ‘After delay’ trigger, it’s not possible to add this at the beginning of each slide (eg after delay of 1 ms). 

I lack functionality. When I paste a link to a board, I expect to see a preview card, not just the link text. Alternatively, you could make the context menu either a preview card or just the link text when you insert it. I also want to post a link to external sources in conjunction with any FigJam element Thank you. All in all, everything is super!

When I’m zoomed way out, it would be nice if I could press “M” or some other key on my keyboard while hovering on something, and then a 2-3 inch diameter circle would appear next to my cursor, showing a magnification of what I’m hovering on. Then I could let go of the key on my keyboard and I’d instantly be back into clicking and dragging mode. This way, I can zoom way out and organize a bunch of things that need to be lined up next to each other in a grid or some other arrangement, without needing to constantly zoom in and out and find my place again every time. 

Figma supports enabling/disabling some OpenType features from the UI.https://help.figma.com/hc/en-us/articles/4913951097367-Use-OpenType-features From the plugin API I can see which features are being enabled withhttps://www.figma.com/plugin-docs/api/properties/TextNode-opentypefeatures/but the property is read-only. How can I programmatically enable/disable some OpenType features?Also, is there a reason why it’s accessible on UI but not Plugin API?

Would Figma consider supporting Variables for variable font axes in the future?We're using Google Sans Flex and switch between two visual modes:Formal - `Rond = 0`Friendly/Cute - `Rond = 100`Example of the ROND (Round) axis in Google Sans Flex. We use this setting to switch between formal and friendly typography styles.​​​​​Currently, font axis values such as Round (ROND) cannot be controlled by Variables. Because of this, we have to maintain two separate text-style systems even though everything else is identical.after add rondIf variable font axes could be bound to Variables, we could switch typography modes through Variables and maintain a single text-style system instead.Example concept: Variable Font axes such as Weight and ROND could be connected to Figma Variables, allowing typography modes to switch automatically.This would be especially useful for design systems that use variable fonts to express different brand personalities across themes or modes. 

The Problem:When designers work on a long-term project, using the Figma Agent creates too many separate chat windows. This causes a loss of context over time. Designers get confused about which chat to use. Also, teamwork is harder because different designers do not share the same chat memory for the same design flow.The Solution:Figma Agent should link its memory directly to specific canvas elements, like Frame IDs or Section IDs, instead of linking it only to a single chat window.Key Features:Cumulative Memory: No matter which chat window a designer opens, the AI adds all new information to the history of that specific design flow. Distilled Summary: The AI constantly updates a short summary of the work done, decisions made, and next steps for that flow. Team Sharing: Any designer who clicks on that frame or section can instantly read the AI summary and continue the chat with the exact same background context. Why It Helps:This stops chat confusion, keeps long-term projects organized

Fractional units and hugs are definitely a welcome addition to Grids, but what’s still missing is the ability to assign both the number of columns/rows and colspan/rowspan to variables.We’ve defined our website breakpoints as modes so we can build components that automatically adapt to the viewport (for example, a 50/50 layout that stacks on mobile). Right now, the only way to achieve this is by storing fixed column-width values for each breakpoint and use them in combination with horizontal auto-layout. It works, but it defeats the whole purpose of Figma’s grid system.Assigning variables directly to the grid would allow every component using that grid to automatically adapt based on its current mode (breakpoint). This would make creating mockups across different breakpoints significantly faster and more efficient.

Problem:When a Figma frame contains a video, GIF, or prototype animation, exporting it as PNG/JPG loses the motion. Currently, designers often need to use external tools or screen-record the prototype.Suggested feature:When a frame contains video, GIF, or animated interactions, add MP4 and GIF as export formats.Export options:PNG JPG SVG PDF MP4 🎬 GIF 🔄Suggested UXWhen clicking Export, Figma could automatically detect whether the frame contains animated content.Export as:○ PNG○ JPG○ SVG○ PDF○ MP4○ GIFFor MP4/GIF, provide:Duration: Entire prototype / Custom Resolution: 1× / 2× / 3× Frame rate: 24 / 30 / 60 FPS GIF: Loop / Play once MP4: Include audio / mute⭐ Extra opportunityA particularly useful option would be:“Export prototype flow as video”Instead of exporting just one frame, designers could select a prototype starting point and Figma would record the entire interaction flow as an MP4/GIF.That would be extremely useful for portfolio case studies, presentations, social media, desig

New UI for viewing library filesOur 5-person design team relies heavily on a color-coded visual system for project identification. Each project project uses a distinct color scheme on file cover pages (for example, green for Analytics files and blue for Finance files), enabling designers to instantly recognize and navigate to their active workspaces visually.The recent UI update collapsed project folder views into compact text-based blocks, removing the cover page preview that displayed the most recently modified file. While this compact view displays more folders on a single screen, forcing designers to rely exclusively on reading text labels adds cognitive friction and disrupts fast switching between active files.For me as a design lead and as someone also managing multiple concurrent projects, visual recognition is critical for maintaining focus and speed. Having to read through text links introduces unnecessary pause points when scanning the dashboard.I request that Figma introduce

When using variables, the container below the variable is too narrow,making the content difficult to read and preventing users from distinguishing between text that matches the beginning of a fuzzy search query.  

Allow users to mark fonts as Favorites so they can quickly find and reuse frequently used fonts without searching through the entire font library.How it could work:Add a ⭐/♡ icon next to each font in the font picker. Clicking it adds the font to Favorites. Add a “Favorites” section at the top of the font dropdown. Favorites sync across files and devices. Optionally allow users to reorder favorites based on usage.Even better UXAdd a “Recently Used” + “Favorites” structure:Font picker⭐ Favorites 🕘 Recently Used All FontsThis would be particularly useful for designers who repeatedly work with the same 5–10 fonts across projects. 

It would be a great idea to add the ability to move annotations (сhanging the place). Right now, they’re fixed in place and can overlap other elements. And you cannot change it.What I mean is the ability to reposition an annotation freely while keeping the link to the target object intact.Annotations are a really useful feature—thank you! Previously, I had to create similar functionality using my own objects. Please do not move this offer to another discussion. 🙏Can we move the Figma Annotations (in dev mode) from one Figma project to another?These are different questions.

Great to see the addition of dividers. Would really love the ability to add a name for each divider, because this still doesn’t solve the issue where we need to create an empty page titled “{Section Name}” to call out what the divider is actually dividing.

Hello Figma! I was wondering if you could add this small feature called “Text on path” making bending much easy. It could also be better if it can merge with the frame so that it can add bg colors to it

I’m working on a complex product that has a lot of business logic and design decisions documented in Confluence.I’ve hand-picked and linked relevant documentation to components in Dev Mode, using the “Dev Resources” field. This can be used as context by coding agents accessing through Figma MCP, which is great. But now I found out, that Figma Design AI can’t see and use it. I have to make it find the documentation by adding a search step to skills and prompts or looking it up myself and linking it there. This feels wrong and like a waste of either my time or AI tokens.It’s already great, that Figma AI is able to access our documentation. But it would be even better if the actively curated context of “Dev Resources” was accessible to it.  

Sometimes, the smallest UX improvement makes the biggest difference.Here’s a small UX problem I came across while working with icons in Figma.When you have a large icon library with multiple styles and color options, scrolling through the list can quickly become confusing.You scroll down…You see a lot of icon styles…And suddenly, you don’t remember which icon style you’re currently looking at.💡 What if the icon style heading stayed sticky while you scrolled through that section?The interaction could work like this:→ Icon Style A stays pinned while its icons are visible.→ Once Style A ends, Style B takes its place.→ Then Style C.→ And so on.Just like sticky section headers in many well-designed interfaces.It’s a tiny interaction, but it provides something very important: context.Good UX isn’t always about adding more features.Sometimes, it’s simply about helping users answer:“Where am I right now?”This is a great reminder that even a small interaction can make a workflow feel significa

Enable Figma Links (page/selection/node) in prompts for Figma Make.Figma Make should be able to connect to our design files and reference the design instead of relying on an image. Using Figma URL into Make and it can read the structure and styling directly Figma Make should be able to detect Code Connect (like MCP) and use React components

Figma Make: From AI Generator to Trusted AI Product Development OSI’ve been using Figma Make extensively and thinking about what the next evolution of AI-powered product development could look like.First, I want to acknowledge that Figma has already made significant progress with Make, AI models, skills, design-system context, editing, code workflows and agent capabilities.My feedback is therefore not simply “add more AI features.”I believe the next major challenge is trust, control, verification and orchestration.Today, the basic experience is often:Prompt → AI generates → Designer reviews → Prompt again → IterateI believe the next evolution could be:Understand → Plan → Confirm → Design → Build → Verify → Test → UAT → Approve → Release1. AI Planning & Understanding GateBefore Make starts building, let AI first analyze the request and create an understandable plan.For example:AI UnderstandingProduct goal:What I believe you are trying to achieve.Users:Who I believe will use it.Requi

Please enable this feature in text links. Currently, to copy a link, you need to click on “Edit” and then press cmd+c.I suggest adding the “Copy to clipboard” action to the interface of the drop‑down window. This will eliminate unnecessary steps.  

The UI can get over crowded with annoying frame/component names hanging off their top edges. I have not found a way to disable/hide these. Please tell me there is a way! 🙂

The blue interaction box is helpful for prompting which elements can be clicked in a prototype. All components with interactive states, even just hovers, now have blue interaction boxes - even when they don’t really do anything useful like navigating or launching a modal. I’d like some level of control over which variant interactions are visually prompted, or some smart defaults (which Figma is awesome at, thanks team!)

Hello Figma Team,I would like to suggest an affordable “Designer + AI” plan specifically for individual and freelance designers.Many individual designers mainly need Figma Design and AI features. We may not need multiple seats or extensive team collaboration features.It would be great to have a plan that includes: Full Figma Design editing Professional design features A reasonable monthly allocation of AI credits The option to purchase additional AI credits when needed No need to pay for unused team/collaboration features For example, a plan around $5–10/month could be very useful for freelance designers, independent creators, students, and small creative businesses.I currently use Figma mainly for design work, and I feel that paying $20/month for a Full seat can be expensive when my main requirement is Design + AI.A dedicated “Designer + AI” plan would make Figma much more accessible to individual designers and could encourage more designers to use Figma’s AI tools.Thank you f