Suggest a Feature

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.

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?

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.

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

Allow offline work on files through the Figma app. This is important because internet connections aren't always available—whether you're commuting, on a long business trip, or working at a client site without connectivity. Work continuity matters. Offline support is standard for professional production tools, even cloud-based ones.

Of course it is easy enough to lock layers but I think that it would be helpful to be able to lock pages in a fashion similar to the layers. I often place root (master, main, og?) components on a separate page and it would be nice to be able to lock these pages to keep items from moving around without intention.

While there used to be a Copy to Figma sites button, it seems that this has been deprecated in favour of “send to Figma make”.  I would request for this feature to be added back in, as well as a way to copy an entire figma file into figma sites (rather than creating a new one and adding frames as separate steps)

Within Figma Sites, you are currently unable to provide “navigate to” as a type of interaction. I am aware that you can add a link, however doing so causes an issue if you have the goals ofDoing conditional navigation (i.e. if X== true Navigate to A, Else navigate to B) Changing a variable, and navigating through the same button (e.g. set Y to Z & navigate to C)1 because navigate to/link to is not available in the interactions (where conditional is found) & 2 because if you assign a link, then onclick is removed as a trigger for interactions In terms of both, I accidentally used a workaround by copying a frame from core Figma into Figma sitesHowever, this is not convinient/intended, and I worry that it may create issues with future versions of figma sties.

The corner radius tool is great if you want to make rounded corners but what if I wanted to make sharp, folded or clipped corners like in the shape below?The catch is that when resizing, the scaling and the angle for these corners should stay the same. If you simply create a shape like this, it doesn’t really scale well if adjusting only the height or the width - the angle of the corners suffer. Has anyone figured out a solution to this or is this something Figma could implement perhaps?

ProblemWhen using stroke-based icons inside nested components (e.g. button components), resizing behavior in Figma causes major inconsistencies:• If the icon is a component, it keeps its original size when the parent resizes• If constraints are set to Scale, the icon scales visually but stroke width does not scale, causing icons to appear heavier/darker• The only way to get correct proportional scaling is using Scale tool (K), which does not work with Auto Layout or component resizingThis makes it extremely difficult to build scalable button components using stroke icons.ExpectedResizing a component or instance should optionally behave the same way as Scale (K):• Stroke width scales proportionally• Corner radius and effects scale correctly• Works inside Auto Layout and nested components Proposed solutionAdd a global or per-object option similar to Adobe Illustrator:“Scale strokes & effects when resizing”​This would:• Fix stroke icon inconsistencies• Enable proper scalable icon usag

Use case: Once an advanced UI has been built , users want a way to quickly select nested components in order to modify their properties and attributes. In this stage of design, designers are less interested in manipulating sub-elements of a component, and more interested in selecting the component itself to modify properties and variables. Current challenges: the deep-select modifier (CMD/CTRL) is currently the most efficient way to access deeply nested items, however it is fairly indiscriminate and will often select the deepest nested element under the cursor. With complex components this often means a graphical element like a frame or a text element, requiring the user to step out of the hierarchy, often a number of steps, before arriving on the parent component, or they must use the mouse to then select the parent component from the Design properties panel. Recommendation / Request: Provide an optional modifier key to be used while deep-selecting to restrict selection to only compon

ProblemThere's no plugin or REST API that exposes a fresh view of which team libraries are currently subscribed to by a file. After a user adds or removes a library mid-session, every documented and undocumented signal continues to report the prior subscription state until the file is reloaded. This makes it impossible to write a plugin that correctly classifies orphan references (variables, styles, components from libraries no longer linked to the file) without asking the user to reload Figma after every library change.Use caseWe're building a plugin that scans a file for orphan references — bindings to variables/styles/components from libraries that aren't subscribed by the file. The orphan signal we use today is figma.teamLibrary.getAvailableLibraryVariableCollectionsAsync(): any remote collection whose key isn't in that response is classified as orphan. This works perfectly when the cache is fresh (after file load), but breaks silently when the user changes subscriptions mid-sessio