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 😅  

Hello, I tried Figma slides to re-create my portfolio, which I had already created in Figma, because I was attracted by the possibility to quickly reorder the slides. However, I noticed a problem: while I can create internal links in Figma slides which allow me to jump from a slide to another, when I export said slides as a PDF, the internal links are substituted with external links which jump back to the Figma website when clicked, instead of allowing you to navigate through the PDF inside your own pdf viewer. This is a problem for various reasons: you can’t easily navigate around the .pdf offline, since each time you click the supposedly internal links you instead get redirected to a web page; the offline .pdf and the online version can be out of sync. Meaning that the offline versions, which may be several and have different slide orders or different elements (it’s common practice to slightly tweak a portfolio when you send it to different clie

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  

I have a very distinct first and last name. My Figma profile uses my full name, which is important for our organization-- coworkers and partners in Figma need to be able to easily tag me in comments and see who worked on files. However, I would like a way to have a different display name and handle for the Figma Community. I don’t really want my questions about plugins, etc. to be publicly searchable if someone were to Google my name. I prefer to have a privacy option and keep my professional work and personal online presence as separate as possible.

When I open my Figma project files, they are always sorted by “Last modified” by default. I can manually change the sorting to Alphabetical order using the dropdown in the top-right corner, but after refreshing the page or reopening Figma, the sorting resets back to Last modified. I’ve seen other people posting the same issue. I want to push this topic forward with sharing it again. Is it possible to fix it please dear Figma? :)

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.

Hi Figma team,My team and I have been experimenting with slots recently. I'd like to propose a feature enhancement: when a component with properties is added via a slot, those properties should be accessible directly from the main component.Ideally, these nested properties would surface automatically, eliminating the need to click deep into the component hierarchy to make edits.

This has been mentioned here: Hide layer using variables - #5 by Andreas_Braendhaugen1 Invert boolean variable for layer display - #14 by Desislava_Slavkova Inverted Boolean Property - #2 by drewcovi_usb but those topics are all closed. I am looking for the availability to HIDE a layer when a Boolean variable is TRUE and SHOW it when it is FALSE. So, the inverse of the default/current behavior. I want to do this without using components. Use case: When a variable is true, show one frame. When that same variable is false, show a different frame. I can get basically this by using two different variables:

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.

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?

I often work across multiple pages within a single Figma file/project, and I’d love the ability to open different pages as separate tabs in the desktop app—just like I can open different files. Currently, I have to either open and close multiple pages many times to get what I need from other pages, use multiple windows or duplicate the file, which isn't ideal for managing design systems or multi-page projects.This would greatly improve workflow efficiency for designers managing large files or working across different sections (e.g., desktop vs. mobile layouts) simultaneously.Please consider adding support for tabbed views of multiple pages within the same file.

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 sim

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 sel

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.

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 s

Enhancing variables to have extra logic in place so that variables can be partially based off other variables e.g. Number new_variable = “{other_number_variable} + 4” String new_variable = “{other_text_variable} New Text” Colour new_variable = “{other_color_variable}, opacity 4” Boolean new_variable = “not {other_boolean_variable}”

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.