Suggest a Feature

In the left-side panel, the pages and layers panels are separated by a single-pixel-thick line. This line is draggable so as to resize the vertical height of the panels.This is incredibly small, and there is almost no affordance to understand this is draggable. To compound the confusion, the flat design offers no indication that these panels may contain more pages/layers (e.g. a fade out of the pages’ names at the bottom of the panel).Finally, why does collapsing the layers panel not reduce its height, like the collapsible panels of Adobe’s apps? it seems like there is no purpose to this collapse, since it does not reveal the full list of pages.This problem is quite annoying when we share our work with stakeholders and collaborators (e.g. copywriters and project managers) that are not familiar with the idiosyncrasies of Figma, and are wondering where all the pages go.Please find a solution to clarify that these panels contain potentially more than they reveal, and that this thin line i

The new preview window in Figma client is great! It would be nice if this could be moved freely outside the window size of the Figma client. This way it would not obstruct the Figma UI and can be moved to a secondary display.

I do accidentally move around comments by mistake. And whenever I cmd-z I accidentally undo the designs rather than comment move.

Hi, in both of my organizations, I use Figma for designs, and my devs are used to it, know how to navigate and adopted it very well. But when I get files from other colleagues outside of my organization, I usually get .ai or .psd files and I can’t open them. I would like Figma (not community that is extra pay and mostly does not even do the job) being able to let me work with these files.The question is, can Figma team work on that?It would be soooo much more helpful than things like Figma Make, because this thing makes me leave Figma and use Adobe instead.  

Add the option to put a password on the page in the file. This is very necessary when you are working on a product and part of the development team temporarily should not have access to one page, but should have access to other pages in the file.

Please allow developers to add annotations directly in Dev Mode to capture technical notes and implementation details. This would make it easier to document decisions, track clarifications, and maintain context during development, all without leaving Figma.

Hi Figma Team,Please update the default Arabic font in FigJam, the current default font sucks.I recommend using one of these Google Fonts instead:TajawalIBM Plex Sans ArabicEven Lovable understood this and chose Tajawal as their default Arabic font.

Our corporate entity requires we use the Microsoft suite, so a Loop widget would be extremely helpful to have for our FigJam collabs with product.

Our organization is growing, and as result we are letting more and more folks into Figma. This is becoming increasingly difficult to manage.I would love to see some updates added to the people page to be able to manage users more effectively.One idea is to just add a “tags” column. This would be sufficient for my needs.Need:I want to be able to know what department/role a user belongs to in my organization so that I can ensure everyone has the right access based on their specific department/role.I imagine that I am not the only one with this issue, not sure how other people that are operating at a larger scale are currently handling this.My current workaround, which is terrible. Is to open up rippling in one view, and Figma in the other and compare individuals across tools to understand what access they need.

During client presentations, we typically showcase the prototype and capture feedback through comments added directly on it. However, while implementing these changes, we observed that the comments move along as the prototype is scrolled. This makes it difficult to accurately track which comment corresponds to which element.It would be highly beneficial if the comments remained anchored to their respective positions on the prototype, rather than scrolling with the frame. This enhancement would ensure better clarity and efficiency during the review and implementation process.

Can we have an option stop syncing while in view only mode at least? I don’t need the latest version all the time for visualization and to keep loading every time I focus back on the tab is very annoying.I’m keeping it in offline mode for now by using dev tools to prevent loading but something a bit smarter would be better.Reloading should be an optional action.

When presenting screens, we want to show the work within a phone. Right now we go to prototype mode, take screenshots of the prototypes, then remove the backgrounds in photoshop. Please let us export screens with the phone like it looks in a prototype, so we can add to slides. 

Hey Figma team, like a lot of design teams, we often add features over time.Sometimes, the feature adds are so large or disruptive to the current design that we need to overhaul it (and sometimes the project structure).Starting a new file is disruptive because we have a fair number of people who have relationships with the old file. Without a redirect function, getting all the stakeholders to find and start using the new file is an epic poem of a task.We want to minimize disruption to other stakeholders who may still need the older designs until the new one is agreed on and ready. The logical thing to do is work in a branch, right?The problem with this is that right now, branch merges require a complete review of conflicts - and this is a problem, because:I don’t want to review and merge conflicts one by one. I just want to completely overwrite main with my branch. Making me do this is the most unnecessary form of “are you sure” and takes forever. The merge tool has a stroke and basica

