Share Your Thoughts

The pink dashed selection box (keyboard navigation focus indicator) appears when pressing Tab on the canvas. It often gets stuck and disrupts the design workflow. There is no option to disable or hide it permanently.Please add a toggle in Preferences to disable the keyboard focus highlight for users who don’t need it. This would help keep the canvas clean and avoid accidental activations.

When you have a number of identical (or comparable) elements and they haven’t already been made into a component, it would be great to be able to:Select each element individually (e.g., a banner within a series of mocked screens) Add these selections into a pile/group within the left or right sidebar Choose one “exemplar” to represent the group Create & replace each selection in place within each frame/screen with a component created from the exemplar(4) could leverage the same UI as Library updates, where you can review each new instance as compared to its current state before confirming its update. 

I would like to have ability to animate overlay in/out animation with more variety of interesting or existing animation that could enhance prototyping experience.

While Figma doesn’t have a built-in URL shortener, so, we currently use external tools, like browser extensions or third-party appsBy adding this feature, we can easily share Figma designs and prototypes with others via shortened URLs.I noticed this feature in google form. while sharing google form link to user for submitting . google form gives 2 option LONG URL or you can Short your Url itself. so, I think if figma will add this feature while sharing prototype long URLs to short url. So, it will impact many users and process will be smooth . beacuse final output url will be short and shown as great 

I would love it if notes were presented as element boxes below the rows of slides. That way I can see the big picture while working on the slides.   

I know there are (paid) plugins that will convert code to Figma files, but I wish this was a feature that Figma could do natively. I think there’s an area that Figma feels natural for and that’s helping to bridge the gap between design and development. And I know, yes, there’s Dev Mode. But imagine if, for example:You could connect to your Storybook account, and your components port through to Figma. The design file in Figma stays up to date, even when designs slightly change between design and go-live (design drift). And again, I know there is a plugin that does specifically this, but for small scrappy teams it just isn’t feasible to pay hundreds of dollars a month for something like this. Feels like a no-brainer.

Please consider supporting code generation in Figma Make using frameworks like Vite, Angular, or Vue, especially since Create React App (CRA) is being sunset. These alternatives are more modern, actively maintained, and better aligned with current frontend development practices. A similar feature request for Angular support was already suggested here:  

I’d like to be able to see applied variables on connection lines and also connection lines caused by conditionalsI am currently building a complex online form with 30+ variables, but debugging this becomes cumbersome if I can’t see where I have set variables. 

The “Tool bar” should be in the upper left of the screen. Personally, I’d expect to find a “Tools” menu near the Min menu, or where I’d see the File/Edit/View/Object… menus. In the bottom center, it overlaps design elements, so designing and walking through designs via screenshare is clunky and awkward. The “floating panel” aspect looks neat, but it’s still a visual obstruction in the center of the workspace. In my opinion, it just renders the bottom 50ish pixels of the workspace useless.Also, Mac users will keep accidentally triggering the bottom drawer.Toolbar 

Hi, I came across a similar idea - Search results are not precise - we get 'similar words' instead of exact match but unfortunately in Figma still missing. I think the exact search by name is a “must have”. Furthermore, it would be very useful if it were possible to find instances of a specific component, according to the specified properties. I think both functions are quite essential for keeping documents in order. Do you plan to add them please?

The New UI changed the keyboard shortcut for creating a link in text. Command+K is the universal keyboard shortcut for adding a link and changing it to shift+command+U severely slows down my workflow. For many designers and copywriters, command+K is muscle memory, and swapping this adds unnecessary confusion. Can you please change the keyboard shortcut back, or allow users to customize their shortcuts? Switching any keyboard shortcuts out is extremely frustrating to designers who rely on using them to save time in their daily workflow.

When reviewing designs with developers I’m often referencing the layout grid I’m using in the designs, but if the developer has ‘view only’ access they are unable to see the layout grid in the inspect tool. We have been trying to limit edit access to only designers as we have many developers (30+) inspecting our files. I’d love it if the layout grid was viewable in ‘View Only’ mode in the inspect tool 🙂 It would help bridge the gap between developers and designers even more 🙂

