Suggest a Feature

Hi everyone,I’m running into a strange shortcut behavior difference between my work and personal Figma accounts. Platform: macOS (Turkish-Q keyboard) App: Figma Desktop + Web (tested both) Mode: Design mode, Move tool active, not in Prototype etc. Issue: In my personal account, pressing ⌥ + ⌘ + ↑/↓ rotates the selected object. In my work account, on the exact same device and setup, the same shortcut correctly changes the layer order.  What I’ve tried (none fixed it): Cleared Figma cache (~/Library/Application Support/Figma) Removed and re-added both accounts The behavior persists only in my personal account, even in the web app. Switched keyboard layout between Turkish-Q and English (US) Disabled all plugins Tested in both Desktop and Web app Confirmed Move tool is selected and Prototype/Dev/Draw modes are off I’m stuck right now how to resolve this issue. I need a help.Thanks in advance!

AVIF is already supported by Chrome and Firefox and Safari. It would be good to also have animated AVIF supported for prototypes the same way that gifs play when viewing a prototype.

Hi, I’m not sure if this is new since the May update, but I wonder why “empty” (all elements hidden) Auto Layout Frames keep the size of the last hidden child (and I do not mean last in the list, but the last element to have been toggled out of view by the user), making them not-0px high even with nothing in them. See here a file with a Frame with three hidden rectangle: the Frame keeps the size of the last child rectangle to have been hidden. When adding a 0-px Frame to the AL frame, and toggling this 0-px Frame off last, the container goes 0-px. In my opinion, empty AL Frames should have a height of 0. What do you think?

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

Hi everyone,I often run into an issue when creating components: I want certain properties to be mutually exclusive.For example, inside a component (most of the time it’s a product card), I have Block A, Block B, and Block C, each controlled by a boolean toggle. If I want to switch from A to B, I have to manually turn B on and A off. This quickly becomes tedious, especially with multiple options.While variants are an alternative, they become impractical when dealing with many of this mutually exclusive choices, and they add too much complexity and file size.Conditional logic could also work for this but it is such a pain to do for this simple and recurent use case that I consider it as not a viable option for a day-to-day workflow. Feature Idea:It would be great to group boolean properties so only one can be active at a time—like a set of radio buttons instead of multiple independent toggles.Would this help your workflow too? What do you think?

Hi to all. I love to use Figma to make prototype but i think that it’s time to improve dev mode and show html+css code about components. Especially if the compponents were made using autolayout. I know that there’s some plugin but i think Figma have to improve this side. What do you think about it?

HeyIt would be great if we have repeat functionality in design mode too not just in draw mode.Thanks

HeyI’m currently using FigJam connectors by copying and pasting them, but it would be much better to have a native version available in Design mode. Also, connectors can’t currently be turned into components or placed inside components, so it would be great if that could be considered as well.

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.

Currently there is a huge limitation in prototyping possibilities because any dropdown menus appear underneath the following element in the autolayout flow. I can’t remove autolayout because it would break designs across all useage of design system components and we can’t properly demo prototypes. Anchored by the lack of a customizable z-index property.

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.

It would be a great idea to add the ability to move annotations (сhanging the place). Right now, they’re fixed in place and can overlap other elements. And you cannot change it.What I mean is the ability to reposition an annotation freely while keeping the link to the target object intact.Annotations are a really useful feature—thank you! Previously, I had to create similar functionality using my own objects. Please do not move this offer to another discussion. 🙏Can we move the Figma Annotations (in dev mode) from one Figma project to another?These are different questions.

Organization would be immensely helpful if we could create folders for our drafts. I want to be able to organize my drafts into different categories (such as UI kits, Ideas, Wireframe kits, iOS, Android, etc…) so I can find files easily. Right now, the drafts page is a huge jumbled mess and I can’t create Team pages for everything. Maybe something as simple as being able to add ‘tags’ to each file, similar to Zeplin.

These are new and improved color formats that replace hex and rgb. They will soon become the standard in web browsers. They open up more colors than are currently possible. The Expanding Gamut of Color on the Web | CSS-Tricks - CSS-Tricks

I would love to see when someone has made a change to a file as well. It would help me be able to identify if people make optimal use of their licence, as well as use the log if my org has suspicions someone isn’t working. Alternatively this might be solved by being able to download the textual version history of a file, but inside the activity log would make more sense in my eyes.

It would be nice if I could quickly open pages in my design file in a new tab. Often pages contain designs that would be useful to view side by side with the current page you are working on. It would be nice if I could quickly open them in a new tab / new window instead of having to go back to files, open the file, wait for it to load and then navigate to the page.

Currently, using Figma component boolean properties, it only shows when true and hides when false. What if you could switch those around? For example, when something is true, it could show some elements, and hide others. For example, a product thumbnail- when “on sale” is true, show sale icon, show strikethrough price, but also hide original price and replace it with a bolded/colorful/what have you of price. Or if ‘Out of Stock’ is true, show all the ‘out of stock’ stuff material, but also hide the ‘add to cart’ button. Stuff like that. Currently you have to create new variants just to show + hide things at the same time, or add redundant switches like ‘In Stock’ and ‘Out of Stock’ and just make sure they never have the same state.

We just opted in for 2 seats on the professional plan.  We find it disappointing that we can’t monitor our remaining AI credits.We have no idea how many credits we used yesterday, and have no sense at all of how much we can accomplish with the credits we purchased.The AI itself has been very impressive.  To obfuscate the AI credits to this degree is a big disservice to your users. 

It would be great if the professional plan offered more than 4 variable modes. Right now I want to set up a mode for each component size-- XS - XL, 5 sizes all together-- which puts me over the 4 limit for pro, but well under the 40 limit for enterprise, which is a quantity I will never need. And there’s no use case for enterprise at all for a team our size. I think 10-12 modes for pro would be perfect to give small teams like mine room to grow before we reach the scale where an enterprise plan would be worth consideration.

I’d like to insert an image into a cell in a table in FigJam so that it moves with the table as it expands and changes size. Currently, I’m just having to drag pictures around with the table as it expands which is fine for one or two images but I have many!

DEV mode is useful for getting pixel-perfect implementation, but the problem occurs when we try to implement animations, as then developers need to eyeball the animation curves and durations, or record screen and review frame by frame, impacting effectiveness. It would be very useful to analyse or view animation information so implementation work would be smoother.

Hi All, we currently use the swap library feature for our styles. We were wondering tho if there is going to be support for swapping variables in the future as well? I know that Figma is currently working on extended collections, but the current omission of swapping variables based on a different library seems a bit weird

Hello Figma Support Team,I have been using the new Figma Make AI feature to generate designs, but I am unable to connect these files to Bravo Studio (and other third-party integrations) because: The files created via Make AI are saved as /make/ links, even after moving or duplicating them into my team/project. Bravo Studio (and most Figma plugins or APIs) require a /file/ URL to recognize and import the design. Even after attempting to move, duplicate, or export/import the file within the team/project, the file remains stuck as a /make/ link, not a /file/ link. This severely limits the usability of Make AI-generated designs in any real-world development or handoff workflow.Steps to reproduce: Generate a new design using Figma Make AI. Move or duplicate the file into a Team or Project (on Starter/free plan). Right-click and “Copy link” – link is always in /make/ format, never /file/. Try to use the link in Bravo Studio – receives “file not found or no permission” error. Expect