The funny thing is that most of the features that would genuinely speed you up aren't hidden in obscure extensions. They ship with the editor, they're documented, and they sit one keyboard shortcut away. Here are eight of them worth pulling into your daily routine, with a quick note on why each one actually matters.
Why "Small" Editor Features Add Up
Speed in coding rarely comes from typing faster. It comes from reducing the tiny interruptions – reaching for the mouse, scrolling to find a file, retyping the same line with one small change. Each one costs a second or two, but they pile up across hundreds of repetitions a day.
There's also a focus cost. Every time you break flow to hunt for something, you have to rebuild your mental context afterward. The features below are valuable less because they save keystrokes and more because they keep you inside the problem you're actually trying to solve.
1. The Command Palette Does More Than You Think
Most people know Ctrl+Shift+P (Cmd+Shift+P on Mac) opens the Command Palette. Fewer people realize that the same box changes behavior depending on the first character you type. Delete the > and you're in quick file open. Type @ and you jump to a symbol in the current file. Type # and you search symbols across the workspace. Type : followed by a number and you go straight to that line.
This matters because it turns one shortcut into a universal navigation bar. Instead of memorizing separate commands for every kind of jump, you learn a single entry point and a handful of prefixes. Once that clicks, the sidebar file tree starts to feel slow by comparison.
2. Multi-Cursor Editing Beyond the Basics
Holding Alt (Option on Mac) and clicking to place extra cursors is the well-known version. The more useful trick is Ctrl+D (Cmd+D), which selects the next occurrence of whatever you've highlighted and adds a cursor there. Press it a few times and you're editing five variable names at once, without the risk of a global find-and-replace hitting something you didn't mean to change.
If you want every match at once, Ctrl+Shift+L (Cmd+Shift+L) selects all occurrences in the file. And Shift+Alt+I drops a cursor at the end of every selected line, which is perfect for adding commas, semicolons, or quotes to a block of data. These are the kind of edits that used to mean a quick regex – now they take about three seconds.
3. Rename Symbol Instead of Find-and-Replace
When you rename a function or variable with plain text replacement, you risk changing a string, a comment, or an unrelated identifier with the same name. F2 runs Rename Symbol, which uses the language server to understand your code structure and update only the real references – including across files.
This is one of those features that quietly prevents bugs. It's especially helpful in TypeScript, Python, and other languages with strong language support, where the editor actually knows which data you mean. Pair it with Shift+F12 (Find All References) to preview where something is used before you touch it.
4. Emmet for Fast HTML and CSS
If you write any front-end code, Emmet is already built in. Type ul>li.item*5 and press Tab, and VS Code expands it into an unordered list with five list items, each carrying the class item. It works for CSS abbreviations too – m10 becomes margin: 10px;.
Why it matters: markup is repetitive by nature, and Emmet removes most of that repetition. Even if you mainly work in frameworks like React, Emmet can be enabled for JSX through settings, so the same shorthand works in component files.
5. Breadcrumbs and Sticky Scroll for Orientation
Long files are disorienting. Breadcrumbs, the path bar across the top of the editor, show where you are in both the folder structure and the code structure – down to the class and method your cursor sits in. Click any segment and you get a dropdown to jump to siblings.
Sticky Scroll takes this further by pinning the current function or class header to the top of the editor as you scroll. You always know which block you're reading, even 200 lines deep. It sounds minor until you turn it off and realize how often you were scrolling back up just to check context.
6. The Integrated Terminal With Split Panes
Opening the terminal with Ctrl+` is common knowledge, but splitting it is less so. You can run a dev server in one pane, a test watcher in another, and keep a third free for git commands – all without leaving the editor or juggling OS windows.
You can also move the terminal into the editor area as its own tab, which is handy on smaller screens. The real benefit is that your code and the processes running it stay in one visual space, which cuts down on the constant window switching that eats attention.
7. Profiles for Different Kinds of Work
Profiles let you save separate sets of extensions, settings, keybindings, and themes, then switch between them. You might keep a lean profile for writing documentation, a heavier one for Python data work, and another for front-end projects with all the linters and formatters.
This matters for performance as much as organization. Every extension you load adds startup time and background work. Profiles let you run only what the current task needs, which keeps the editor responsive and your UI uncluttered.
8. Snippets You Write Yourself
VS Code ships with snippets for many languages, but the real speed gain comes from your own. Through Configure User Snippets in the Command Palette, you can define a trigger word that expands into a block of code with tab stops for the parts that change.
Think about the code you type every week – a test scaffold, a logging statement, a component template, a standard error handler. Each one is a candidate. A custom snippet library is basically a personal shorthand that grows with you, and it's portable across machines through Settings Sync.
Key Takeaway
You don't need to adopt all eight at once. Pick two that match friction you feel right now – maybe the Command Palette prefixes and Ctrl+D – and use them deliberately for a week until they become automatic. Then add the next one.
The goal isn't to become a keyboard-shortcut performer. It's to remove the small snags that pull you out of focus, so more of your time goes into thinking about the code rather than moving around it.
FAQ
Do these features work the same on Mac, Windows, and Linux?
Yes, the features themselves are identical. The shortcuts differ mainly in swapping Ctrl for Cmd on Mac, and a few Alt-based commands use Option. You can check any shortcut through Keyboard Shortcuts in the settings menu.
Will adding more extensions make VS Code faster?
Usually not. Many of the biggest productivity gains are already built in, and extra extensions can slow startup. Profiles are a good way to keep heavier setups contained to the projects that actually need them.
Can I change the default shortcuts?
Absolutely. The Keyboard Shortcuts editor lets you search any command and rebind it. If you're coming from another editor, VS Code also offers keymap extensions that recreate familiar bindings.
Is Sticky Scroll on by default?
It has been enabled by default in recent versions, but you can toggle it in settings by searching for "sticky scroll" if you prefer a cleaner view.
Final Thoughts
VS Code rewards curiosity. The editor has quietly grown into a very capable tool, and much of that capability sits in plain sight. Spending ten minutes this week learning one new habit can pay you back every single day you code.
Start with whichever feature made you think "wait, it can do that?" That reaction is usually a good sign it'll stick.
📚 Sources
Visual Studio Code – Tips and Tricks: https://code.visualstudio.com/docs/getstarted/tips-and-tricks
Visual Studio Code – Basic Editing (multi-cursor, selection): https://code.visualstudio.com/docs/editor/codebasics
Visual Studio Code – Emmet in Visual Studio Code: https://code.visualstudio.com/docs/editor/emmet
Visual Studio Code – Snippets in Visual Studio Code: https://code.visualstudio.com/docs/editor/userdefinedsnippets
Visual Studio Code – Profiles in Visual Studio Code: https://code.visualstudio.com/docs/editor/profiles
