Hi everyone,I’m running into a strange shortcut behavior difference between my work and personal Figma accounts. Platform: macOS (Turkish-Q keyboard) App: Figma Desktop + Web (tested both) Mode: Design mode, Move tool active, not in Prototype etc. Issue: In my personal account, pressing ⌥ + ⌘ + ↑/↓ rotates the selected object. In my work account, on the exact same device and setup, the same shortcut correctly changes the layer order. What I’ve tried (none fixed it): Cleared Figma cache (~/Library/Application Support/Figma) Removed and re-added both accounts The behavior persists only in my personal account, even in the web app. Switched keyboard layout between Turkish-Q and English (US) Disabled all plugins Tested in both Desktop and Web app Confirmed Move tool is selected and Prototype/Dev/Draw modes are off I’m stuck right now how to resolve this issue. I need a help.Thanks in advance!

enesates

New Member

Question

Shortcut Option + Command + Up/Down rotates objects instead of moving layer order

Forum|Forum|11 months ago
October 14, 2025
16 replies
893 views

Hi everyone,

I’m running into a strange shortcut behavior difference between my work and personal Figma accounts.

Platform: macOS (Turkish-Q keyboard)
App: Figma Desktop + Web (tested both)
Mode: Design mode, Move tool active, not in Prototype etc.
Issue: In my personal account, pressing ⌥ + ⌘ + ↑/↓ rotates the selected object. In my work account, on the exact same device and setup, the same shortcut correctly changes the layer order.

What I’ve tried (none fixed it):

Cleared Figma cache (~/Library/Application Support/Figma)
Removed and re-added both accounts
The behavior persists only in my personal account, even in the web app.
Switched keyboard layout between Turkish-Q and English (US)
Disabled all plugins
Tested in both Desktop and Web app
Confirmed Move tool is selected and Prototype/Dev/Draw modes are off

I’m stuck right now how to resolve this issue. I need a help.

Thanks in advance!

Show previous replies

Shaked

New Participant

Hey All, thank you for your feedback!

We completely understand how unexpected changes like this can be frustrating, especially when they disrupt your current workflow. I’ve updated this topic into a feature request and sent your feedback with our product team to ensure they’re aware of how these updates are now affecting your workflow. This is helpful for us to better understand the issue and evaluate next steps.

We’ll continue monitoring this thread and keep the feedback loop open with the product team. In the meantime, the new keyboard shortcuts for this: Cmd/Ctrl + ] and Cmd/Ctrl + [ will allow you to reorder layers

Lastly, we plan to keep the Accessibility at Figma article in Figma Learn updated as new information and shortcuts become available. Thanks again for your understanding and for taking the time to surface this.

Why there’s complete silence from the product team? can we get answers? or at least, an OPTION to choose from?

djv

Community Support

Hey @Shaked,

The reply I originally sent on November 3rd was from the product team, and this is still something they’re proactively working to improve since it launched last month.

Again, our product team made this update as part of ongoing efforts to improve accessibility and streamline shortcut usage across Figma. We know this particular change was unexpected and may have disrupted some established workflows, and we’re sorry for that. The team did review how the shortcut was being used, what was documented, and explored alternatives (including a modal), but we recognize that the transition could have been communicated and supported better.

While this update was shared in advance with our Friends of Figma community, we understand that not specifying the exact remapping caused some confusion. We’ve shared this feedback internally to ensure we communicate future shortcut updates more clearly and directly with our Design Accessibility community.

To help ease the transition, users will now see a toast message explaining the change and linking to more information when using the previous shortcut. You can continue to reorder layers using Cmd/Ctrl + ] and Cmd/Ctrl + [, or you can also adjust your keyboard layout to better match your preferred setup.

Feedback like this is incredibly valuable in helping the team decide what to improve next — including discussions around custom keyboard shortcuts. Thanks again for your thoughtful input and for helping make Figma more accessible for everyone.

Flo_Sebald1

New Member

Hey @Shaked,

The reply I originally sent on November 3rd was from the product team, and this is still something they’re proactively working to improve since it launched last month.

Again, our product team made this update as part of ongoing efforts to improve accessibility and streamline shortcut usage across Figma. We know this particular change was unexpected and may have disrupted some established workflows, and we’re sorry for that. The team did review how the shortcut was being used, what was documented, and explored alternatives (including a modal), but we recognize that the transition could have been communicated and supported better.

While this update was shared in advance with our Friends of Figma community, we understand that not specifying the exact remapping caused some confusion. We’ve shared this feedback internally to ensure we communicate future shortcut updates more clearly and directly with our Design Accessibility community.

To help ease the transition, users will now see a toast message explaining the change and linking to more information when using the previous shortcut. You can continue to reorder layers using Cmd/Ctrl + ] and Cmd/Ctrl + [, or you can also adjust your keyboard layout to better match your preferred setup.

Feedback like this is incredibly valuable in helping the team decide what to improve next — including discussions around custom keyboard shortcuts. Thanks again for your thoughtful input and for helping make Figma more accessible for everyone.

So what you are saying is that there will be no option to revert the change and that anyone using a non US keyboard is expected to f off and switch hardware? Do you understand how unreasonable that is, especially for an accessibility feature. On many non US keyboards it is physically impossible to press the shortcut involving the bracket keys.