Suggest a Feature

To the Figma Team and Community,I'm writing today with an urgent and heartfelt request: please make the Dev Mode focus view available on the Professional plan. Gating this feature away from Professional users feels like a profound misunderstanding of how your community works and builds in 2025.The landscape of product development is changing rapidly. We're in an era of "vibe coding," where small, agile teams and even single-person companies empowered by AI are creating products with massive impact. Many of us on the Professional plan are exactly these people – the freelancers, the indie hackers, the startup founders who wear multiple hats. We don't just design; we code. We build.Why are you creating such a painful partiality between design and code for your Professional users? To give us a powerful design tool but then restrict a feature that streamlines the most critical handoff – from design to code – feels incredibly counterintuitive. It pena

 I’ve been exploring Figma Buzz and noticed an issue affecting our workflow. We already have asset libraries (icons, illustrations, images), and while creating a Buzz template, you can define instance swaps (for example, for icons). However, swapping these instances only works in design mode, not in Buzz mode.While the "Swap content" feature is available, it only works if assets are components within the same variant set. Converting our 400 icons into variants, or even more illustrations - isn’t practical.This limitation is a major blocker to us adopting Figma Buzz, as it prevents collaborators from easily swapping assets within Buzz mode. Related topic:  

Figma has removed the ability to switch frame between Portrait and Landscape mode (without adding rotation to nested elements). Now the only option is to “rotate” the canvas and it adds -90degress to everything that is designed within. Which also flips W and H. And if a component is designed in portrait and then added to landscape (rotated artboard) and you want to “fill” autolayout and contraint proportions totally mess up.I could make my own frame and use that instead, but I cannot save it as a template within Frame templates, super annoying.Bring this back please: https://www.delasign.com/blog/figma-frame-landscape-portrait/ 

I've been using figma for more than 3 years now and it has been extremely helpful to me. And It’d be really helpful to have an scroll up / scroll down commands because the absence of this feature is holding back my ideas and its easy to explain how the website will actually work when built. i know you can do this with drag option but it feels unnatural and cant go back to the previous frame and feels unnatural.thank you.

Currently exported .PDFs out of Figma are not accessible, because the text is flattened as images. I would like to request an option for exported .PDFs to have editable text. This would be a game changer for our team to move off of Sketch! 😃 (Sketch allows for .PDFs to export with editable text, but Figma does not)

Scenario: Large design file with 15+ pages#Designers per team: multipleContext: We have multiple feature based design files and each file is 10+ pages with multiple designers in one team working in the same file.Problem: Branching creates multiple huge files with all pages. With multiple designers working together and making updates every week if not everyday, its very hard to merge these huge files after reviewing multiple updates every time a change is made.Idea: There seems to be a need for selective branching and merging. The user can select what pages they want branched and merge them once the feature is updated. This would not overload the files or system and would reduce redundancy.

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

I’m a UI/UX designer and a regular user of Figma, and I absolutely love how collaborative and flexible the platform is. However, I’ve run into a limitation that I believe many users might also be facing:Problem:There is currently no way to control access to individual pages within a Figma file. When I share a file with a client or collaborator (as a viewer or editor), they can view all pages. But in many real-world scenarios, I want to:- Share only specific pages with certain users- Keep draft or internal pages private from clients- Give different collaborators access to different sections of a fileProposed Feature:Allow users to set **page-level permissions** within a Figma file, similar to how layers or frames can be organized and hidden. This could be something like:- Page visibility toggle (private/public)- Per-user or per-role page access- Ability to share a file with filtered pages onlyWhy This Matters:

It is possible to lock frames, only to have everything in it locked… Any way to lock just the frame in place but not the content? So I can interact with the content without having to worry about constantly selecting the frame, moving it around etc…?

I want make some element in frame just creating it in place where i want to see it, and during work i also use AL, and i always have to make element somewhere, because of AL and than add it to place where it have to be, and after it compare sizing and other visiuals elements Let me make element that already have absolute position by some shortcut, to quick add layer to layout without problems with override AL settings

Would be great to have a native skew and shear tool in Figma. Even with plugins, I’m not finding a way to control the skew anchor. Just something simple like Illustrator’s Free Transform, where you can skew an object and choose where the effect starts from.

Unsure if any additional context is needed but would be a lovely feature 

Hi everyone, As you know, being able to add negative padding is a must when creating design systems. However Figma only allow negative values in the inner-spacing between elements in auto-layout. We found a workaround and thought it would be useful to share it with the community. If you define a local variable, type number, and add a negative value (e.g. -4px), you can then apply this variable to the auto-layout padding and it will work. In summary: use local variables to define negative values and apply such variable to the padding.

