Introduction
Here's the thing about VS Code extensions — there are thousands of them, and 90% will just clutter your editor and slow you down. I've been using VS Code since 2018, and I've probably installed (and uninstalled) more extensions than I care to admit. Some were amazing. Most were forgettable. A few actively made my life worse.
After years of testing, tweaking, and actually using these tools in real projects, I've narrowed it down to the extensions that genuinely earn their place in my setup. These aren't the flashy ones with the best marketing. These are the ones I actually can't work without.
The Extensions That Actually Matter
1. Prettier — Code Formatter
Let me be honest: formatting code manually is a waste of your brain. Prettier does it automatically, and it's genuinely life-changing. I used to spend time arguing with colleagues about whether to use tabs or spaces. Now Prettier handles it, and nobody has to care anymore.
The magic happens on save. Your messy code becomes consistent automatically. It's opinionated (you don't get to customize much), but that's actually the point. You stop making formatting decisions and start writing code.
The one downside? Sometimes Prettier formats things in a way that looks slightly weird to you at first. But after about a week, you stop noticing and just accept it. That's when you know it's working.
2. ESLint
ESLint catches mistakes before you run your code. Unused variables, missing semicolons, logical errors that would crash your app — it catches all of them right in the editor with those little red squiggles.
I pair this with Prettier because they work beautifully together. Prettier handles formatting (how your code looks), and ESLint handles code quality (whether your code is actually correct). Together, they're unstoppable.
Fair warning: ESLint can be annoying at first. It's strict. But that's the feature, not a bug. Those warnings have saved me from shipping broken code more times than I can count.
3. GitLens
GitLens shows you who wrote each line of code, when they wrote it, and the commit message. I know that sounds boring, but it's weirdly useful when you're debugging something weird and need to understand why a line exists.
You can hover over any code and see the history instantly. You can blame specific lines (yes, that's the technical term) and jump to commits. For teams especially, this is invaluable. It's like having git history right there in your editor instead of having to dig through the command line.
The free version is actually plenty good. The paid stuff is nice but not necessary unless you're on a huge team.
4. Live Server
If you're doing any front-end work, Live Server is essential. It runs a local web server and automatically reloads your browser when you save files. No more switching between your editor and manually refreshing your browser.
I've tested the alternatives, and they're all fine, but Live Server is reliable and lightweight. It's been around forever and just works. Sometimes the simplest tools are the best ones.
One small thing: it can slow down VS Code if you're not careful about what you're watching for changes. Make sure to exclude your node_modules and other large folders in your settings.
5. Thunder Client
You might be using Postman for API testing. I was too. Then I tried Thunder Client, and I realized I didn't need a separate app anymore.
It's built right into VS Code, has a cleaner interface than Postman (in my opinion), and syncs beautifully with your workspace. Test APIs, save requests, organize collections — all without leaving your editor.
The free version is genuinely generous. I haven't felt the need to upgrade because it has everything I use daily. That's rare.
6. Path Intellisense
This one seems small, but it saves me probably 10 minutes a day. Path Intellisense autocompletes file paths as you type them. So when you're importing a component or requiring a file, you get real-time suggestions.
Without it, you're either typing out full paths manually or relying on fuzzy search to find files. With it, you get smart, instant suggestions. It's one of those extensions that becomes invisible because it just works.
7. REST Client
REST Client lets you test APIs directly from your editor using .rest or .http files. You write a simple HTTP request, hit a button, and see the response instantly. No app-switching, no fussing with Postman.
I like pairing this with Thunder Client (yes, I use both for different workflows), and honestly, REST Client is lighter weight if you just need quick API testing. It's especially good for documenting API calls because you can keep them in version control with your code.
8. Tabnine
Tabnine is AI-powered autocomplete, and I was skeptical at first. Then I actually used it for a week and realized how much faster I code now.
It predicts what you're about to type based on your code patterns and the broader patterns it's learned from millions of lines of code. Sometimes it's spookily accurate. Sometimes it's completely wrong. You get used to ignoring the bad suggestions and accepting the good ones.
The free version has limited features, but it's still genuinely helpful. The pro version offers offline mode and better accuracy, but I haven't needed it.
9. Better Comments
Better Comments highlights your comments differently based on what type they are. Alerts show as red, questions as blue, important notes as orange. It's purely visual, but it makes scanning your code for important notes way easier.
If you're working in a legacy codebase with lots of comments (and let's be honest, most of us are), this extension is surprisingly useful. You can customize the colors and types, so it fits your team's commenting style.
10. Peacock
Peacock lets you color-code your VS Code workspace. So if you have multiple projects open, you can give each one a different color. It sounds cosmetic (because it is), but it actually reduces mistakes.
I can't tell you how many times I've almost edited code in the wrong project. Peacock makes it immediately obvious which project I'm looking at. Plus, if you're someone who cares about your workspace looking nice, it's satisfying.
| Extension | Primary Use | Must Have? |
|---|---|---|
| Prettier | Code Formatting | Yes |
| ESLint | Code Quality | Yes |
| GitLens | Git History | Yes |
| Live Server | Front-End Dev | If Doing HTML/CSS |
| Thunder Client | API Testing | If Building APIs |
| Path Intellisense | File Path Autocomplete | Recommended |
| REST Client | API Testing | Optional |
| Tabnine | AI Autocomplete | Nice to Have |
| Better Comments | Comment Highlighting | Optional |
| Peacock | Workspace Coloring | Nice to Have |
How to Actually Install These Without Killing Your Editor
Here's something I learned the hard way: installing extensions is easy. Installing the right extensions and not bloating your editor is harder.
Start with just Prettier, ESLint, and GitLens. Use those for a week. Feel the difference. Then add the extensions that match what you actually do (Live Server if you're doing front-end, Thunder Client if you're building APIs). Add one at a time and notice how it affects your workflow.
I see a lot of developers with 50+ extensions installed and their editor running like molasses. That's not because extensions are bad. It's because most of them aren't needed. Your editor should feel fast. If it doesn't, you have too much installed.
Extensions I Tested and Didn't Keep
I want to be fair here. I tested a bunch of other extensions that seemed promising but didn't make the cut.
Copilot is technically amazing, but it's paid and honestly makes me think less carefully about code. I'd rather type and think than let AI suggest everything. That's a personal preference, not a knock on the extension.
Bracket Pair Colorizer seemed like it would help, but VS Code now has this built-in, so the extension is redundant.
I tried three different "productivity" extensions that promised to make you code faster, and they were all just distracting. Sometimes fewer tools is actually better.
The Real Verdict
If you're starting from scratch, install Prettier, ESLint, and GitLens. These three will immediately improve your coding experience. Then evaluate the others based on what you actually do.
Don't install extensions because they're popular. Install them because they solve a real problem in your workflow. That's the difference between a great developer setup and a bloated, slow one.
VS Code is powerful because it's customizable, but customization only matters if you're intentional about it. These 10 extensions are the ones worth being intentional about.
Published by Dattatray Dagale • 07 May 2026
.gif)
0 Comments