This page focuses on the editor shortcuts people need repeatedly during development, phrased as tasks instead of raw key lists.
Windows/Linux: Ctrl+Shift+P
macOS: Cmd+Shift+PExample: Use this when you know the action you want but do not want to hunt through menus.
Gotcha: This is the fastest entry point for commands that do not have a dedicated shortcut on your keyboard layout.
Windows/Linux: Ctrl+Shift+F
macOS: Cmd+Shift+FExample: Useful when you need to find usages of a symbol, route, or string across multiple files.
Gotcha: Global search results can be noisy in generated folders. Exclude build output in your workspace settings when needed.
Windows/Linux: Ctrl+P
macOS: Cmd+PExample: Type part of the filename and jump directly without browsing the explorer.
Gotcha: This is most effective when filenames are distinctive. Generic names like `index` often need more of the path typed in.
Windows/Linux: Shift+Alt+Down
macOS: Shift+Option+DownExample: Useful when you want a copy of the current statement, config block, or markup line directly below.
Gotcha: On some systems the shortcut may conflict with input method or OS-level bindings.
Windows/Linux: F2
macOS: F2Example: Use this when language support is available and you want consistent renaming across references.
Gotcha: Results depend on the language server or extension. In plain text files this is only a text edit, not semantic refactoring.
Visual Studio Code gets faster when you treat the keyboard as the primary interface instead of a backup. The point of a shortcut reference is not to memorize dozens of obscure bindings. It is to make the high-frequency actions frictionless: opening files, switching symbols, jumping to definitions, viewing references, commenting code, opening the terminal, and fixing problems without breaking flow.
If you searched for Visual Studio Code shortcuts, VS code uncomment shortcut, Vscode comment multiple lines shortcut, or a printable shortcut reference, this page focuses on the commands that actually move daily development forward.
| Task | Shortcut | Why it matters |
|---|---|---|
| Show Command Palette | Ctrl+Shift+P or F1 |
Entry point to almost everything |
| Quick Open file | Ctrl+P |
Jump to files without browsing the sidebar |
| Go to Symbol in file | Ctrl+Shift+O |
Jump inside the current file quickly |
| Go to Definition | F12 |
Move from usage to source |
| Peek Definition | Alt+F12 |
Inspect code without leaving context |
| Go to References | Shift+F12 |
Find all usages of a symbol |
| Toggle Line Comment | Ctrl+/ |
Comment or uncomment the current line selection |
| Toggle Block Comment | Shift+Alt+A on Windows, Ctrl+Shift+A on Linux |
Useful for larger commented regions |
| Format Document | Shift+Alt+F on Windows, Ctrl+Shift+I on Linux |
Keep code consistently formatted |
| Open Keyboard Shortcuts | Ctrl+K Ctrl+S |
Inspect or customize bindings |
Ctrl+P, Ctrl+Shift+O, F12, and Shift+F12 cover a huge percentage of navigation work. Open a file, jump to a symbol, visit its definition, then inspect its references. That is the backbone of productive code reading in VS Code.
Commenting, uncommenting, formatting, and multi-step refactors are much smoother when they stay on the keyboard. Even if you do not memorize dozens of shortcuts, learning the ones for comment toggling, rename, and formatting pays for itself quickly.
Whenever you forget a binding, open the Command Palette. It is effectively the searchable index of the editor. Over time, repeated commands become memorable because you use them by name first and by shortcut later.
A productive editor session often looks like this:
Ctrl+P to open a file by nameCtrl+Shift+O to jump to a symbol within that fileF12 to go to a definitionShift+F12 to see references without guessworkCtrl+Shift+P to reach a command you remember by name but not by keysThat sequence matters because it mirrors how developers actually move through code: file, symbol, definition, references, action.
A lot of people search specifically for the VS Code comment multiple lines shortcut or the uncomment shortcut. The practical rule is simple:
That is why “comment” and “uncomment” are often the same shortcut in practice. The editor toggles the state rather than using unrelated commands.
Use Shift+F12 on Windows and Linux. This opens the references view for the symbol under the cursor so you can inspect usages without manually searching the whole codebase.
Ctrl+F7 in VS Code?Ctrl+F7 is not one of the standard default shortcuts in the main VS Code reference for Windows and Linux. If it does something in your setup, the behavior is likely coming from a custom keybinding, a keymap extension, or another tool in your environment.
Use Ctrl+Shift+P or F1 to open the Command Palette, then search by command name.
Group them by workflow: file navigation, symbol navigation, editing actions, and code intelligence. Learn the few commands you use every day first.
The shortcuts become more valuable as language tooling improves. Go to definition, peek definition, and go to references work best when the language server or extension for your stack is configured well. In other words, keyboard speed and code intelligence reinforce each other. The shortcut is only the visible layer; the real win is a navigation model that keeps context intact.
Use the Vim reference for a modal editing contrast, the Git reference when code navigation turns into commit review, the Bash reference when you jump from the editor into the terminal, or the Postgres reference when the file you opened is a migration or query script.
A shortcut page becomes more useful when it stays selective. Ten reliable commands that cover navigation, editing, and code intelligence are better than a giant wall of bindings you never remember. That is the right mindset for Visual Studio Code as well: keep the default reference close, then customize only where repeated friction remains.
Everyone by now presumably knows about the danger of premature optimization. I think we should be just as worried about premature design - designing too early what a program should do.
…
…