I used to be that developer who opened VS Code with absolutely nothing installed except the default theme. Thought I was a purist. Thought all these extensions were bloat. Spoiler: I was wrong, and I wasted a lot of time.
The thing about VS Code extensions is that they're not mandatory—but once you find the right ones, going back feels like coding with your eyes closed. I've spent the last year installing, testing, and ruthlessly uninstalling extensions. Some promised the world and delivered notification spam. Others quietly saved me hours every single week.
Here are the 10 extensions that actually stuck. The ones I install first on any new machine, the ones I'd genuinely miss if they disappeared tomorrow.
The Essentials That Changed My Workflow
1. Prettier (Code Formatter)
Stop arguing with your team about spacing. Stop manually fixing indentation. Prettier just... does it. Every file, every time, same rules.
I resisted this for months. Thought manual formatting gave me control. Then I realized I was spending 20 minutes per day on something a tool could do in 20 milliseconds. The extension is free, saves a config file in your project, and enforces consistency across the entire team. You can set it to format on save, and it's almost hypnotic watching your messy code snap into shape.
Fair warning: if you have strong opinions about single vs. double quotes, this might frustrate you initially. But honestly? That's the point. Stop caring, let Prettier care, move on with your life.
2. ESLint
This catches bugs before they exist. Seriously.
ESLint scans your code for common mistakes—unused variables, accidental infinite loops, type mismatches—and flags them in real-time. I used to find these errors in production. Now I find them before I even save the file. The squiggly red line appears, I read the explanation, I fix it. Takes 10 seconds instead of 10 minutes of debugging later.
Setup is slightly annoying (you need ESLint installed in your project, not just the extension), but it's a one-time thing. After that, it's pure automation. Pair it with Prettier and you've got a self-correcting development environment.
3. Thunder Client (or REST Client)
I stopped opening Postman separately. This changed everything.
Thunder Client lets you write API requests directly in VS Code, send them, and see the responses instantly. No context switching. No bloated Postman window eating your RAM. Just .http or .rest files that you can version control and share with your team.
You literally write requests like this:
GET https://api.example.com/users
Authorization: Bearer token123
Hit a button, get response. Thunder Client has a slightly nicer UI than the basic REST Client, but honestly, both work. I went with Thunder Client because it handles environment variables better and the UI doesn't feel like it's from 2015.
The Intelligence Layer
4. GitHub Copilot
Okay, this one costs money. Let's be honest about that upfront.
Is it worth $10/month? For me, yes. For everyone? Maybe not.
Here's what it does: it predicts what you're about to type and suggests it. Usually it's right. Sometimes it's brilliantly right—it'll auto-complete entire functions based on the context above it. Sometimes it's confidently wrong. The key is learning when to trust it and when to ignore it.
Best use case: writing repetitive code. Generating test cases. Writing documentation. Worst use case: relying on it to write critical business logic without thinking through it first. I've seen developers accept Copilot suggestions that look correct but have subtle bugs.
My honest take: if you're early in your career, Copilot might teach you bad habits (too much auto-acceptance without understanding). If you're experienced, it's a legitimately useful productivity boost. It's not replacing developers, despite what Twitter says, but it is saving me maybe 2-3 hours a week on boilerplate code.
5. Path Intellisense
Stupid simple. Incredibly useful.
You're importing a file. You type the path. Path Intellisense auto-completes it and shows you available files in real-time. No more typos in import paths. No more hunting through folder structures trying to remember if that file is in /utils or /helpers.
This extension is so good it should honestly be built into VS Code by default. Takes 30 seconds to install, saves you dozens of "file not found" errors every week.
The Visual Helpers
6. Bracket Pair Colorizer 2
Nested brackets become a nightmare in complex code. This extension colors matching brackets, so when you're staring at 5 levels of parentheses, you can actually see which ones belong together.
It sounds cosmetic. It's not. It cuts debugging time for syntax errors significantly. You spot mismatched brackets instantly instead of spending 15 minutes trying to figure out why your code won't parse.
7. Peacock
This is cosmetic. I'm including it anyway because it genuinely improves how you work when you have multiple projects open.
Peacock color-codes your VS Code windows. Different projects get different colors. When you're alt-tabbing between three projects, you instantly know which one you're looking at. Sounds trivial until you've switched to the wrong window and started editing the wrong project file at 11 PM.
Yes, I've done that. Yes, I use Peacock now.
The Productivity Multipliers
8. GitLens
This extension shows you who wrote each line of code, when, and in which commit. Sounds like a snitching tool. It's actually incredibly powerful for understanding code.
You're reading some weird line and wondering why it exists. GitLens shows you the commit message. Suddenly it makes sense. Or it doesn't, and you can click through to the PR and see the full discussion.
For teams, this is essential. For solo developers, it's useful for understanding your own past decisions (spoiler: past you was often confused too).
9. Tabnine
This is like Copilot's quieter, lighter cousin. Free version exists.
Tabnine uses AI to suggest code completions, but it's less aggressive than Copilot. It learns from your codebase's patterns and adapts. Paid version is better, but the free tier is genuinely functional and doesn't require an internet connection.
I keep both Copilot and Tabnine installed (I could be wrong here, but I find I use Copilot for the big suggestions and Tabnine catches the smaller ones). They don't conflict, and having redundancy means I'm never waiting for suggestions.
10. Live Server
For front-end development, this is essential. One click and your HTML/CSS/JS file is served on a local server with hot reload.
Change something, save, page refreshes automatically. No manual browser refresh. No dealing with file:// protocol issues. It's so obvious in retrospect, but the first time you use it, you wonder how you ever coded without it.
Comparison and Setup Guide
| Extension | Category | Cost | Essential? |
|---|---|---|---|
| Prettier | Code Formatting | Free | Yes |
| ESLint | Code Quality | Free | Yes |
| Thunder Client | API Testing | Free | If you test APIs |
| GitHub Copilot | AI Assistance | $10/month | No (nice to have) |
| Path Intellisense | Autocompletion | Free | Yes |
| Bracket Pair Colorizer 2 | Visual Aid | Free | If you write nested code |
| Peacock | Workspace Organization | Free | If you juggle multiple projects |
| GitLens | Version Control | Free (Pro version available) | Yes |
| Tabnine | AI Assistance | Free (Premium available) | No (but excellent free tier) |
| Live Server | Front-end Development | Free | If you do front-end work |
My Take
Here's what surprised me: most of these extensions aren't about new features. They're about removing friction from things you're already doing. Prettier doesn't let you write better code—it just stops you from manually formatting. GitLens doesn't improve your code quality—it just lets you understand existing code faster.
The honest part: I used to think developers who relied on extensions were lazy. I was being an elitist idiot. The best developers I know aren't spending time on stuff machines can do. They're spending time on the actual logic, the architecture, the problem-solving. The extensions handle the repetitive stuff.
What disappointed me: some extensions I expected to be game-changers (like certain AI tools) were honestly overhyped. And some free tools have gotten slower as they added premium features, which is frustrating. But the core ten here? They're solid. They've earned their place on my machine.
Who is this actually for? If you're coding more than a few hours a week, these will pay for themselves in time saved. If you're a hobbyist coding occasionally, the free ones are still worth it. If you're working in a team, Prettier and ESLint should be non-negotiable—they save way more time in code review than they cost to set up.
Verdict
Install these three first: Prettier, ESLint, and Path Intellisense. They're free, they have no downsides, and they'll improve your workflow immediately. Add GitLens and Thunder Client (or REST Client) if you work with git and APIs.
Give yourself a week with those five. After that, add the others based on what you actually need. Copilot if you want AI assistance and have $10/month. Live Server if you do front-end work. Peacock if you have multiple projects open constantly. Bracket Pair Colorizer if you're writing deeply nested code.
Most importantly: resist the urge to install 30 extensions because they look cool. Your VS Code startup time will thank you. Your sanity will thank you. The extensions that survive your ruthless culling are the ones worth keeping.
Start lean. Add what you actually use. That's the way forward.
Published by Dattatray Dagale • 29 October 2026
0 Comments