VS Code is still the dominant code editor in 2026, and its extension ecosystem is a big reason why. But with thousands of extensions available, most developers are either using too many (slow editor) or too few (missing out on huge productivity gains).
Here are the 10 extensions I actually use every day — no filler, no “Prettier is nice” padding.
1. GitHub Copilot
The single biggest productivity boost available to developers today.
GitHub Copilot has evolved significantly since its launch. In 2026, it handles inline completions, chat-based coding, multi-file edits, and even terminal command suggestions. It’s not perfect — you still need to review its output — but it eliminates the tedious parts of coding: boilerplate, repetitive patterns, test scaffolding, regex, and “how do I do X in this framework again?”
Cost: $10/month (individual) or $19/month (business). Free for verified students and popular open-source maintainers.
Worth it? Absolutely. If it saves you 30 minutes a day — and it will — the math isn’t even close.
2. GitLens
GitLens turns VS Code’s basic git support into a proper git powerhouse. Inline blame annotations show who changed each line and when. The commit graph visualizes branch history. File history lets you see every change to a file over time.
The free tier covers everything most developers need. GitLens+ (paid) adds visual comparisons and team features, but I’ve never needed it.
Why I use it: Inline blame alone is worth the install. Knowing why a line exists (by reading the commit message on hover) saves you from asking “what does this do?” a dozen times a day.
3. Error Lens
Error Lens takes VS Code’s subtle squiggly underlines and turns them into impossible-to-miss inline error messages. Errors, warnings, and hints appear directly on the line, in color, right in your editor.
This sounds small but it changes your workflow. You catch errors immediately instead of after running the build. It’s especially good for TypeScript and linting errors.
Config tip: Turn off info-level hints if they’re too noisy. Errors and warnings only keeps it useful without being overwhelming.
4. Todo Tree
Todo Tree scans your codebase for TODO, FIXME, HACK, and other comment tags, then displays them in a sidebar tree view. Click any item to jump straight to it.
I use TODO comments as breadcrumbs while coding — “TODO: handle error case,” “FIXME: this query is slow.” Todo Tree makes sure those breadcrumbs don’t get lost.
5. REST Client
REST Client lets you send HTTP requests directly from VS Code using .http files. Write a request, hit Send Request, see the response — no need to switch to Postman or curl in the terminal.
GET https://api.example.com/users
Authorization: Bearer {{token}}You can define variables, chain requests, and commit your .http files to the repo so the whole team has them. I’ve completely replaced Postman with this.
6. Docker
The Docker extension from Microsoft gives you a visual interface for managing containers, images, registries, and Docker Compose. You can view running containers, check logs, exec into shells, and manage images without memorizing docker CLI commands.
If you work with Docker daily (and in 2026, who doesn’t?), this is essential.
7. ESLint + Prettier (Together)
I’m counting these as one because you should always use them together. ESLint catches code quality issues; Prettier formats your code consistently.
The key setting: Enable format-on-save with Prettier as the default formatter, and configure ESLint to auto-fix on save. Never argue about code style again.
{
"editor.formatOnSave": true,
"editor.defaultFormatter": "esbenp.prettier-vscode",
"editor.codeActionsOnSave": {
"source.fixAll.eslint": "explicit"
}
}8. GitHub Pull Requests
The GitHub Pull Requests extension lets you review and manage PRs without leaving VS Code. Browse open PRs, check out branches, leave inline comments, approve, and merge — all from your editor.
It’s slower than the GitHub web UI for quick reviews, but for deep code review where you want to understand the full context, it’s superior.
9. Remote - SSH
Remote - SSH lets you open a VS Code window connected to a remote machine over SSH. Your editor runs locally with full performance, but files, terminal, and extensions operate on the remote host.
I use this for editing code on my home server, working on Raspberry Pi projects, and connecting to cloud VMs. It’s seamless — you forget you’re working remotely.
10. Vim (for the keybindings)
Vim emulation in VS Code is the best of both worlds: Vim’s keyboard-driven editing speed with VS Code’s UI, extensions, and Copilot integration.
If you’ve never used Vim keybindings, the learning curve is 2-3 painful weeks followed by a lifetime of faster editing. ciw to change a word, dd to delete a line, / to search — once it’s in your muscle memory, going back feels like moving through mud.
Not for everyone. But if you’re curious, try it for a month. You’ll either love it or uninstall it in 3 days.
Honorable Mentions
- GitHub Actions — manage and debug workflows from VS Code
- Tailwind CSS IntelliSense — autocomplete for Tailwind classes (essential if you use Tailwind)
- Thunder Client — alternative to REST Client with a GUI interface
- Markdown All in One — keyboard shortcuts and preview for markdown files
Extensions I Removed
- Bracket Pair Colorizer — VS Code has this built in now (
editor.bracketPairColorization.enabled) - Path Intellisense — VS Code’s native path completion is good enough
- Auto Rename Tag — Built into VS Code since late 2023
The Bottom Line
Install Copilot, GitLens, and Error Lens today — those three alone will noticeably improve your daily workflow. Add the rest as needed based on your stack. And regularly audit your installed extensions — every extension adds startup time and memory usage. If you haven’t used it in a month, disable it.
Your editor is where you spend most of your working hours. Invest the time to set it up right.