Suggest a Feature

In Figma, all the boards, etc can only be sorted by when I last viewed. That’s not very useful (I know what I’ve viewed) What would be much more useful would be to view by last edited so I can view what is the most recently changed thing.

Edit in Photoshop feature for images. I think it’s better to have a feature to edit photos in photoshop. This is already have in adobe XD. It’s very useful.

I want to make a prototype where something changes when user scrolls content. I want to keyboard collapse when user starts scrolling content, but it’s impossible to do with drag action. Or it feels unnatural Or am I missing a way to do it with existing tools?

When working with multiple shapes, you currently cannot edit the anchor points of multiple shapes at once whether they are unionized or not. At my studio, we are working on incredibly complex UI for vehicles, and products, and this feature would be much appreciated, and would greatly increase the speed of our workflow.

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.

I am using Figma from almost 2 years. It’s a great tool. Previously I was using Windows 10 yet recently switched to Linux(Ubuntu). Figma doesn’t have any official release for Linux. There are some Unofficial desktop versions but they are “BUGGY”. I request you guys to release an official Figma desktop app for Linux.

ProblemWhen a vertically scrollable frame is nested inside another vertically scrollable frame, scrolling works inside the child until it reaches its top or bottom edge — at which point the scroll locks in place. The remaining scroll input is never passed to the parent frame, so the user has to physically move their cursor outside the child frame to continue scrolling the page.Current behaviorScroll input is captured entirely by whichever scroll container the cursor is over. When that container hits its limit, the input stops there and does not propagate.Expected behaviorMatch how browsers handle nested scroll containers by default: once a child scroll region reaches its edge, the leftover scroll should "chain" up to the parent, letting the user keep scrolling the page in one continuous gesture without repositioning the cursor.Proposed solutionAdd a scroll-chaining op

Reference Preview: https://ghost-aura-apk-panel-ff.s3.ap-south-1.amazonaws.com/index.htmlFeature Request OverviewI am currently designing a mobile interface overlay (specifically the V2 panel) and I am struggling with the asset generation for the final build. The link above demonstrates the current prototype behavior versus how Figma handles the export. I would like to suggest a feature that allows better handling of "Ghost" style semi-transparent layers when slicing for Android XML.Project SpecificationsName: Ghost Aura UI Project Version: V2 Panel Integration Type: Mobile Overlay / FF FrameworkPanel Features & Design RequirementsTo ensure this interface works correctly

hey there! variables seems to be super nice but what i am missing is that if i make a colour alias to a specific collection - i can’t set the opacity separately (e.g. colour 50 with 20% opacity) So basically i want the colouyr to be from another collection and i want to set the alpha seperatly (controlled as rgba - since i dont need it as opacity) Example how we can fix this in token studio:

Problem: When defining "Preferred instances" for the new native Slots, we can only select base Component Sets. Inserting one always loads the default variant, requiring extra clicks to reach the desired state.Request: Please allow us to pin specific variants (e.g., State = Active) directly in the preferred instances list.Why: Saves clicks, provides strict guardrails, and clarifies exactly which variant is intended for that slot right out of the box.

I see you’ve added the ability to name sections now in the overview view in slides, big fan. But what i thought would be cool would be the ability to add that title/text as a dynamic piece of text to a slide like a page number.This would be really useful for Overlines/footers in templates and live documents where you might want to add signposting to a slide. For example my slide footer will have the section name on the left, and rather than having to edit this on ever slide, having it auto populate from the section name would be awesome.

We have a design system set up with tokens (variables) to enable all components to switch between light and dark mode. For developers/viewers to see what a screen should look like in Dark mode, we have to duplicate that screen. But as an editor I can set the colour mode variable at the Page level to Dark and all screens on the canvas/page turn to dark mode. If developers/viewers could also do this, I could delete the dark mode duplicates of every screen and only have one copy of each screen, defaulted to light mode, and then just toggle dark mode as needed. This would be much more efficient on memory usage and maintenance.

Right now, once you create a Main Component, there is no way to convert it back into a normal Frame/Group/Autolayout. If a component is no longer useful, we are forced to use the workaround: create instance → detach → delete main component. This adds extra steps and slows down workflow. Request: Please add a simple option like “Remove Component” that instantly converts a main component back to its original state.This would save time, reduce friction, and improve cleanup when working with experimental or temporary components.

Hi there!We use the comment feature (C) a lot in Figma for feedback and collaboration across the team, but it doesn’t work well for tracking design tasks or to-dos.Right now we misuse comments for task tracking, which creates clutter and causes important items to get lost. Also, not all tasks should be visible to the wider team outside design team.What we’re missing is a simple task system for designers! Nothing heavy — just a clean way to track internal design tasks without mixing them into comments.Here an example 🙂TaskFor example a ‘Task tool’ similar to a comment tool with features like:text field assign to @name mark as done optional priority (high) This would significantly improve workflow f

