Share Your Thoughts

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.

Without better tab/file management I will use Figma less. I have 40ish tabs open. Some are Figmas I just need to refer to often, some are Figma/FigJam projects I am working on, some are presentations I have been asked to look at, some are my presentations, and some are FigJams for meetings that happen frequently.  If you want Figma to be a central repository for all of this the file/tab handling will have to get better or I will work in other tools where I can find the information I need.Small fixes:Hovering over tabs needs to show the current view...not some Front page that I do not recognize.  Current tab needs to be easier to find. Vertical tab bar so I can read the names. Right now I can see 1-3 character of each tab’s name. Ctrl+/ needs to teach open and closed files. An open tabs view with preview of the last view I had. 

If I use a link that is a click, should be green, if it is a hover, could have another color blue, if it is while pressing, purple, and then so on, drag could be red or orange, for example. And they could show in the line a icon related to the trigger it is using.Swap overlay should show a different icon and line color too.Would make it easier to identify when we mistakenly created a drag instead of a click.

We have moved from Pitch to Figslides for our presentation tool. We are finding several issues with Figslides that pitch had nailed, but one of the biggest frustrations I’m hearing from the team is sharing presentations with clients. In Pitch, from one button you could create a link to share with any external party. If you wanted it password protected it would also create the password and copy both link and password as text to share via email.In figslides, you have to go in to presentation mode > share presentation > Copy audience link > Who can access (changed to anyone) > click on password required > click generate password and then paste the link in to a text box or email before going back in to copy the password and paste that to. What should be a simple 1 or 2 step process is 10! Please make this a more simple process and copy both link and password to the copy board at the same time.

We need to apply variables according to property in more styles, much like how we can assign conditional visibility to toggles on and off. If I’m creating a button component, I want to assign text sizes, padding and colors according to properties of size and type. Currently we’re making different instances for every size and type to link them to each property which results in multiplications for each new property.It will probably work using some conditional logic, when the property is this, assign that, and so on ..

As I am using Blender for VFX and 3D modeling, I find some interesting UX there. Like when panning the 3D world: if the cursor reaches the edge of the viewport, it is put on the other end so I can keep on panning. Is something like this a nice idea for the infinite canvas? You pan, and can keep on panning without reaching the limit of your screen. Similarly, when scrubbing values in an input field, in After Effects the cursor is hidden. Maybe hiding is not the best UX, but the idea is that you can keep on scrubbing infinitely without reaching the same limit of your screen.Anyway, I was wondering: could this be a nice UX addition for Figma Design? And other Figma products, perhaps?

I would like to be able to use colour styles just like fills / strokes. Meaning that I would like to be able to apply mutliple of them and or combine them with other fills. Current implementation: Currently using a colour style for either the fill or the stroke completely disables adding new fill or stroke colours Why I would need the feature: Using them in combination with other colour styles and or regular fills / stroke colours would allow me to do things like define shades over an image fill that I could reuse and update easily, or define a highlight shade that I can apply for different states (like mouse over). Currently, if I wanted to do that I would need to create multiple layers and give each of them their own colour styles. This is very much possible but complicates groups that have auto-layout or leads to text layers being below other layers and as such are not easily changeable without going through the layer panel. It would also enable you to quickly create slight variants

Hi everyone,While working on a design system today, I had an idea that I think could be a valuable addition to Figma—especially when it comes to building out basic UI components.It would be incredibly helpful if, after creating just a single base component (like a primary button), we could use AI to automatically generate the full set of common variants based on that one example. For instance: States like hover, focus, and disabled Versions with or without leading/trailing icons Alternate styles like secondary or ghost buttons Of course, this might be harder to apply to more complex components, but for foundational elements like buttons, input fields, tags, or chips, it feels like it could save a lot of repetitive work.I’m sure there’s more to consider technically, but I wanted to put the idea out there—maybe it’s something worth exploring as a potential feature.Thanks for reading, and I’d love to hear what others think!