Suggest a Feature

While I appreciate Figma keeping the frame presets updated with the latest hardware, the current organization makes it difficult for designers who prefer specific devices sizes/or is part of the deliverable (like me and the iPhone 13 Mini <3) for their workflow. Currently, I have to scroll to the 'Archive' section every time I want to create a new frame. This adds unnecessary friction to my process.Proposed Solution: Give users the ability to 'Pin' their most-used frames to the top of the sidebar, or allow us to toggle the visibility of specific device categories—similar to how the 'Inspect' mode in Chrome allows you to customize which devices appear in the list. This would allow us to prioritize the screen sizes that fit our specific design.Or other suggestion: just give us the control over it. :P 

Dear team, Please add a layers panel for Figma Team, just like how you would in Webflow. It is hard to imagine which layers we are selecting. This is so we can be more accurate in our prompts.Looking forward to granting this feature.Regards,Aileen

LibreChat is a free, open-source, and self-hostable AI chat platform that offers a unified interface for interacting with multiple LLMs and connecting to various MCPs.  Our team uses LibreChat extensively and we have already onboarded 40+ MCPs to it. Onboarding Figma MCP would be a great unlock for the org. Requesting you to allow LibreChat to connect with the remote Figma server.  Thanks!

currently working at an agency and they won’t switch to Figma due to the issue of Internal vs. external comments and how this is solved in Invision with Private Comments. I feel like if we just had private or even levels of permission (admin) comments vs. guest comments Does anyone else experience this? Is anyone using a plugin or workaround to help solve this?

This is a feature that would really improve the cross-pollination between the two systems! Right now it only functions for videos or static photos. At the very least, a simple download button would suffice- allowing you to manually download another user’s GIF upload and drop yourself into the slides document. Currently you’d have to request the file be sent separately. thanks!

Problem:Currently, FigJam is an excellent tool for collaborative brainstorming and ideation. However, when transitioning from high-level conceptualization to more structured representations like flowcharts, sequence diagrams, or entity-relationship diagrams, users are often forced to switch to other tools or manually draw these complex diagrams, which is time-consuming, prone to errors, and difficult to maintain. This breaks the seamless flow from idea to implementation, creating a gap between the initial brainstorming phase and the detailed technical documentation or code implementation. The lack of text-based diagramming also limits the ability to easily version control diagrams or generate them programmatically.Solution:Integrate native support for Mermaid.js within FigJam. This would allow users to create various diagrams (flowcharts, sequence, class, state, ER, Gantt, etc.) directly using Mermaid's simple, Markdown-inspired syntax within a dedicated block or widget in FigJam.Key f

