I'm not exaggerating. When I first switched to VS Code from Sublime Text back in 2019, I used it bare. No extensions. Just the editor, a terminal, and pure stubbornness. I lasted about a week before I felt like I was moving in slow motion.
The thing about VS Code extensions is that they're not optional luxuries—they're the difference between feeling productive and feeling frustrated. I've tested probably 50+ extensions over the past few years, and I've settled on a core ten that genuinely make me faster, less error-prone, and honestly, happier to code.
I'm not here to list every extension that exists. I'm here to tell you which ones actually matter, based on what I use every single day.
The Essentials That Save Hours Per Week
1. Prettier (Code Formatter)
Here's the awkward truth: I have opinions about code formatting, and they don't matter. Prettier exists to end wars that were never worth fighting in the first place.
I used to manually format code. I really did. I'd spend 10 minutes getting indentation "just right" and feel productive. Now? I hit save, Prettier runs, and I move on with my life. Zero seconds wasted. The extension integrates so cleanly that you literally forget it's there—until you realize you haven't thought about semicolons in three years.
What surprised me: the peace of mind. When you're pairing or reviewing code, nobody argues about spacing. It's all automatic.
2. ESLint
ESLint catches stupid mistakes before they become bugs. Unused variables. Unreachable code. That one console.log you forgot to delete before pushing to production (we've all been there).
I used to think linters were overkill. Too many warnings. Too much noise. But modern ESLint—configured properly—is surgical. It catches real errors without being a nag. When you see that red squiggle, you *should* fix it.
Fair warning: setup takes 20 minutes if you've never done it. But your future self will thank present-you.
3. Thunder Client (API Testing)
I used to jump between VS Code and Postman like an idiot. Open Postman. Make the request. Check the response. Copy the response into a JSON file. Close Postman. Back to Code.
Thunder Client lives inside VS Code. You test APIs without leaving your editor. It's not trying to be Postman Pro. It's trying to save you 30 seconds per request. Over a day of coding, that's real time.
Insomnia and REST Client are alternatives if you're loyal to another workflow, but Thunder Client just works for most people.
The Productivity Multipliers
4. GitHub Copilot
Okay, controversial take incoming: Copilot isn't magic. It's really, really good at boilerplate and repetitive patterns. It's awful at complex logic. I don't trust it to write the core algorithm—I trust it to write the boring 80% of the code.
The learning curve is negative. You literally just start typing and it suggests completions. You press Tab to accept. That's it. It does hallucinate sometimes (generates code that looks plausible but is completely wrong), so you can't just accept everything blindly. But when it works? It's like pair programming with someone who knows your codebase.
Cost: $10/month or free if you're a student. Not free otherwise, which eliminates it for some people. But I've calculated it saves me about 3-4 hours per week on average. For me, that's worth it.
5. GitLens
GitLens shows you who wrote every line of code. Sounds useless? Try debugging a weird function and wondering why someone made that decision. You hover over the line, GitLens tells you the commit message. Suddenly everything makes sense.
It also has blame annotations, commit history, and repository insights. The free version covers 90% of what you actually need. The premium features are nice but not essential.
I used to alt-tab to GitHub or run git blame in the terminal. This is just faster.
6. Path Intellisense
This autocompletes file paths. Sounds small. Is small. Saves about 30 keystrokes per day. You're typing `import { something } from '../../../utils/he` and Path Intellisense suggests the full path. Press Tab. Done.
Not flashy. Not expensive. Just removes friction.
The Specialized Tools That Unlock Workflows
7. Peacock (Color Workspaces)
This one's weird but I'll explain why it matters.
When you're juggling five VS Code windows (frontend repo, backend repo, docs, config, experimental project), your brain burns cycles just figuring out which window is which. Peacock colors the entire interface. Frontend is blue. Backend is red. Docs is green. Your brain doesn't have to think anymore.
This is especially useful in remote work situations where you're constantly context-switching. It sounds trivial until you realize you've opened the wrong repo four times in a morning and wasted an hour of work.
8. REST Client (Lightweight API Testing)
Simpler than Thunder Client. You write .http or .rest files with plain text requests. Open the file. Click "Send Request" above each endpoint. Results appear in a panel. Clean. Scriptable. Version-controllable (unlike Postman collections stored in some cloud).
It's my backup when Thunder Client feels overkill. Some teams prefer REST Client because the requests are literally text files that live in the repo.
9. Live Server (Quick Local Testing)
For frontend work: you edit HTML. You save. The browser auto-refreshes. That's it. No terminal commands. No webpack watching. No build step if you're just testing static files or basic JavaScript.
Use it for rapid prototyping. Use it for teaching. Use it for debugging. It's not for production workflows, but it's perfect for the other 80% of the time.
10. Markdown Preview Enhanced (Documentation)
If you write README files, API docs, or any markdown in VS Code, the built-in preview is... adequate. This extension is prettier, faster, and supports more features (tables, code highlighting, mermaid diagrams, LaTeX).
I write a lot of documentation. This extension convinced me to write *more* documentation because it's now pleasant to work with.
Quick Comparison
| Extension | Primary Use | Cost | Setup Time |
|---|---|---|---|
| Prettier | Code formatting | Free | 2 min |
| ESLint | Error detection | Free | 15 min |
| GitHub Copilot | Code generation | $10/mo | 3 min |
| Thunder Client | API testing | Free | 1 min |
| GitLens | Git integration | Free | 1 min |
| Path Intellisense | File path completion | Free | 1 min |
| Peacock | Workspace coloring | Free | 2 min |
| REST Client | API testing | Free | 1 min |
| Live Server | Local development | Free | 1 min |
| Markdown Preview Enhanced | Documentation | Free | 1 min |
My Take
Here's what surprised me: the best extensions don't add flashy new features. They remove friction. Prettier removes formatting arguments. ESLint removes surprise bugs. GitLens removes the need to context-switch to GitHub.
What disappointed me? Most of the "AI-powered" extensions beyond Copilot are either vaporware or solving problems that don't exist. I tested about fifteen over-engineered extensions that promised to revolutionize my workflow. None of them stuck.
This list is what I actually use. Not what's popular. Not what everyone recommends. Copilot is the only paid one in my core setup (and it's optional—plenty of developers skip it on principle). The rest are battle-tested, boring, and effective. They work on Windows, Mac, and Linux. They work for JavaScript, Python, Go, whatever you're coding.
If you're a student or freelancer on a budget, you can get 90% of the value with just Prettier, ESLint, GitLens, and Path Intellisense. Total time to setup: under 10 minutes. Total cost: $0. That's a reasonable foundation.
Verdict
Install Prettier first. Seriously. It'll change how you think about code formatting. Then add ESLint if you're doing JavaScript. Then GitLens if you work with teams or need to understand code history.
Everything else depends on your specific needs. Frontend developer? Add Live Server. API work? Add Thunder Client or REST Client. Writing documentation? Add Markdown Preview Enhanced. Juggling five projects? Add Peacock.
The extensions in this list have all been around for at least 2-3 years, which means they're stable and actively maintained. They're not going anywhere. You won't wake up next month and find that the developer abandoned it.
Don't treat this as gospel. Your workflow is probably different from mine. But use this as a starting point. Test these. See what sticks. After six months, you'll have your own list of ten that fits how you actually code—not how someone on the internet codes.
Published by Dattatray Dagale • 26 June 2026
0 Comments