Skip to main content

Cmd+alt+up/down recently started to rotate object instead of moving the layer up down.

How to fix/disable it?

This is so fucking annoying and stupid I don’t know where to begin. Yet another unbelievable move by Figma that just keeps getting worse.

  1. There is NO WAY rotate +-1° is used more often than Bring forward/Send backward. So why not just create a new shortcut for rotate, instead of “stealing” an already used one?!?!?!
  2. Using up/down arrows for rotating left/right makes no sense whatsoever. 🤯
  3. You say users can now use Cmd+[ to Bring forward/Send backward, but guess what – for people with non-English keyboards (like myself and probably 10000 millions others) this doesn’t work. 🤡
  4. In your “Keyboard shortcuts” settings, why can’t I just create my own shortcuts in the first place? How is that for accessibility?!
  5. I’ve tried to override this stupid change by going to my MacBook’s keyboard shortcut settings and assign Cmd+Alt+Up/Down to send layers forward/backward, and in the Figma “Object” menu it looks like the change has been confirmed, but nope! Still rotates.

You say you do these changes to “to make Figma easier to navigate for all” which is completely nonsense. You’re making it HARDER for a MAJORITY. I’m betting my right arm you’re damaging more people’s workflow by this change than helping those with screen readers, which you say is the reason for this change.


Please bring back the old shortcut. Working with a non us keyboard layout makes the new shortcut ridiculous to press for such a common interaction. I almost never rotate anything in figma, but I move layers by the minute.. 


@Tom Reem what if you unmap all the shortcuts from the alt+cmd+up/down? It allows the solution ​@David Samuelson to work. So the users who want to move layers could map their preferred shortcut, and the users who prefer to rotate could rotate.

That would be the real accessibility.


Shortcut is BACK for me.
GJ Figma for listening to your userbase.

EDIT: Nvm.. scratch that. it was a bug I think.