Rectangle on Non-US Keyboards: Known Layout Issues and Fixes
Rectangle app‘s default shortcuts are defined around a US QWERTY layout — ⌃⌥D for first-third, ⌃⌥U for top-left, and so on, chosen for their mnemonic value on that specific layout. On a different physical or logical keyboard layout, a handful of specific, documented problems can show up. None of these are exotic edge cases; they’re real reports on the project’s own GitHub issue tracker.
Shortcuts changing when you switch input layout
Issue #1464, filed on Rectangle mac 0.83 against macOS 14.6.1, describes shortcuts changing behavior when the user switches between keyboard input layouts (for instance, between a US layout and a different regional one) on the same physical keyboard. This is distinct from a shortcut simply not firing — it’s the assigned action appearing to shift when the active input source changes mid-session. If you regularly switch input languages rather than sticking to one, this is worth checking against the issue’s current status before assuming your configuration is at fault.
The Globe/Fn key: display and function mismatch
Issue #1605, filed on Rectangle app 0.87 against macOS Sequoia 15.5, documents a specific problem with the Globe/Fn key as a shortcut modifier: the symbol shown in Rectangle’s shortcut field doesn’t always match what’s actually configured, and in some cases the shortcut doesn’t fire at all despite appearing set. The reporter notes this happened with all of macOS’s own Fn-based window shortcuts disabled in System Settings → Keyboard Shortcuts → Windows first — ruling out the most obvious cause (a conflict with a native macOS Fn shortcut) before filing. If you’re trying to bind a shortcut using the Globe key specifically — common on newer Mac keyboards that replaced a dedicated Fn key — and it isn’t behaving as displayed, this is a known report to check rather than a sign of a broken installation.
Defaults appearing already changed on a fresh install
Issue #1392 describes a user installing Rectangle fresh and finding Maximize bound to ⌘⌥F instead of the documented default ⌃⌥↩, with no obvious way to switch back to what the README describes as standard. This is a useful reminder that “the default shortcut” can depend on choices made during first launch (the Rectangle-vs-Spectacle-compatible prompt) or on a previous configuration file being picked up — if your bindings don’t match this article’s reference tables from the start, check Settings → Import for a leftover config file before assuming the documented defaults are wrong.
What actually causes most of this: US-centric mnemonic design
Rectangle’s shortcut scheme is built around mnemonics that work on a US QWERTY layout — U for upper-left, C for center, D/F/G sitting together on the home row for thirds. On a different physical layout (AZERTY, for instance, where key positions shift relative to US QWERTY), the letters Rectangle expects are still what’s bound, but their physical position on the keyboard moves, which can make the mnemonic logic stop making intuitive sense even when the shortcut technically still works. This isn’t a bug so much as a design assumption that doesn’t universally translate — worth knowing before concluding something is broken when it’s actually just positioned differently on your specific keyboard.
Practical steps if shortcuts misbehave on your layout
- Check the shortcut is actually being interpreted the way you expect by testing the same action from Rectangle’s menu bar item instead of the keyboard. If the menu action works and the shortcut doesn’t, the issue is specifically in how macOS is interpreting your key combination on your layout, not in Rectangle’s window-moving logic.
- Rebind rather than fight the default. If a specific letter’s physical position bothers you on your layout, there’s nothing forcing you to keep Rectangle’s mnemonic scheme — reassign any action to whatever physical key makes sense on your keyboard in the preferences window.
- Search the exact symptom on the issue tracker before assuming it’s unique to you — layout-related reports, especially involving the Globe/Fn key or input-source switching, come up periodically and may already have a maintainer response or workaround.
- Note your macOS version and Rectangle version when comparing to any report, including the ones cited here — several are tied to specific version combinations, and layout-handling code can change between releases.
The reliable fallback
If shortcut-based actions on your specific layout keep being unreliable, Rectangle’s snap areas (drag a window to a screen edge or corner) are layout-independent by nature — they respond to cursor position, not keyboard input, so none of the issues above apply to them. Falling back to drag-to-snap while you sort out a layout-specific shortcut quirk is a reasonable interim step rather than losing the tool’s functionality entirely.