microsoft / microsoft/PowerToys
Inconsistent modifier key labeling in Command Palette / Keyboard Manager (⇧ symbol vs Ctrl/Alt text)
@niels9001 is already working on this.
Since May 12, 2026.
- Dominant language
- C
- Stars
- 139k
- Forks
- 8.6k
- PR merge metrics
- PR metrics pending
Description
## Summary
The shortcut display in PowerToys (Command Palette and Keyboard Manager) mixes Unicode key symbols with text labels, which is confusing for Windows users.
Example display: `[Win] [Ctrl] [⇧] [P]`
- `Win` → icon (⊞)
- `Ctrl` → text
- `Shift` → Unicode symbol (⇧, U+21E7)
- `P` → text
## Problem
Most physical Windows keyboards label the key as `Shift` (text), not `⇧`. The `⇧` symbol is standard on Apple keyboards but uncommon on Windows. Users who do not recognize the symbol cannot tell which key to press without external research.
I personally spent ~30 minutes trying to identify this symbol before asking elsewhere — it is not searchable by copy-paste in most search engines, which compounds the discoverability issue.
## Why this matters
- macOS uses a fully consistent symbol set (⌃⇧⌥⌘) — symbols make sense there.
- PowerToys uses **mixed** notation: only `Shift` and `Win` are iconified while `Ctrl` and `Alt` remain as text. This inconsistency breaks the visual hierarchy and provides no benefit over plain text.
- Microsoft's own documentation (Windows shortcut help, Office) consistently uses the text `Shift`.
## Suggested fix
Pick one and apply it consistently:
1. **Text everywhere**: `Win + Ctrl + Shift + P` (matches Microsoft conventions, most familiar on Windows).
2. **Symbols everywhere**: `⊞ ⌃ ⇧ P` (matches Apple/ISO 9995-7, but unfamiliar on Windows).
Option 1 is recommended for Windows-native ergonomics.
## Environment
- PowerToys: latest (observed 2026-05)
- OS: Windows 11 Pro 26200
- Affected UI: Command Palette shortcut display (the small chip row showing the activation hotkey)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.