Suggest a Feature

When an active branch is open, making the main branch read-only can help prevent accidental changes to the main file. This would reduce the chances of someone (like myself) mistakenly editing the main branch when they meant to be working in a separate branch. Sometimes I don’t even realize I’m still on the main branch until after making changes—this feature would help avoid that confusion.

Issue:Currently, the Community tab automatically closes when switching to another tab, and the app does not save the last viewed state for the next access. I can’t see the pin tab function in the action menu of this tab  Can not find the pin action 

I get so many bogus requests for Dev seats from our team members who accidentally click the request button because of how it is placed in the UI.It is very annoying. Could you please make it so that once a request is denied a member can’t re-request Dev seat?

It would be a big time saver to preserve the style and formatting of a text layer, when copying and pasting it from one file to another file. Right now the paste operation loses all formatting and I have to re-format the text all over again.

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.

Hey y’all,  Who votes for the calc() - feature ?It’d solve a whole bunch of tiresome workarounds, such as :Line-height and widths on all kind of stuff, but for me it’d be really cool to have the grid working in percentage…  What are your thoughts? 

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 

Hello Figma team,First of all, thank you for your great work on Figma — it has truly transformed the design workflow for many of us.I’d like to request RTL (Right-to-Left) support for the Wrap feature in Auto Layout.Currently, when using Auto Layout with horizontal direction and Wrap enabled, the elements are wrapped from left to right, which works perfectly for LTR languages.However, when designing interfaces in RTL languages like Arabic, Persian, this behavior causes layout issues. In RTL layouts, the natural expectation is for the second line to wrap from the right, not from the left — but this is currently not possible.Although reversing the order of elements helps with initial alignment, it does not fix the direction of wrapping, which leads to awkward designs and manual workarounds.Adding RTL-aware wrapping logic in Auto Layout would be a huge improvement for designers working in RTL en

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?

I'm excited for Bulk Create in Figma Buzz. It’s a lot more intuitive for our marketers to use, but at its current stage it’s actually more time consuming than our existing workflow, mainly because it doesn’t have the ability to bulk rename frames or the exported filenames. That means we still end up having to manually rename "Frame1.png" all the way to "Frame175.png".Here’s our use case: we need to create OpenGraph images for a website with over a hundred pages. We have two design templates: one with page title only, one with page title and a subhead.Currently, the marketing & web dev team maintain a spreadsheet of all the pages currently exist.We have the 2 designs set up as components and use a plugin called Scribe - Dynamic data in seconds to pull in the CSV and use a column we choose for naming the frames / files.I can see Bulk Create doing this as well, and even adding some common renaming & conditional naming option

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

Maybe on confused on how the feature works. If the team is using for ideation and keeping the master branch clean for devs and clients. When it comes time to push elements from a branch to the master file, currently it pushes the entire branch. This is pointless. We don’t want all the ideation, all the options, all the throw away work, just the version that we moved forward with. Currently we need to make a new branch we call “to be merged” and we need to copy just the artboards that are approved into the new branch then merge from there. This feels like to many steps and is complicated on a team of 4 designers. Shouldn’t there be an option to select just the artboards, components, styles, etc that we want to bring forward and leave all the other work in the archived branch incase we need to go back and grab something from it in the future? Pushing everything makes the feature feel useless because you’re either deleting all your ideation or creating “merge” branches to ma

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 dis

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. Thi

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