The VS Code Keyboard Shortcuts tool is a focused, searchable reference for 20 common default commands in Visual Studio Code, with separate Windows, Linux, and macOS mappings. It helps you find the key combination for a named action, confirm the platform-specific default, and return to VS Code ready to use it. Open the tool, select the operating system that matches the machine running VS Code, then search for a command such as Format Document, a category such as comments, or a key string such as Ctrl+P. The result is a compact default reference, not a live view of your editor. It cannot read keybindings.json, detect conflicts, or prove that a default is still active after customization. For a normal VS Code setup, that makes it faster than guessing at modifier combinations; for a customized, remote, extension-heavy, or non-US-keyboard setup, treat the result as a documented starting point and verify it in VS Code's built-in Keyboard Shortcuts editor. Here, “VS Code” means Visual Studio Code, the code editor, rather than Microsoft’s separate Visual Studio IDE.
What the VS Code shortcut reference includes
The reference is intentionally bounded to exactly 20 unique command names. It covers Command Palette access, Quick Open, settings, keyboard settings, line editing, comments, search, formatting, symbol actions, the integrated terminal, and basic file operations. Each row contains one command, one category, and explicit mappings for all three displayed platforms.
Those platform mappings come from Microsoft’s current shortcut references, with eight representative entries maintained as source-checked golden mappings. The reference searches a fixed in-browser table rather than monitoring your keyboard or communicating with VS Code. It does not install an extension, inspect editor settings, modify keybindings.json, or identify conflicts on your computer.
Look up and use a shortcut in VS Code
Use the lookup whenever you know the action but not the exact keys. The following process keeps platform selection, search, and verification in the correct order.
- Choose the platform first. Select Windows, Linux, or macOS before reading any mapping. The selector determines which default modifiers appear, so changing platforms can change the answer rather than merely changing its presentation.
- Search for the action, category, or key string. Enter a command such as Format Document, a category such as comments, or a combination such as Ctrl+P. Search matches command names, categories, and key labels case-insensitively against the fixed table.
- Read the complete row. Check the command name and every modifier before pressing the keys. For example, do not assume that a Windows combination also applies on Linux merely because both platforms commonly use Ctrl.
- Apply the displayed combination in VS Code. Make sure the editor, terminal, file explorer, or another relevant part of the interface has focus. Some commands only apply to a particular context, such as an active editor selection or an open terminal.
- Verify the binding if it behaves differently. Use the Command Palette to open VS Code’s built-in Keyboard Shortcuts editor, search for the command name, and inspect its current keybinding and when clause. If you need to see what VS Code receives, run Developer: Toggle Keyboard Shortcuts Troubleshooting; it can show the key received and the command dispatched.
Why the operating system changes the mapping
Windows and Linux share many Ctrl-based commands, but the reference does not treat their defaults as interchangeable. macOS also uses different modifier conventions in several commands. These differences are real defaults rather than errors in the lookup.
| Command | Windows | Linux | macOS |
|---|---|---|---|
| Format Document | Shift+Alt+F | Ctrl+Shift+I | Shift+Option+F |
| Toggle Block Comment | Shift+Alt+A | Ctrl+Shift+A | Shift+Option+A |
The table writes modifiers as readable text such as Ctrl, Shift, Alt, Cmd, Option, or Control instead of relying only on platform-specific symbols. For a broader side-by-side look at the platform defaults, see VS Code Keyboard Shortcuts defaults compared by platform.
Read shortcut chords and modifier labels correctly
A chord is a sequence of key combinations. A chord such as Ctrl+K Ctrl+S means press Ctrl+K, release it, and then press Ctrl+S; it is not one simultaneous four-key press. The command still depends on the interface context in which the sequence begins.
The documented defaults assume a standard US keyboard layout, while VS Code renders keys according to the active layout. Function keys such as F1, F2, and F12 can also be intercepted by laptop hardware before they reach VS Code. Those two details explain why a visually familiar shortcut may not produce the expected command.
Troubleshoot a shortcut that does not respond
When a listed combination fails, do not assume the reference is wrong or immediately assign a new binding. First determine whether the shortcut is being received and then whether VS Code dispatches it in the current context.
- Check focus and editor state. Activate the intended panel and make sure any required text selection or file is present. Context-specific when clauses can prevent a command from running.
- Inspect the current binding. Open the built-in Keyboard Shortcuts editor and locate the same command name. It shows the binding currently assigned in that installation rather than only the default documented by the lookup.
- Trace the keystroke. The Developer: Toggle Keyboard Shortcuts Troubleshooting command can display the key VS Code receives and the command it attempts to dispatch, helping distinguish an intercepted key from a context mismatch.
- Account for other software. User keybindings, keymap extensions, other extensions, operating-system shortcuts, accessibility tools, remote environments, and Linux window managers can all alter the result.
Microsoft’s Customize keyboard shortcuts documentation explains that rules can include context conditions. If you need to locate or change a customized binding, follow the focused workflow in find and change a VS Code shortcut default.
Know where the 20-command reference stops
This desk reference does not claim to include every built-in or extension-contributed VS Code command. It intentionally omits debugging sequences beyond common symbol actions, task bindings, notebook-specific commands, accessibility-specific alternatives, Vim and Emacs keymaps, and localized layout variants. If the command you need is absent, use VS Code’s built-in Keyboard Shortcuts editor or Microsoft’s full shortcut reference for the relevant platform.
The platform selector is therefore essential even when Windows and Linux look similar. Likewise, a successful row lookup is evidence of a published default, not proof that the binding is active in your customized profile. The tool can guide you to the right command and standard combination, but only VS Code can show the effective binding in your current environment.
Build a dependable daily shortcut routine
A practical routine keeps the reference useful without treating it as a substitute for VS Code’s own diagnostics:
- Search by the action you want to perform before searching by a guessed combination.
- Confirm the selected platform before copying or pressing the displayed keys.
- Use familiar categories such as search, comments, formatting, navigation, or terminal commands to build a small working set.
- Check the built-in editor before relying on a shortcut in a customized, remote, or accessibility-adjusted setup.