Suggest a Feature

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.

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

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

I work for both desktop and mobile screens and I would like to save custom frame sizes and have them under a custom category. basic desktop sizes like 1366x768 is not available in the presets and the desktop category only has Mac screen devices as options.

Allow the users can move the new toolbar through the canvas, that today is fixed underneath the page. I liked the new version but I believe some extra flexibility on it would be welcome.

Figma is the most intuitive tool I have ever used and I would love for Figma to expand into web development! Publishing a website directly from Figma would be incredible!

When adding components to a Slot and attempting to surface nested properties I see a message that nested properties can not be surfaced with Slots. This severly limits their usefulness to us since we are creating multiple composable components using sub components with properties and having to drill in to each instance in a multi-item Slot is very time-consuming.

Since a couple of weeks Figma Buzz is auto-naming the frames it creates when BULK CREATEing. It simply adds 10 (or something) characters from each CSV-Tag and pastes them in.Please add the possibility to deactivate this feature. It messes with our current workflow and forces us to add additional steps. Would also be nice to be able to fine tune this to our needs (i.e. choose what tags should be used)Also: there seems to be no documentation in terms of release-notes for this.

As a user I want the text to auto-adjust: in this way I can write sticky notes different in length (without breaking them in height).

As described in the title, links are broken as soon as you cut a frame and paste it elsewhere (on the same page, in the same file).How to reproduce this issue:Copy the link to any selected frame Save the copied link somewhere Cut the previously selected frame and paste it elsewhere (same file, same page) Open the saved link The link no longer leads to the frameSuggested solution: When a frame is cut and pasted, the associated link ID should not be lost.

A lot of AI features in Figma so far seem to be generative, which IMO is mostly fruitless for the core auidence as current models are not capable of new problem solving, only generating variations of the combined knowledge of everything that has been observed before, without understanding the context of decisions made to implement design choices as well. Where I can see see value add is in other aras. QA for example - perhaps pointing a dev URL at the tool to see how front-end have developed the designs and comparing to what was in the original figma (visually, not comapring the code generated by Figma, which is often not all that helpful in established systems) - could help catch mistakes and also documwent intentional changes in the design to development process. 

The experience of Move to Page can be frustrating and inefficient. That's because when a user moves a frame/section to another page:there is no immediate feedback to where the element was placed user must manually go to the page and search for the moved element often, the element is placed using the same absolute coordinates, and that can result in it being placed on top of other elementsThis creates unnecessary hassle, especially in large files with many sections, frames and components. I can think in 3 possible solutions for this problem, I hope my suggestions can help y'all (and myself!):Auto-navigate after moving: after using Move to Page, automatically switch to the destination page and bring the moved frame into view, allowing the user to immediately position it (similar behavior in Apple Finder). Smart placement instead of absolute coordinates: instead of preserving exact x y coordinates, place the moved frame in a visible empty area, or far from existing content to avoid overla