Share Your Thoughts

We have a general collection of colors but for my specific file I want to add more variables. However this is not possible with extended collections. My work around is to use less frequently used variables (button-hover) for my usecase (color-bold) and this makes it very confusing and limiting.

Sometimes I use dev mode links to look through people’s files. For every file I viewed I get notifications when something is marked as Ready for dev.And it also bloats my mail withFrame 2087324273 is ready for dev in Draft | You're subscribed because you viewed this file in Dev Mode.Kinda tired to unsubscribe from every single file. Why there’s no option to opt off every dev mode updates in settings? Figma notifications settings  

If I have a team with some members not spending their Make credits, I want to commandeer those as an admin. Or even better, I’d like an admin setting to put the sum of all the credits for our full seats into one shared bucket.

With the strict enforcement of AI credit limits starting March 18, I’ve been looking at our organization's options for scaling usage. The current pricing structure for additional credits vs. adding new seats seems completely disconnected from reality for power users.Let’s look at the numbers for a Professional Plan (2026 pricing):Option A: Add a Full Seat. Cost: $16/mo. Cost/credit: ~$0.005 Cost for 3,000 credits: $16 Option B: Pay-As-You-Go (Overage). Cost/credit: $0.03 Cost for 3,000 credits: $90 Option C: Shared Credit Subscription. ​​​​​ Cost: $150/mo for 5,000 credits. Cost/credit: $0.03 Cost for 3,000 credits: ~$90 The Result: It is 5.6x more expensive to buy official "extra" credits than it is to simply spin up a secondary "ghost" seat and use that account for AI generation.The base credits for my team members who don't use AI are currently "locked" and wasted, while I’m expected to pay $90 for a 3,000-credit overage that could be covered by a $16 seat. We need a way to p

It really should allow external users to leave comment on Figma make. Commenting on Figma make is crucial!I have been pasting them back to Figma Design just to get comments for feedback...

Figma Make Commenting Feature Request.Feature request: Add native, pinned commenting inside Figma Make prototype view/links (similar to Figma prototype presentation comments). Current behavior: Comments are not supported in Figma Make today, so feedback needs to happen in Figma Design or FigJam instead.

I really do not like the new confirmation dialog when deleting an account.  As an admin of an instance with 14k+ users, I delete people every single day and this new dialog gets in my way.

If I am writing feedback in a comment and need to go back and inspect something, once I click out of the unsent message, the entire typed comment in progress disappears. Can we please have the ability to auto-save comment drafts so I do not need to remember to copy and paste what I have in progress each time?

Right now, size depends on stroke width, so stuff like this happens: I want to be able to adjust the arrowhead scaling, just like in any other design tool:

Currently, when using variables, in the settings you can’t select wether you want a value (for example, padding-sm) to apply to just the padding or the gap of an auto layout. Which means that when you want to select a gap variable, it shows all the padding values as well. Can we get a setting for this?

It’s so limited and we have to clear it everytime. Increasing the limit or making it unlimited and wrap the text is a great idea.

I’ve just applied variables to all our project’s text styles. It all works as expected. However, in inspect mode, font weight it still displayed as normal css value and not with css-variable. See screenshots. Is this a bug or me messing up things?

Hey ​@ksn just one small request can we get tracker and queue on our community account that would help for sure. Thanks 😅  

Hi everyone,Is there an option to cancel the export action?While the action is running it shows this nice “Exporting...” info:But I could not find a way to abort the action.And if one made the mistake to choose export 1064 x instead of w it takes quite a while until the export action is done. Meanwile I cannot edit anything else.Why not add a little (x) next to “Exporting...” to give a possibility to stop the action? This would be great!Best, Sarah​​​​​

Hey all - I am running into a bit of a issue with how component properties are working today - specifically in the context of Figma-to-code workflows. It’s not so much of a “blocker” but I think it would be a huge unlock if we were able to attach “meta” or “pass-through” properties on Figma components.Currently any properties added to a component need to be “used” in your component. A variant, boolean, etc. needs to affect something structural or decorative in your component or you’ll see an error icon and a message “Not used within component”. Instances of the component will not contain these unused props. This is reasonable since you don’t want to have extra props on your component that are effectively no-ops. However, as Figma designs and components are increasingly the input for many design-to-code workflows, many of the things we might want to associate with a given component do not necessarily have a visible presentation impact on the Figma side, but are used in downstream coded