Example:My color picker component is created from an instance of my input component.I would like to block certain properties of the instance for its use in the color picker."

I don’t know where Figma’s server is but def. not in my country. So it is slow sometimes and can’t even open a file sometimes. So why not add a proxy setting so that we can speed things up if we need?

I would like to be able to have two actions happen on hover. E.g. a button component with a hover state, accompanied by a tooltip - also on hoverstate. On click a third action happens.

I'm currently working on a multi-brand product (EHR dashboard) using Figma Pro. I maintain a shared design system for efficiency and consistency, and I use this design system across multiple design files within a project.For each brand, I need to: Create a new project Duplicate both the design system file and the product design file Customize the design system with unique logos, colors, and typography per brand The problem is:When I duplicate the files for Brand 2 and move them to the new project, the duplicated design file still links back to Brand 1's design system instead of the duplicated one. Even if I duplicate the design system file separately, the link doesn’t reset — which means changes made to the design system (like updating Brand 2’s colors) affect Brand 1 as well.Currently, Figma doesn’t support project-level duplication, which could have helped preserve the file links and created is

I often use Miro to gather design inspiration. I take screenshots of stuff that I like and paste it in. And now I want to use FigJam for that, but the quality of the pasted images are too low. The pasted image is too pixelated (in Miro the image is super crisp).

Hi,As a half a decade long user of Figma, I always struggle to back track my design decisions during working on multiple projects or even during development hand-offs or knowledge transfers to other design peers. It’s crucial for designers because there could be multiple reasons that could have influenced why we chose a particular design/element/component in our designs. I tend to write text notes below my figma screens which is sometimes lost when moving things around and also the developers / PMs don’t tend to notice the message below the screen during implementation.I wish there was an easier way to add a note to each design element or a group of elements together and tag it as Dev note, PM note, etc so that my respective stakeholders can see those notes in the screen while reviewing (not like a comment but something that’s more intentional and doesn’t get lost/unseen). It would also help me to remember to write notes / questions while designing to clarify or a

What do you think about having a horizontal scroll on the layers panel? I can’t see the name of the layers and usually widen the panel to be able to see, but since I use a 13", this makes the canvas smaller.

I often create small graphics in Figma for my company’s communications and website. We use a lot of custom drop shadows and glows and it would be much more efficient if I was able to just copy and paste the settings of the drop shadow on one element to another. Or at least the ability to save a custom drop shadow in your library similar to how you can with gradients. This would be a huge timesaver, thanks!

Hello,I need the ability to the hex code on my color variables when I am applying them to my components. I’m using Material Color Tokens for naming so it is not obvious what the color is based on the name.

It would be great to have quick-access aspect ratio presets (like 1:1, 3:2, 4:3, 16:9, etc.) when working with the rectangle or frame tools in Figma.How it works:While designing a website or app, I often use image ratios like 3:2, 1:1, or 19:9. If my image has a width of 1024 px, it would be great to just pick a ratio like 3:2 from a dropdown, and Figma sets the right height automatically — no need to calculate it myself.Example interaction:Select a rectangle with 296 × 170 px → choose 3:2 → Figma adjusts it to 2

i u’d love to see Figma provide a way for companies or organizations to officially submit and add their own shape kits, icons, or templates directly into the FigJam “More Shapes” sidebar—alongside AWS, Google Cloud, and similar resources. This would allow teams to streamline diagramming with organization-specific diagrams available instantly. At present, only core libraries curated by Figma are available there, so extra shapes need to be imported as templates or community files. Can Figma build a model or submission process for partners or trusted orgs to add resources to the sidebar natively? This would hugely benefit larger teams and anyone diagramming with standards unique to their work.

TLDR - Variables in editor should indicate they are stored in an external file. When using Variables in conditional statements or setVariable the UI elements don’t completely nor clearly display the context of the variable, such as which file its being referenced from, or its full path. Basically, it looks like you shorten the full path of the variable. As such when using variables that are deeply nested in the Collection, it becomes impossible to see that. This creates an issue if you use the same variable name within nested groups in a collection. For example `/Collection/Group-1/Count` becomes `Count`. As such, if you have `/Collection/Group-2/count` it becomes impossible to know which Count variale you are using. THis forces you to name variable count_1, count_2 etc. Also, If i make the mistake of creating a copying a component from one figma file with variables to another figma file, (without the variables). Then the component