As a system analyst, I often walk others through design files to confirm specifications or gather feedback—whether it’s with clients, internal teams, or stakeholders. In Axure, I’m used to having a fixed notes panel on the side—so I can present the screens on the right while referring to key talking points or structured notes on the left (Axure screenshot attached).This setup has been incredibly helpful during presentations or walkthroughs. It keeps the discussion organized and lets me stay on track without jumping back and forth or losing context.But in Figma, I constantly find myself dragging the screen around just to switch between designs and notes. Not only does it interrupt my own focus, but it also makes it harder for others to follow along, especially when the screen keeps shifting back and forth. It can be visually tiring and distracting for everyone involved, making the whole session feel less smooth and less clear. I truly believe a fixed or detachable notes panel would be a

Our design system has many components that can’t be edited beyond what is available in the props list. In the past, we generally enabled the “simplify all instances” option for these types of components (things like icons, checkboxes, switches, etc.). With the latest UI, “simplify all instances” hides the alignment features within the Position section of the design panel by default, which means any designer wanting to align one of these components within their design must first un-hide additional properties. It seems to me that a component’s alignment to other components shouldn’t be an “additional property” — positioning components within a layout is the first thing we do, and doesn’t involve editing the component itself. As a result, we’ve had to disable the “simplify” option across the board to make things easier for designers. This means displaying extra layers unnecessarily.

Multiple tools focusing on retrospective meetings allows to control visibility of text written on stickies, see example from metroretro.io, each user is able to control visibility of their own stickies. It’s extremely practical functionality which seems to be missing in FigJam (i wasn’t able to find any plugin/widget addressing this functionality) are you planning to implement something covering this need? Example

Feature Name: PagesDescription: Introduce a "Pages" feature within Figma Buzz files, allowing users to create and navigate between multiple distinct pages within a single document. Each page would function as a separate canvas for content, behaving similarly to pages in Figma Design files or FigJam files.Core Functionality: Add/Delete Pages: A simple interface to add new blank pages and delete existing ones. Page Navigation: A clear sidebar or dropdown menu to easily switch between pages. Page Naming/Renaming: Ability to name and rename pages for better organization. Content Isolation: Content on one page should not interfere with or be directly visible on other pages, maintaining distinct, independent workspaces. Benefits:Adding "Pages" to Figma Buzz would significantly enhance organization, collaboration, and content planning capabilities, offering several key benefits: Improved Performance on Low-Hardware Devices: By segmenting content across multiple pages, Figma Buzz would o

We propose a powerful new set of AI-driven features for FigJam, extending beyond the mind map functionality to enhance all collaborative workflows, including chart creation and more.Key Features: Contextual AI Prompts (as shown in image): Integrate AI directly into text elements across FigJam, similar to the "Any question or topic" prompt in mind maps, offering intelligent suggestions and expansions like "An idea" or "A thought." This should be available for all features (e.g., sticky notes, shapes, and text within charts). AI Model Selection Support: Allow users to choose specific AI models for processing within FigJam, providing flexibility and control over the AI's output. Content Control for AI Processing: Implement granular control over what content the AI processes. This includes: Process Selection: The ability to select specific elements or areas for AI processing. Skip Page/Section: Options to exclude certain pages or sections from AI analysis. Benefits:With these

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 penalizes the very users who are pushing the

 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.

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.

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

Properties propagation is necessary to build and maintain a flexible, modular, and dynamic design systems.For example, I’m building a TableCell component in my design system, which should support inline editing. I’d like to crate a Value property on the TableCell master component, so both states (View | Edit) retain this value when switched. I’ll use different components to render out the cell value:View mode - Typography (text) component Edit mode - TextField (input) componentI can’t implement this, unfortunately, due to the limitation described in this thread, so I have a few options:Use nested instances and lose the ability to propagate the master component (TableCell) Value property to the child instances (Typography, TextField), so once the state is changed, overrides (Value) are lost, and should be re-entered (manually) for each of the component states.   Don’t use nested instances and instead put detached versions of them. In that case, I’ll need to re-implement a lot of additio