Suggest a Feature

Hi there.I create a new thread because this one is closed: Like many, I do my resumé with Figma. And I’ve seen that the text exported PDFs have undesirable spaces inside the words.Example:Copy/paste this text and you get:“with 2 0 + years of e xperience”, which is wrong!! Of course, the MKitFPDF plug-in solves some problems but brings some others, without to say it’s not free.Did someone got a real fix for this?

I’m new to prototyping with variables, and I’m finding the learning curve is pretty steep 😅 I’m trying to build my own variable troubleshooter in my prototype that displays the current value for each variable, to help me see if the issues I’m running into are due to my failing to SET a variable, vs failing to properly DISPLAY a variable. But now I find myself troubleshooting my troubleshooter… 😭 Place forehead on desk, repeat rapidly It would be amazing if there was something in the native Figma UI for the prototype that would display the current value for each variable. Then as I interact with the prototype, I can see whether those variables are changing properly or not. It would really help narrow down the culprit for my prototype bugs. For example, when previewing a prototype in Axure, they have a Console panel that looks like this:

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 f

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

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 ext

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.

I have a single page site that has a nav bar that scrolls to different sections on that page. I want to add sub pages for some of the content on that page, and I’m trying to add the same nav bar and anchor a nav menu item to a section on the main page but it doesn’t seem like its possible unless its on the same page. 

Hi! First of all-- congratulations on the release of CMS! I’m already super excited to create stuff with it and I’ve been playing around with it this morning. Hereby my humble feature requests for the future of CMS!Categories and tags with separate pages for their content. Search and date picker (for events) functionality. I would love to see component swapping supported inside CMS, so that I can pick a different component per CMS article if I want to highlight it on my list with a special component for example. (A feature like this would be ~ incredibly ~ powerful.) Or/and, the ability to change page variables in a CMS item, so you can for example change the colors of the page based on the variables set in the item. The ability to connect CMS fields to the SEO, so you can attach a meta description and social sharing image to each CMS article. The ability to hide CMS items from lists but still have them in your database and vi

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 :)  

Hey! How can I transfer the AI generated Prototype in Figma Make to Figma Design and continue editing it manually there?

These are new and improved color formats that replace hex and rgb. They will soon become the standard in web browsers. They open up more colors than are currently possible. The Expanding Gamut of Color on the Web | CSS-Tricks - CSS-Tricks

Hey there! I was also wondering if it is somehow possible to include also the layer of variant controls to be exposed or hid! I often have cases where I need to nest base components e.g. an icon wrapper providing me with the ability to select certain sizes, or color overrides and boolean props of an icon. I am now able to expose all of those or none, but I can’t restrict the users to only be able to select just some of those. What do you think about it?

I have a few SVG shapes as part of the branding for a project I am working on. I’m in the process of building out a component library and for the primary CTAs, one of the shapes will be the background for the CTA. That white background would typically be a solid fill with border radius, and using Auto Layout would be able to grow and shrink based on the label overrides per instance. However, I am unable to get an SVG working as the frame’s fill. It does allow me to “Choose image” and select the SVG but it never displays. From the docs, there is no mention of using SVG for this, as opposed to PNG, JPG, etc, and I don’t see why we can’t use an SVG as a fill.

Describe the problem your experiencing and how your idea helps solve this The issue with this feature has been covered many times in Spectrum discussions:Spectrum – 3 Jan 18 There is a way to avoid this by holding SPACE as soon as you click & don’t start dragging the object. But why force us to do acrobatics with our fingers by holding down an additional button, just to move the object? Why not provide an option to disable that functionality completely? Nagaraj Chandran had a very logical idea in his comment: “I don’t want to hold the spacebar key to disable auto-nesting. Maybe, it should be the other way around. Hold spacebar or any other key to auto-nest.”

My team and I are currently having the inconvenience of having to publish our library every single time we make even a small change (like a font size increase, color change, etc.) and then switching to the working file and manually updating the library. Due to the nature of the project we do this quite frequently and having to publish – switch file – update every single time to see the changes in our designs turns out very time consuming if you add it up. It would be amazing if Figma could integrate a shortcut for automatically updating a library and automatically updating the files it is being used on (like a cmmd+S shortcut!), of course not everybody might want to have this so it would also be nice to be able to turn this shortcut on and off.

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.

As I was looking for a way to do this natively in Figma, I came across this concept article on Medium. In the article, Андрей Насонов (Andrey Nasonov) describes adding the option to choose alignment in the image settings beyond the default centered. This would be a simple but huge improvement to image settings, especially for responsive design. Here’s his example of how that might look on the Properties Panel for images:

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,The addition of annotations and measurements to Design mode is such a great decision.However this is rendered almost useless if the annotations and measurements can’t be made visible to View Seat users.Often annotations are used for communication with a range of stakeholders, not just designers and developers. It’s not viable to upgrade every stakeholder to a Full or Dev seat to engage with this content.

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.