In other design tools you can simply press a key, and any selection outlines, grab handles, etc. get hidden while the key is down, so you can preview and evaluate how things look, without having to de-select everything and lose your selection. Apparently there is no way to do this in Figma =( This is important while experimenting with different colors, fonts, etc., and in Figma it could be used to see how different sizes, variants, and states, look in your design, without those selection handles and outlines getting in the way of you previewing things.

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!

Right now, working with branches is quite limiting in the sense that: If I have a Figma project, with 2 frames (Frame “A” and “B”) contained within the same section I open my branch and select “Update from main…” Frame “A” has some changes I want to APPLY to the branch, BUT Frame “B” has some changes I want to KEEP in the branch PROBLEM: because both frames are contained within the same section, when updating from main file, I can only resolve the conflicts by updating all the frames, and therefore losing either the uptades in the branch or in from the main file. What I need: More granularity in what updates from the main file I need to ADD from the main file and which ones to keep in the current branch I’m working. Conflict resolution today is ALL or NOTHING and this doesn’t work. Sections are great for keeping my files organized, but they’re making it IMPOSSIBLE to work with Figma branches. Please fix this. Thank you!

Setting durations, easing curves, delays, especially for Smart Animate animations are essential tools when making presentations in Figma in order to make fluid ‘Keynote-like’ transitions. Unfortunately these are completely absent in Figma Slides at the moment, making it pretty much useless to our team. We will keep making our presentations in Figma Design and linking everything by hand🥲 until these crucial settings are implemented in Figma Slides…

Something thats always been tedious is the Figma export function. It would be helpful for there to be a button that takes you to the folder you’ve exported your assets. This is most often a problem when exporting assets into multiple tiers of folders, and having to navigate between the folder and the Figma file.

For the moment the “ready to dev” in the top left corner show all status of a “ready to dev” task (ready + completed)The number shown become unclear the real number of ready to dev task to do. I may have 1-2 tasks but the number show 24. I don’t think knowing the total number of task relevant. It’s would probably better to allowed to filter that number to user specific need. Tx.

Hello Figma Team, I hope you’re doing well. I’m writing to request that you please do not stop or heavily limit the Figma AI credits after March. The current credit limitation (around 3000–3500 credits per month) is very restrictive for teams like ours that rely heavily on Figma AI for daily design work. If continuing unlimited usage is not possible by default, we would really appreciate an option to purchase a monthly AI credit plan even for just one month at a time. We are fully willing to pay for an upgraded or add-on plan that provides unlimited or significantly higher AI usage, rather than being capped at a fixed credit limit. Figma AI has become an essential part of our workflow, and strict credit limitations significantly impact productivity. Offering a paid, flexible credit or unlimited plan would be extremely helpful for professional teams. Thank you for considering this request. We truly value Figma and hope for a solution that supports high-usage teams. Best regards,Rahul Ka

Hey everyone,I work extensively with Figma prototypes, and one functionality I feel is really missing is onScroll.the ability to trigger interactions based on scroll events (similar to scroll animations or parallax effects available in other tools).Does anyone know if Figma plans to add this feature in the near future?If not, are there any smart workarounds to achieve scroll-based animations within Figma itself without relying on external tools?Would love to hear your thoughts!Thanks!

Ver aquelas várias pessoas no arquivo enquanto eu trabalho me deixa ansiosa. / I feel anxious when I see many people in the file while I am working.

Anyone knows if Figma mentioned something about adding analytics to their slides in presentation mode? Same as pitch.com where you can measure the data from people that open the deck? If not, it might be a nice idea on the roadmap for Figma Slides? What are your thoughts on this?

Hi,I am currently using your platform for a university project and have unfortunately run out of educational credits. As a result, I can no longer access or demonstrate the prototype I have already built.I wanted to ask whether it would be possible to receive a small, one-time credit extension so I can complete the project and final evaluation. The prototype is already finished, and the additional credits would only be used for limited testing and demonstration purposes.Thank you very much for considering my request.Kind regards,Akira

When I want to access annotations via API on edit mode, I just need to check the node.annotations object.It would be great to also have a node.measurements object to work with.When annotations came to edit mode in beta at my org, I created a plugin for deleting all annotations after a colleague complained they needed to delete them for stakeholders.I’ve got someone asking to make it work with measurements as well, but that’s not really possible without a new API endpoint for it accessible via edit mode.

Currently, Figma does not provide a way to set a global or file-level default font for newly created text layers. When creating a new text object, the font is determined by the most recently used text style or Figma’s default font, which often leads to inconsistent typography and unnecessary repetitive adjustments.This limitation creates several issues: Designers must repeatedly change the font, weight, and size for every new text layer, increasing friction in daily workflows. Brand and design system consistency is harder to maintain, especially in team collaboration and onboarding scenarios. The problem is more pronounced for non-Latin workflows (e.g., Chinese, Japanese, Korean), where default fonts like Inter or Roboto are rarely used. Suggested ImprovementIntroduce a “Default Text Settings” feature at the file or workspace level, allowing designers to define: Default font family Default font weight Default font size Line height and letter spacing (optional) These settings

Maybe if we could alter the speed at which the elements of the screen move, we could generate interesting effects such as parallax scrolling. Imagine you have a frame and an image object inside that is going to scroll at 0.75x of the regular speed. This will create a parallax effect.

It would be great to have the option to set the asset filename using a data field out of the Spreadsheet file being used to do bulk create.By selecting the asset filename and assinging it to the respective datafield, the assets created would have the names described in the spreadsheet as filenames. Inside exel, google sheets or other program we can easily create a formula that generates the desired filename to each asset. Right now filenames are auto-generated or fixed, which means extra manual renaming after export. Being able to map a column like filename, slug, or ID to the asset name would make batch exports much smoother.This would be especially useful for high-volume workflows (social assets, product images, variants, etc.) and would save a lot of time while reducing errors.

Idea: Once a Figma Make file is connected to GitHub, automatically generate and maintain a changelog.md in the docs. I created one manually and it’s neat. It feels like it should be native. Part of a broader versioning and release history system tied to GitHub pushes maybe? 🤷‍♂️

Hi Figma team,After updating the desktop app today, I noticed that the Auto Layout panel no longer appears when selecting an Auto Layout frame. Additionally, the Layer panel now uses icons, making it difficult to distinguish between Frames and Auto Layout containers.Interestingly, the web version works correctly, showing the Auto Layout settings as expected.This change has significantly affected my workflow, and I hope you can either restore the panel visibility or provide a clearer way to access Auto Layout settings in the desktop app.Thank you for your attention!

1. Describe the problem your experiencing and how your idea helps solve this I can open 1 plugin at time, the plugins are located only in plugin section. I don’t have any possibility to add plugin to UI (exp. sidebar). Also plugin windows can be opened only in Figma webview window. 2. Add as much context as possible (screenshots, Figma files, mockups, etc.) example of sidebar for plugins 3. Ask questions to bring the community into the conversation Does anyone else have same problems?

As a design system builder and engineer, I’ve noticed that Figma’s component documentation—specifically, the component “Description” field—is currently buried in the component configuration panel. This limits its visibility during handoff, onboarding, and day-to-day use.Opportunity for improvement:Just as engineering disciplines rely on disciplined nomenclature and readily available documentation for clarity and scalability, design systems need robust, frictionless access to component descriptions. Bringing these principles to Figma’s UX would benefit teams of all sizes—especially those treating design as an engineering problem.Suggestion:Give the Description field its own space in the right toolbar, separate from deep configuration. Allow toggling visibility (e.g., an “info” or “eye” icon). By surfacing this information naturally—similar to a tooltip—users can reference component context without extra clicks, boosting clarity and alignment.Benefits:Faster onboarding for new teammates