Your editor should work for you, not the other way around. With the right VS Code tips, shortcuts and a few setting tweaks, you can finish the same work in half the time and barely touch the mouse. This article collects the practical techniques that genuinely speed up a daily workflow — the kind that become muscle memory rather than trivia. Examples are given for both Windows/Linux and macOS (replace Ctrl with Cmd on macOS).
Command palette and quick file switching
If this were the only shortcut you ever learned, you would still come out ahead: the command palette. Open it with Ctrl+Shift+P and you can reach almost everything the editor can do — no menu hunting required. Start typing the command and the matches filter down.
Ctrl+P— open any file by name instantly (Quick Open). A few letters is enough.Ctrl+Shift+O— jump to symbols (functions, classes, methods) in the open file.Ctrl+G— go to a specific line number.Ctrl+T— search for a symbol across the whole project.
A small trick: in Quick Open, type : after the file name followed by a line number (for example UserController.php:42) to land directly on that line.
Multi-cursor: edit everywhere at once
For repetitive edits, the most powerful VS Code tips revolve around multiple cursors. Instead of making the same change in ten places by hand, do it once:
Ctrl+D— select the word under the cursor; press again to add the next matching occurrence to the selection.Ctrl+Shift+L— select every occurrence of the selected word at once.Alt+Click— drop an extra cursor anywhere with the mouse.Ctrl+Alt+Up/Down(macOS:Cmd+Alt+Up/Down) — add a cursor on the line above or below.
Say you need to rename ten variable names in a JSON file: select the first, add the rest with Ctrl+D, type, and they all change together.
Line operations: move, copy, delete
Instead of dragging lines around, keep your hands on the keyboard:
Alt+Up / Alt+Down → move line up/down
Shift+Alt+Up / Down → copy line up/down
Ctrl+Shift+K → delete line
Ctrl+/ → toggle line comment
Ctrl+Enter → open a new line below (wherever the cursor is)Lifting an if block upward or duplicating a config line takes seconds this way. Once these settle into finger memory, you stop reaching for the mouse entirely.
Navigating and renaming code
In a large codebase, most time is lost to the question "where is this function defined?" VS Code solves that:
F12— Go to Definition.Alt+F12— Peek the definition in a small inline window.Shift+F12— find all references of a symbol.F2— rename a symbol safely; all references update automatically.Ctrl+Tab— cycle through recently used files.
Renaming with F2 uses the language server instead of a plain find-and-replace, so it won't catch false matches — renaming a variable won't mangle a comment or a string that happens to share the name.
Integrated terminal and Git flow
Working without leaving the editor is a major speed gain. Ctrl+` (backtick) toggles the integrated terminal; Ctrl+Shift+` creates a new one. You can split several terminals side by side — run a dev server in one and type Git commands in another.
The Source Control panel on the left (Ctrl+Shift+G) is ideal for reviewing changes line by line. Stage a file with the "+" next to it, write a message, and commit. Inline gutter markers show which lines changed; click one to revert it. For deeper history, the GitLens extension shows who wrote each line and when (blame) right at the end of the line.
Lasting wins through settings
Shortcuts are momentary; settings work in the background every day. Open settings with Ctrl+, or edit settings.json directly ("Preferences: Open User Settings (JSON)" in the palette). A few of the most useful:
{
"editor.formatOnSave": true,
"files.autoSave": "onFocusChange",
"editor.tabSize": 2,
"editor.bracketPairColorization.enabled": true,
"editor.minimap.enabled": false,
"files.trimTrailingWhitespace": true
}With formatOnSave and a formatter installed (Prettier, ESLint), your code is tidied on every save — the "indentation debate" simply disappears. Drop a .vscode/settings.json and .vscode/extensions.json in the project root and teammates open with the same settings and recommended extensions; consistency comes for free.
Snippets and focus
Turn the patterns you type often (a React component, a Laravel controller skeleton, a license header) into your own snippets: "Snippets: Configure User Snippets" in the palette. Type a trigger word, press Tab, and the whole block appears with the cursor hopping through the fields to fill in.
When you need to concentrate, Zen Mode (Ctrl+K then Z) hides every panel and leaves only the code. Ctrl+B toggles the side bar, and Ctrl+\ splits the editor so you can see two files side by side.
Frequently Asked Questions
How do I learn these shortcuts more easily?
Don't try to memorize them all in one day. Pick two or three a week and deliberately use them instead of the mouse. When you run a command from the palette, VS Code shows its shortcut next to it — a natural learning loop. You can also grab a printable summary from "Help → Keyboard Shortcuts Reference".
How do I move my setup to another machine?
Turn on VS Code's built-in Settings Sync (Gear icon → Turn on Settings Sync). Your settings, shortcuts, extensions and snippets sync through your GitHub or Microsoft account; sign in on a new machine and everything falls into place.
Do too many extensions slow VS Code down?
They can. Run "Developer: Show Running Extensions" from the palette to see which extension spends how much startup time and CPU. Disable the ones you don't use; enable some only for the relevant projects via the "workspace" level toggle.
Speeding up your editor is only the beginning of a faster workflow. If you're building a web project, an automation, or a setup that should accelerate your development process, let's look at it together — get in touch.