Most of us use a fraction of what our editor can do. VS Code is quietly packed with features that shave seconds off tasks you do hundreds of times a day, and those seconds add up fast. Here are the VS Code tips that have genuinely changed how I work — no obscure extensions required, just what is already in the box.
Live in the Command Palette
If you learn one shortcut, make it the Command Palette: Ctrl/Cmd + Shift + P. Nearly everything VS Code can do is searchable there by name — change theme, format a document, split the editor, run a task. You stop hunting through menus and start typing what you want. It is the fastest way to discover features you did not know existed.
Jump anywhere instantly
Two navigation shortcuts do most of the heavy lifting:
Ctrl/Cmd + P Open any file by typing its name
Ctrl/Cmd + Shift + O Jump to a symbol in the file
F12 Go to definition
Alt + Left/Right Navigate back / forwardOnce your hands know these, reaching for the file tree or scrolling to find a function starts to feel slow. You navigate a large codebase at the speed of thought.
Master multi-cursor editing
This is the trick that makes people ask “how did you do that?” Hold Alt and click to place multiple cursors, or press Ctrl/Cmd + D to select the next occurrence of the current word and edit them all at once. Renaming five variables or wrapping ten lines in the same change becomes a single fluid motion instead of tedious repetition.
Let the editor do the boring parts
Turn on Format on Save in your settings and never manually fix indentation again. Pair it with a formatter (Prettier, Black) and your code is tidy the instant you hit save. Add Ctrl/Cmd + . for Quick Fixes — it surfaces the auto-import, the missing method stub, or the lint fix right where your cursor is.
Rename the right way
Never find-and-replace a symbol by hand. Put your cursor on it, press F2, type the new name, and VS Code updates every reference across the project safely, understanding scope instead of blindly matching text. It is the difference between a rename that works and one that quietly breaks three files.
Search like you mean it
Project-wide search (Ctrl/Cmd + Shift + F) is obvious; using it well isn’t. The three icons at the end of the search box toggle case sensitivity, whole-word matching, and — the big one — regex mode, which turns search-and-replace into a refactoring tool. Capture groups work in the replace field: search console\.log\((.*)\), replace with logger.debug($1), and preview every change across the project before applying. Two more force multipliers hide in the “files to include” field: scope a search to src/**/*.ts to skip vendored noise, and use the ! prefix to exclude (!**/*.test.ts). Once you’ve done one multi-file regex replace with preview, you stop dreading rename-adjacent chores entirely.
Snippets: stop typing the same ten lines
Anything you type more than a few times a week deserves a snippet. Command Palette → “Snippets: Configure Snippets” → pick your language, and define:
"Try-catch async": {
"prefix": "tca",
"body": [
"try {",
" $1",
"} catch (err) {",
" console.error('${2:context}:', err);",
"}"
]
}Now tca + Tab expands the block, with Tab-stops ($1, $2) walking your cursor through the fill-in points. Test scaffolds, component boilerplate, license headers, that API error-handling pattern your team standardized on — each becomes three keystrokes. Snippets are also the honest fix for the “I keep writing this slightly differently each time” consistency problem.
The integrated terminal is a real terminal
Stop alt-tabbing to a separate terminal window. Ctrl/Cmd + ` toggles a full terminal inside the editor — split it, run several side by side (server in one, tests watching in another), and enjoy the small-but-constant wins: file paths in error output are clickable and jump straight to the line, and the terminal inherits your project’s directory and environment. Pair it with the Problems panel (Ctrl/Cmd + Shift + M), which aggregates every lint and compile error across the project into one clickable list, and most of the run-check-fix loop happens without your hands leaving the editor.
Refactor beyond rename
F2 rename is the gateway; the rest of the refactoring menu lives behind Ctrl/Cmd + . on a selection. Highlight an expression and extract it to a constant; highlight a block and extract it to a function or method — the editor figures out the parameters and return value for you. Language-aware “Organize Imports” (Shift + Alt + O) sorts and prunes unused imports in one stroke, and “Go to References” (Shift + F12) shows every usage inline without losing your place. These are the features that separate “text editor with syntax highlighting” from the IDE you actually paid nothing for.
Frequently asked questions
Which extensions are actually worth installing? Fewer than you think — extension bloat slows startup and adds noise. The consensus short list: your language’s official extension, Prettier or the equivalent formatter, ESLint or the equivalent linter, and GitLens if you work in a team. Add others only when you feel a specific pain.
How do I sync settings between machines? Built-in now: turn on Settings Sync (gear icon → “Backup and Sync Settings”) and your settings, keybindings, snippets, and extension list follow your GitHub or Microsoft account to any machine.
Is it worth learning the keyboard shortcuts if I’m productive with the mouse? Learn the five or six from this article, not all two hundred. The payoff isn’t raw speed — it’s staying in flow. Every reach for the mouse is a micro-interruption, and the shortcuts that eliminate the most-frequent reaches (file open, search, terminal, quick fix) return the most focus.
Build the habit
You will not absorb all of these at once, and that is fine. Pick one this week — the Command Palette is a great start — and use it deliberately until it is automatic, then add another. Stack a few of these VS Code tips into muscle memory and the editor stops being something you fight and becomes something that gets out of your way.
