
VS Code has a huge shortcut reference, but you do not need to memorize it. On a Mac, the six habits that remove the most mouse work are: opening commands, opening files, searching across the workspace, toggling the sidebar, switching to the terminal, and editing with multiple cursors.

Learn these first
| Shortcut | What it does |
|---|---|
Shift-Command-P |
Open the Command Palette |
Command-P |
Quick Open: find a file by name |
Shift-Command-F |
Search across the workspace |
Command-B |
Show or hide the primary sidebar |
Control-` |
Show or hide the integrated terminal |
Option-Click |
Add another cursor |
If you are switching from Windows, use VS Code first as a tool for moving through files, searching, and making controlled batch edits. Do not try to relearn every command in one week.
Command Palette and Quick Open
Command Palette
Shift-Command-P
This is VS Code's universal entry point. When you cannot remember where a feature lives—or what an extension calls its command—open the palette and search for it. It is often faster than navigating a menu, and it gives unfamiliar features a consistent place to start.
Quick Open
Command-P
Quick Open finds files with fuzzy matching, which is much faster than drilling through the Explorer in a large project. It is especially useful in a convention-driven app such as Next.js, where routes and components are organized by file path. Pair it with the Mac development setup guide when you are building out a new machine.
Files, tabs, and the sidebar
Close the current editor
Command-W
Toggle the sidebar
Command-B
The Explorer, Search, and Source Control views can be reached through the activity bar or the Command Palette. If you constantly switch among them, pick one route and make it automatic. The gain comes from reducing small decisions, not from avoiding every click.
Editing with multiple cursors
Option-Click
Command-D
Shift-Command-L
Option-Clickadds cursors manually.Command-Dselects the next occurrence of the current selection.Shift-Command-Lselects all matching occurrences.
These commands are excellent for carefully renaming a local variable, adding a repeated prefix, or changing a repeated JSX structure. They are not a substitute for a language-aware rename refactor: use VS Code's Rename Symbol command when identifiers may have different scopes or meanings.
Move or copy a line
Option-Up Arrow / Option-Down Arrow
Shift-Option-Up Arrow / Shift-Option-Down Arrow
The first pair moves the current line; the second copies it above or below. They are tiny actions, but they make small edits noticeably smoother.
Search, navigation, and definitions
Search the workspace
Shift-Command-F
Use workspace search to find a component, CSS class, interface field, or piece of copy across files.
Search the current file
Command-F
Go to definition
F12
Command-Click
Go to Definition is only as reliable as the project's language setup. If it regularly jumps to the wrong place or fails entirely, investigate TypeScript configuration, path aliases, and project structure rather than assuming the shortcut is broken.
Terminal and Source Control
Toggle the integrated terminal
Control-`
Front-end work constantly alternates between editing and commands such as npm run dev, git status, and pnpm test. Keeping the terminal inside VS Code removes a context switch, but it is still a real shell: inspect commands before running them and keep project dependencies intentional.
Once this feels natural, connect a small keyboard workflow: review changes in Source Control, write a focused commit message, run the relevant command, then return to the file. For package-manager choices and project consistency, see pnpm in practice.
How to make shortcuts stick
- Start with five to eight commands you use every day.
- Memorize by situation—opening, searching, editing, and running—not by a giant feature list.
- Make repeated actions follow one route, such as Quick Open first for files.
- Create custom bindings only after an action is genuinely frequent.
If you use a command once a week, look it up when you need it. Shortcut fluency is about an uninterrupted work loop, not a large number of memorized keys.
Where to go next
- Starting development on a new Mac? Follow the 30-minute Mac development setup.
- Want a more predictable JavaScript and TypeScript install workflow? Read pnpm in practice.
- New to the Mac keyboard itself? Use the Windows-to-Mac roadmap before trying to force every Windows habit onto macOS.
For the complete, version-specific reference, keep the official VS Code Keyboard Shortcuts documentation nearby.
Continue reading
New Mac? Don't Install Apps Yet: What macOS Already Does for Office Work
A practical check of the PDF, ZIP, screenshot, image conversion, document scanning, file preview, AirDrop, notes, and reminders tools already built into your Mac—and the point where a third-party app becomes worth installing.
21 minHookify Guide: Generate Claude Code Hooks Without Handwritten JSON
Use Hookify to create Claude Code hooks through conversation, understand its rule files, apply practical automations, and debug hooks that do not run.
9 minpnpm in Practice: Installation, Migration, and Workspaces
Use pnpm for faster installs, smaller dependency storage, stricter resolution, npm migration, and practical workspace management across frontend projects.
Subscribe to FreeMac
Weekly picks: free Mac software reviews, trusted source updates, alternatives, and low-friction guides.