I’d love for there to be a way, when working with overlays/modals, to be able to close the overlay so that when it closes, the screen revealed upon closing is different from the original parent screen. For example, on mobile I have a bottom sheet menu from which I can select an icon that allows me to navigate to a new page. This isn’t the same as swapping overlays or navigating within overlays. It’s that an action from the overlay results in the parent screen (screen under the overlay) changing. I’m able to do this with Smart Animate with just the menu component, but when I want there to be a dark background to overlay the parent screen, that messes the animation up and the behavior isn’t as one would expect. The animation with the overlay feature is perfect, except that I can’t control which screen the overlay closes on to.

We sometimes link component to another component in another page.On desktop app, it will be very convenient if we can go back to previous page instead of having to look for the figma page we came from manually.

Apple's Universal Linking implementation is a robust and easy to implement way to open Mac Apps instead of their Web App counterparts.It's absolutely annoying to open a Figma link from any other tool and having to first open Chrome + a new Tab that will have to be manually closed when we already have an alternative that works so well. Please consider adding Universal Links to Figma.Here are the blueprints from Apple:https://developer.apple.com/documentation/xcode/supporting-universal-links-in-your-app

It would be great to have a quick way to copy the hex codes of the library colours. At the moment it’s three steps (click the colour > filter icon > copy hex code. Be great if it could be one click, especially with having to check colours for accessibility regularly.

I find it really frustrating to have to either hold the space button or toggle between the hand tool to move around on my board. Can you please include an option to let us hold the right mouse button to hover and move around on the board?

When I create a template, the template should CLEAR the conversation thread for all users, including me, the owner. When creating a template, it would be nice to have a checkbox where I could say “clear conversation thread for everyone”.

Videos can autoplay once you’re on a slide instantly but doing multiple elements that sequentially animate seems to require two clicks to get the first element to animate and trigger the rest. It makes it tricky for presenting to know which slides are one click and which are two clicks. Please make it possible for first image element on page to auto appear (without using smart animate) and trigger the rest of the elements. 

My prototypes have a lot of animations which my Macbook Pro has no problem rendering when I present from my computer; however, many of my non-designer colleagues don’t have the same luxury of a good graphics card on their computers, causing my prototype to run very slowly when they ‘re demoing my prototype to other teams.  Rather than maintain two prototypes or worse, manually disable the transitions I set for my prototype and undo all the work I did so that it’s playable by under powered computers, it would be helpful to have a setting in presenter mode to toggle animations on and off. A good example would be like modern video game consoles having performance and fidelity modes. The former optimizes frame rate at the cost of fidelity, where the latter optimizes for resolution with a fixed lower frame rate. In the context of Figma, all animated transitions could be toggled to play as “instant” in “Performance” mode but could be easily turned back on to see the prototype as it was fully

My team needs to review all UI copy. That copy goes into a library so we can be consistent across the product. I’m trying to review and update the copy in Figma Make. However, it’s impossible to extract the reviewed copy so I can add it to the library. A separate file in code view would not only make it easier to review and make sure we haven’t missed anything (even if we then have to update the .tsx file also) but also have that record.

While working with complex prototypes, I see the following features are missing: Management of a local database for components. Copy/paste of created components (e.g., File.tsx) between pages. See all created pages and easily navigate between them. Identify where an element is a component versus hardcoded with the same appearance. Configure component properties.

I wish I could zoom the Figma UI without also zooming the canvas. That is all.

Hey there! 👋 It always has bothered me that Figma’s general UI is slightly too tiny / has very small font sizes and I hoped that View>Interface Scale would solve this issue. Figma’s small font size and icon size make it quite difficult to navigate through the app without having hawk eyes. Sometimes elements (especially in Effects menu) are small click targets. Scaling the Interface up seems like a good idea to counter this and improve readability and clickability. Unfortunately at this rate, it’s not a real solution for me. It is pretty much useless to me since it also scales your designs / the canvas. I’d like to scale the UI (Sidebars, Top Bar) only and keep my design canvas untouched to remain at an actual 100% scale. The current behaviour doesn’t make much sense to me. If I’m designing for example a screen at 1920px width I’d like to see an actual 1920px screen. My work depends on the canvas representing the pixels at 1:1 / @1x scale. Sure, a workaround could be to view