Share Your Thoughts

Firstly great job Figma Font variables are here!!! Figma tutorial: Variables for typography The only thing missing is the use of percentages in the line-height property. You can not use a percentage in the line-height as it only accepts variables that are a number type. Although the variables for line-height caters for pixel (absolute) line-heights (10,12,14)- it does not accommodate relative line heights. In other words you can’t use percentage variables for line heights that are a percentage of the font size (100%, 120%,150%). Interestingly …You can use a variable for letter-spacing ( which accepts a number variable - but reads it as a percentage) - the challenge remains that line heights by default are absolute not percentages - even though you can input a percentage. Percentages allow greater flexibility and less calculations Word around would be to allow formula in a variable e.g. =[variable] * 1.5 Or figuring out a way for the line height to be toggle between absolu

Hello Figma Community 👋I wanted to raise a question regarding the monthly AI credit system and also share a suggestion that could benefit many users.Currently, on the Professional plan, we receive 3,000 AI credits per month, and as confirmed by support, unused credits reset at the end of each billing cycle and do not roll over.However, in real-world usage, credit consumption is not always consistent every month. Some months require heavy usage, while others involve lighter workloads depending on project timelines.📌 Example Scenario:Month 1: Allocated credits: 3000 Used credits: 1800 Unused credits: 1200 (expired) Month 2: Project demand increases Required credits: 4200 Available credits: 3000 only Result: Need to purchase extra credits, even though unused credits expired in the previous month.This makes planning usage difficult, especially for freelancers, small teams, and agencies where workloads vary.

Hi Celine- Are there any plans to remove this constraint? We have container frames with a handful of separate screen specs in them and would like to designate certain screens as ready, but not the entire set. It’d be great to not have to have the frame or instance top-level, but allow nesting and still mark contained elements ‘ready for dev’. Thanks!

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.

You can currently set multiple stroke colours to an object, but they will share the same properties (thickness, position, etc.). My idea is that you should be able to set all stroke properties on each stroke: Make sense or am I missing something?

When I started sharing AI Skills with teammates, I expected teammates to be able to edit a published AI skill and republish their changes without requiring the original owner to make every update.Problem: published skills are shared for use, but ongoing maintenance is blocked when only one person can update the source skill.Impact: this slows iteration, creates ownership bottlenecks, and makes shared team workflows harder to manage.Desired behavior: teammates with the right workspace permissions can open the published skill in Manage skills, edit it, and use Publish changes to update the shared version.

According to Cursor, this feature API does exist but it’s not allowed. Until we fully trust and understand how AI tools can help us with our work, we need a way to revert back to our designs prior to having any AI tool update it. Client: Cursor + remote MCP (https://mcp.figma.com/mcp) Tool: use_figma API: figma.saveVersionHistoryAsync(title, description?) Error: "saveVersionHistoryAsync" is not a supported API Debug UUID from our attempt: 9e76fe30-de7b-4528-b50e-a337ac24dd14 Use case: named “before Cursor edits” checkpoints with the user prompt in the description

It would be great if dev could export without rounded corners applied and or have some export flexibilities

📣 Don’t make the same mistake we did in attempting to clean up some projects by taking advantage of nesting folders 🚨If you move a top-level folder from your “All folders” section into another folder, then realize you actually want it back at the top level (perhaps due to the inherited permissions not being suitable, or just because you re-thought your organization strategy) there is apparently no way to reverse this change.You would think you could drag the folder back onto the “All folders” option in the sidebar: Nope! Or perhaps up to the team name that shows at the top of the page… Nuh Uh! Maybe right-click > “Move…” on the folder will offer the “All folders” option, maybe even under the “All” tab Negative! We looked through all the documentation and best practices guides we could find and this appears to be a fully-unmentioned gotcha 😖The AI support agent “helpfully” suggested manually re-creating such folders back at the top level, reapplying permissions as desired, and fin

 The `list_shader_fills` tool can only reference built-in shaders. There should be a path to make user-defined shaders accessible via `list_shader_fills`.

It seems a little weird that you can’t copy a link to a layer within a component instance. I understand why this might be technically difficult, but it has been a real pain point for our engineers recently who would like to be able to point their AI coding tools to layers or frames inside components and who aren’t attuned enough to what’s going on inside the layer hierarchy to know why they can copy links to some things but not others.

Hello, It would be more than interesting to be able to create variable at a component scope. And of course instance to inherit those variables. Why ? it would be a good way to organize variables. One file can have a lot of different components and subcomponents = a lot of variables. it would give us the possibility to ease prototype creation by preparing upfront variables in components library. it is a good way to get rid of variants. I mean variants are nice but variables are far better :). it would give the possibility to create different set of variables corresponding to different state of the components faster.