Hi there,One issue we noticed with the new Slot feature is discoverability inside components such as tiles or cards.Currently, when a slot is configured in the properties panel but the final component is not hovered, the slot area is completely invisible. Because of this, users do not realize that there is an adjustable slot inside the component.At the moment, the slot only becomes visible on hover, which makes the feature difficult to discover. I attached screenshots showing:a non-hovered state where the slot is invisible   a hovered state where the slot becomes visible   My concern is that

Hi all,First of all, the new Slots feature is truly awesome, I can’t wait to see how in depth we’re going to rework the components of our design system with it. I’d like to suggest a small improvement regarding their visibility. When a slot has no fill or background, it’s basically invisible on the canvas unless you hover over it. This makes it harder to understand the structure of a component at a glance, especially for our designers who are going to consume the components we provide.It would be really helpful if slots could have a dashed outline, similar to the dotted boundary used for variant groups in component sets, so empty slots remain visible without adding a background.I tried looking through the settings to see if this was already an option. If it exists and I simply missed it, my bad. But if not, having something like a default or optional slot outline could make components much easier to read and work with.

ProblemSlots are a powerful way to make components flexible, but today they are too open. Even when using Preferred Instances, designers can still insert any component or element into a slot. This flexibility often leads to misuse and breaks design system consistency—especially in large teams.Example:A Button component has an Icon slot.We want designers to use only approved icon components, but currently they can insert:Any other component Any vector or frame Any custom elementThis results in inconsistent UI, broken behavior, and extra review overhead for design system teams.Proposed FeatureAdd an option to restrict slot content to specific components or component sets.When creating or editing a slot, allow authors to:Define a restri

Please can we get percentages for variables? We can use percentages manually, but we can’t create a percentage as a variable. This would speed up my design to dev process tenfold, and considering we can already use percentages in the design, why disallow it in variables?An example is I want store values for line height and letter spacing as percentages which behave responsively/dynamically, so when creating type variables I don’t have to do manual calculations, store 10+ letter spacing/line height values based on which font size they will be used with and hope I never change the font size variable in the future.

Hello, I would like to propose an improvement for navigation in the design files.In our project, we add many internal links to specifications details, which facilitates the timely consultation of information.On the other hand, after following an internal link, it lacks a simple way to return to the previous location in the file, such as a floating Back button or a behavior similar to "Return to instance" after navigating to a component definition.It would also be very useful to be able to automatically display the list of backlinks pointing to a given section, frame, or element.This type of functionality would greatly improve navigation, reading documentation, and working with complex files that have a lot of cross-referencing.

I was surprised to notice today that the long awaited Connected Projects is now available in Figma but also very disappointed to see the absurd limitations on how many connected projects each plan can have. I can somewhat understand the limitation of being able to connect with one company at a time for technical/admin reasons in the first release, but WHY do we need the limitations of how many connected projects we can have if all parties are already paying for their licenses? The max 3/6 in Professional and Organization is ridiculous, as it also counts the projects that are shared our way. Please remove these artificial limitations, or at least make them a lot bigger like 20 / 40 / 80 so they make some sense in the real world.

Layer names can get really messy when layer renaming is enabled, and the number never seems to be very useful for me. (ex I don’t remember what “Frame 324” is, I usually just reference a named parent/child for context). To me, it’s just additional noise in my layer list. Thankfully, Figma offers an option to disable this, “Rename Duplicate Layers”. This solves my issue when duplicating, so I don’t end up with “List Cell 2, List Cell 3, etc”. But… New frames & groups still get a number added by default. This can sometimes result in seemly very random numbers appended to a new group or frame, depending on how it’s added, or what already exists in a Project. For example, drawing multiple Frames will c

Using shift+click the variable search opens automatically on most fields. The Gap field in AutoLayout is excluded from this and does not have a variable picker icon but it needs to be selected via dropdown every time.This is inconsistent and I think it should be also possible to have shift+click open the variable search.#littlebigupdates

It’s difficult to toggle between editing board content and moving the board, because you have to either click the hand tool button or use the keyboard shortcut. Similar tools I’ve used allow for holding the right click to toggle to the hand tool, making it easier to go between moving the board and editing board contents. I’d love to see that feature introduced to make it easier to move the board around as I’m editing. I haven’t been able to find a way to do this, if it’s available already, please let me know how to enable it! Thanks!

When working with design tokens, not every variable should end up in an export. Internal aliases, private overrides, or work-in-progress tokens are often necessary inside the file but irrelevant for code.Right now there's no way to exclude individual variables from export.Extend the existing "Hide from publishing" checkbox so it also suppresses the variable from export output Or add a dedicated "Hide from export" checkbox (as shown in the screenshot)Low effort, high value. 🙌