Skip to main content

The main source of inspiration for this idea was to match the keyboard shortcuts themselves to different keyboard layouts. Right now, users who don’t use US keyboards have to memorize the location of the keys, rather than to use the actual character location to be able to use the shortcuts. Those involving this region are primarily the case:




ABNT2 layout (Brazil).


And here’s an example of confusing shortcuts:


image


Although this problem could be solved by just rebinding the shortcuts to the actual character and not the location on the keyboard, I’ve noticed there are some other issues concerning key bindings.


On this forum post, a member of the community asked for help on backing one layer level with a different shortcut from what Figma has right now. This makes the user adapt their workflow to the tool, and not the other way around — and that hinders efficiency. It would be nice if the tool itself provided some sort of customization on this regard.


Although being a workaround, Mac users can customize keyboard shortcuts by application, but it is a bit limited. It’s also not a possibility for Windows users.


I think this could be a game-changer, as i’ve seen people who refused to migrate from other tools to Figma because they couldn’t customize shortcuts. It would also give the user more control over the tool and their workflow.


What do you guys think about it?

How about it @Josh ? Ready to be legally compliant in Europe?


For windows users just use this for now, Clavier+. Lightweight and it has a simple UI not complicated like AutoHotKey.


And again I have to revert to old version because a huge project is messed up by opt + cmd + T and all text layers are center aligned and since I didn’t notice it before I can’t just undo…


PLEASE FIGMA FIX!!!


P.S. Same with shortcuts like “Bold”, “Quit” etc.

Why are they even there?


Ohgods that sounds terrible


And who at Figma decided: 1. That “T” makes sense for centering text? Like, nearly every other piece of software since MacWrite has used “C”. 2. Who else uses command-option for aligning text? The original keystrokes were command-shift, and then became just command (in word processors). The lack of adherence to existing norms is so flagrant across the keyboard shortcuts, it blows my mind every time.


And that is why we need to be able to customize them. Because so many of the shortcuts that Figma has invented are unique, and therefore, they are difficult to learn and get triggered by mistake.


I wish I could have Ctrl + C copy the image instead of the text in the image… I dont want to do Ctrl + Shift + C


This thread is almost 4 years old, and we still don’t have a way of customizing shortcuts? I keep hitting cmd+Q instead of cmd+A… there’s a big difference between quitting Figma and selecting all. FREE THE SHORTCUTS. its time!


Preach brother, free the shortcuts


I’m attempting to tailor the shortcuts to meet my workflow for greater efficiency. I use a lot of design software, and I have the same shortcuts in all of them. Therefore, it annoys me that Figma, despite being a great product, forbids users from making adaptations to match their daily work processes. Please allow us to personalize shortcuts. Right now, it’s difficult to utilize.


Another reason we need this, on Windows you can have applications that override/intercept shortcuts, which makes them unusable in Figma, so we need a way to change them in Figma to actually use them.


Hello!


I’m sure others have requested the ability to customize keyboard shortcuts in the past, but here’s one more reason why it’d be really nice to have it:


As many know, when you hit Cmd + B with one or more frames selected, it bold all of the text in those frames. I’ve occasionally done this without realizing it and continued on working for a while, only to then realize I’ve bolded everything and breaking my applied styles. I then have to either back out all of the work I did since that point, or re-apply all of my styles.


If I could change or disable that shortcut, it’d solve this problem for me!


Or maybe I should just always be working in branches?


Using apps like BetterTouchTool you can set Cmd + B to no action.


It would be very helpful if we could edit our own keyboard shortcuts for any item in the menus, now especially that the toolbar is now on the bottom of the page. Such as allowing us to set shortcuts for actions such as “Create multiple components” or “Set default properties”.


Premiere pro does it best IMO!



That may be good for seeing what shortcuts exist, but I find Adobe InDesign’s UX better for creating shortcuts. For example, you can select an item in a panel menu that does not have a shortcut and assign one to it. And also see what shortcut may exist for the item, as well as what feature may have your shortcut already assigned to it (see below). You can also show the set and search for any aspect of the shortcut — the key it uses, or the function.



A post was merged into an existing topic: UI3 – Feedback – Call me oldschool, but


I can’t believe they’ve overridden the universal Windows command for quitting an app and replaced it with the MacOS one. I’m not using a Mac, why do you force me to use Mac hotkeys?


BRILLIANT!!! I have been plagued by this for the past 2 years. You saved the day!


It’s cut off in the screenshot but the Premiere UI also has this functionality!


Lots of chat about shortcuts here 🙂 I’m a Figma user / Engineer. I built a product that helps you learn shortcuts in Figma (and other apps) faster. Pre-Release currently, but feedback has been good. Happy to share if folks are interested: https://reiden.ai/ ⌨️


How is this not solved yet…? Its been 4 years.


Hello Guy,

I appreciate your idea to help people learn the Figma shortcuts. But that is not addressing the vast majority of the issues described in this years old thread. The various needs for customization simply go far beyond merely memorizing them.


I really wish someone from Figma could just tell us where this stands. Like, near the top of being worked on? Is it being worked on? Q4 release? Q3 2025? What are some of the blockers (like, making it a true application?). Are there blockers? Why hasn’t this been done already? Why wasn’t it done in the first place? Why is it so challenging?


Simply answering many of those questions would go along way to alleviating the immense frustration of folks in this thread. 46,000 views is a lot!


This is reminiscent of what Adobe does: post ticket, Adobe resonds that it has been put on the backlog somewhere; sets ticket to solved. You don’t want to be Adobe, do you @Josh ?


How can this issue still not be solved! PLEASE SEND HELP !!!


“its not issue if its intended”


Reply