Share Your Thoughts

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!

Displaying the frame in the interface was a terrible decision; it made the interface very cluttered.

WHEN - will Make be able to read the very design system tokens, primititves semantics and componenets that third party applications already can? I love the platform but this is such an own goal for anyone really clued up- when and why is this not allready implemented? Whats the point in figma make ifw e can’t control the design system and connect design system primitives,semantic and componenets with wrappers around shadcn components etc without doing it manually.For anyone with a modicum of development knowledge this is crazy ommission. It puts me off recommending figma. I might have to resourt to my own custom ontoligies and the daft thing is claude etc reads the darn tokens and renders to production so that kind of also knocks figma make out of the game own goal number 2. Someone please please tell me I am wrong. This seem a massive hole in capability which shoulld have been a main reason for building make to start with doh...

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?

Come on Figma, it's just about adding the options into the menu. I now can translate from Czech to English, but not from English to Czech, because the option is not there in the menu. Same goes for Hungarian, Romanian, Bulgarian, etc. 

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

Auto layout sometimes causes more problems than it solves.  When I get a set of wireframes from someone else, I find it causes a lot of wasted time trying to figure what objects are using it and shut it down for each one.There should be a setting to just turn Auto Layout off for the whole file. The way is works per object right now is a huge time waster in using this product.

im an interior designer and im creating a webpage for my portfolio , there are some features i ued in the figma site that arent available in the figma design  which is a bit inconvenient since the two complement each other pretty well , is there a way i can use both on one design ? if not , any suggestions ?also it would be amazing if the features were all accessible in one page :)  

We need support for Alt text for images added in Figma Slides. This is a major issue for us. We are using Figma Slides to create presentations and those presentations must be accessible to our co-workers who are blind or low-vision, and to set a good example for other teams.

I previously used Figma and Figma Slides as a great collaborative tool for my public university’s design courses. However, we are required by law to make our classroom content and slides accessible. Without features like alt text, reading order, etc. I cannot use Figma slides in my classrooms until an update is made.I suggest that accessibility be standard across all Figma software. Whether you are using design, slides, or any other current/future pieces of Figma regardless of what you are creating in. Furthermore, if Figma could export accessible PDFs, it would really aide in designer’s ability to make accessible design more simple to produce. This would not only promote accessibility in your software, but also make it useable in more spaces where accessibility is required.

Hi everyone! Why “accesibility settings” are not available for Figma Slides too? It would be very useful, also to download accessible pdf. Please add it soon. Thank you 🙂

Hi Figma. First of all, thank you so much for introducing nested instances feature! It’s a very good feature for a team that handle design systems. It gives our consumer a clear clarification what they can do with components without the need to dig deep into the layers of the component. There’s one thing I think it can help this feature to be a lil bit clearer on the right panel. It would be best if Figma can add a separator between each of the parent group and have an indentation for the children nested instances. With this, it’s much easier to identify the grouping, especially on complicated components with many nested instances. Please refer to the image attached.

Can anyone figure out how to reorder the list of variable collection in the fill dropdown? The layer ‘mode’ assignment appears to sort correctly alphabetically, but the pick list under the fill menu does not, which is a huge painpoint, and will definitely lead to my designers picking the first color they see instead of the semantic one. Correctly sorted - numerical Incorrectly sorted - 2. is at the top instead of 1.