So I created a skill to help me organize my Components in Design Library, something like rename layers, reorder variants to make library more tidy.But when I (or AI) trying to reorder variant values’ order, it says that no API support this kind of operation. For example, I would like to change Variant “size” from [medium, small, large] to [small, medium, large], it can’t be done by program, only can be change manually.I can ask AI to create a new, same Component Set, but it will lose connection to exist instances, and it’s bad.Is there a way to adjust values’ order by Plugin API?

Hi, as I have used up my 3000 AI credits, I would like to request adding a LOW CREDIT BALANCE alert, since AI credits can’t be manually reset or extended each month? If possible, maybe offer an option to purchase more credits WITHOUT changing our plans?

As mentioned in closed topic https://forum.figma.com/t/bug-autolayout-resizes-incorrectly-when-it-contains-no-visible-frames/14619, Is anybody facing the same problem? Even all contents inside “trailing-section” frame are invisible and frame resizing is set to “hug”, it still has 24 pixels of width.

it would be game changer to be able to export generated artefacts with figma make to figma design  

Hey, It would be great if we could manage the z-index of some elements. Example: I 've got an element which has a built-in tool tip displayed on hover (or click, whatever) if it’s in auto-layout and the previous element is just above, this tool tip will appear behind this precedent element. The only way to make it appear on top is to place it manually on the actual layout which takes horrendous amount of time. I suggest there would be an option “take the highest z-index” or such when defining “display overlay” in prototyping mode.

When overriding a single element inside a slot in a component instance, Figma marks the entire slot as overridden. As a result, updates made to the main component no longer propagate to any elements inside that slot — even if only one element in the slot was actually changed. Expected behaviorOnly the modified element should be treated as overridden.All other elements inside the slot should remain linked to the main component and continue to receive updates.

I’m with Figma in this AI Design battle. I’d be happy to share my internal AI VScode + copilot workflow, maybe it would influence the Figma Make approach to what a designer needs from an actual “vibe designing”

Love that branches were added but would like to make some suggestions: Support sub-branches from branches. This is a really helpful way to signify milestones in an app design and allow for many avenues of exploration and iterations with the ability to only merge the branch (feature or milestone) which was approved. See example below of how I would ideally structure the process of a project

Feature Request: Git-like Version Control for Figma BranchesCurrently, Figma allows us to create a branch from each file, but this limitation makes it difficult to manage complex design workflows — especially for teams working on large design systems.Git-like branching would make version control in Figma far more powerful and flexible. With this approach, designers could create multiple branches from existing ones — functioning much like environments (e.g., test, staging, production) in development.Attempt at elucidating through a flow diagramAs a design system maintainer, this would be a huge benefit. For example: Components that need additional review or testing could be safely designed in separate subbranches. Compatibility between different branches could be tested before merging changes into the main file. It would reduce merge conflicts and ensure higher quality and consistency across the system before releasing updates. Allow for other users to expand on branches through t

I was looking at the release notes to double check my gut feeling that Figma itself has not been getting a lot of love lately. For my personal uses that has been the case. Only vague AI related things, which might be fine but makes me feel a lot of things are left behind. The trigger for posting this was looking at “Code Connect” after reading about a “bug” in Slots that seemed to be “intended behavior” (which is weird). This feature coming from 2024 (!) seems to be in Beta still (according to the blog post). The Github feels completely abandoned. This reminded me of things like branches (total abandonement), Percentage widths, Slots that feel half baked. The whole grid thing that seems to fizz out. New UI that was not a big success (I am still scanning everytime I select a diffferent layer where things are after all these years). Still not seeing the new App layout with the buttons on the left side (my team does, not me). Etc. Etc.I was just curious, I am getting the same kind of feel