Hi @Figma_support Issue If you choose unevenly spaced objects, Figma doesn’t allow you to enter a numeric figure to evenly space these. It does if the objects are evenly spaced though. Example Let’s say you have 3 objects on the canvas, each at different distances from each other and you want to set the vertical spacing between each object to 32px. You need to evenly distribute the objects first then then set the 32px spacing. Solution Cut the need to evenly distribute step by adding horiz and vert spacing inputs fields when unevenly space objects are selected. Mock up Thank you!

Hi Figma team, It would be very useful if it was possible to crop/zoom-in an image while using the fill option for responsiveness designs, and then deciding if it’s the width or height of the cropped image that should be the constraint. Here’s an example with a pink area showing what part of the image could be visible based on the selected constraint:  Current problem being a cropped image will be deformed if its container change size, which happens  when using responsiveness and auto-layout. Looking forward to see this improvement being worked on! 

Currently, when you draw any shape, the shape becomes selected. Makes total sense, since I would likely want to change the color etc of the thing I just created. But the same is not true of connectors. After drawing a connector, the previous shape is still selected. When I want to change the color of the connector I just drew, I keep accidentally changing the fill of the shape instead. It’s not only extra clicks to change the connector color, but also prone to user error due to the inconsistent design of the property bars and the inconsistent behavior across objects.

The recent update of the Make panel UI has seemingly removed the ‘Go to Source’ button when in edit mode. You used to be able to select an element in the app, then go to the source code.The code would be highlighted for you and you can then make manual edits without the struggle of scrolling and navigating through the code to find the element you want to edit. Please bring back this feature!!

I'm really enjoying the Actions menu! It would be awesome to have the option to access the Assets tab directly as well, just like we can currently access the Assets left panel with a keyboard shortcut. This way, we could set a custom shortcut to open the Assets tab directly from the Actions floating menu.  ​@Figma_Desktop🙏

💡 Feature Idea for Figma: “Fonts Used in Frame”I’d love to see a feature in Figma that automatically shows all fonts used within a selected frame.For example:Fonts UsedInter — 12 layers Regular — 7 Medium — 3 Bold — 2 Roboto — 4 layers Poppins — 2 layersIt would be even more useful if we could click a font, see which layers are using it, and replace it across the selected frame.Suggested workflowSelect Frame → View Fonts → Identify Usage → Replace FontA Suggestions section could also highlight:⚠️ Missing fonts 💡 Too many font families 📏 Inconsistent text sizes 🎨 Similar text styles/colorsThis could make design audits and maintaining consistency much faster.Would you find this useful in Figma? What would you add to this feature?#Figma #FigmaCommunity #FigmaFeature #UIDesign #UXDesign #DesignSystems  

Figma MCP should provide frame-to-image exporting as a tool. That way AI could export graphics in a page design as `.svg`s, `.png`s, etc... and upload them to our cloud bucket,or put them in our web assets folder.

Figma, Auto jump to next comments when previous comment is resolved is frustrating to use. Most of the times when we resolve a comments we tend to look and ponder on screen if we want to add any new comments. When it auto-jumps we need to search for the section again which is really bad experience. Please look into this. 

Selecting color styles/variables, text styles, or anything else from one of these narrow and short popup windows in Figma is like trying to read a book through a keyhole - a major usability issue considering that selecting these things is one of the most common operations that a designer does. I have modified a few lines of CSS in Figma to demonstrate the glory of a wider and taller color styles window, where style names are not truncated so that I can actually read them, and my screen space is being used to its full potential. Sadly, the changes don’t persist after the window is closed. This would be a very nice and probably easy little big update, eh Figma? 🙏 A few lines of CSS can improve the lives of many.

Thanks for the auto layout CSS update. Strokes that sit outside the padding the way border-box works, removed mismatches between our components and our CSS.Inner shadows were missed though? In Figma the offset is measured from the outer edge of the frame, so the stroke eats part of it. In CSS an inset shadow starts at the padding box, right below the border. Same numbers, different result. A Frame with padding 8 and stroke set to Inside with a weight of 4, and one inner shadow with X 0, Y 8, blur 4, spread 0:- Figma renders 4px of green. The first 4px of the offset sit underneath the stroke.- Dev Mode hands out box-shadow: 0 8px 4px 0 #00FE00 inset, which renders 8px of green in the browser.- Matching Figma requires “0 calc(8px - 4px) 4px 0 #00FE00 inset”, so the visible offset is Y minus the stroke weight.Could inner shadows follow the same model as the rest of the auto layout change, or get a per effect switch like the Included and Excluded border option? Until then it would already

Hello,I can’t see the “minize UI” icon on every tab on the sidebar, and before the new UI I could minimize in every tab. I wish we had that icon back, it is very useful. Thank you for your attention!

In the People option of the Admin panel, I need a column to identify which group each person belongs to. Currently, it is very difficult to find and track this information.--En la opción 'Personas' del panel de administración, necesito una columna para identificar a qué grupo pertenece cada persona. Actualmente, es muy difícil encontrar y rastrear esta información.

Is it possible to change default font in Figma? (from Inter to Mardoto)