Before we start — a warning.

This isn't one of those lists where I throw 25 extension logos at you and call it a day. There are over 50,000 extensions in the VS Code marketplace. Most of them are garbage. Some duplicate features that are already built in. Some haven't been updated since 2021 and are silently slowing your editor down right now.

This list is 10. Intentionally. Because a bloated extension setup is its own kind of technical debt.

Let's get into it — opinions included.

1. ESLint — Non-Negotiable

The take: If you're writing JavaScript or TypeScript without ESLint running in your editor, you're just sending bugs to code review instead of catching them yourself.

ESLint enforces your project's coding rules in real-time, flags problems as you type, and saves your team hours of review comments on things a machine should be catching. It's been around forever and it's still irreplaceable.

Unpopular opinion: Most developers have ESLint installed but misconfigured. Default rules are nearly useless. The value comes from setting up rules that match your actual project. If you haven't touched your .eslintrc in six months, you're not really using ESLint.

2. Prettier — Just Let It Format Your Code

The take: Code formatting debates are a waste of everyone's time. Tabs vs spaces, semicolons or not, single quotes or double — none of it matters as long as the whole team is consistent. Prettier enforces consistency automatically on save. End of discussion.

Unpopular opinion: If your team is still arguing about formatting in 2026, that's a culture problem, not a tooling problem. Install Prettier, set "editor.formatOnSave": true, and move on to actual work.

3. GitLens — Git Blame That Doesn't Make You Leave the Editor

The take: GitLens is the most downloaded Git extension for VS Code for a reason. Inline blame annotations showing who changed each line and when, interactive commit graphs, file history — all without leaving your editor. The free tier covers everything most developers will ever need.

Unpopular opinion: If your first reaction to a bug is "whose fault is this?" rather than "how do we fix this?", GitLens will make you a better developer or a more toxic teammate. Depends entirely on you.

4. Error Lens — Errors Where You Actually Look

The take: By default, VS Code shows errors in the Problems panel at the bottom of the screen. Nobody is looking at the bottom of the screen. Error Lens moves error messages inline, right next to the line that caused them. It sounds minor. It's not. Once you use it, going back feels broken.

Unpopular opinion: This should be VS Code's default behavior. The fact that it's an extension in 2026 is a minor embarrassment for Microsoft.

5. GitHub Copilot — But Not For the Reason You Think

The take: GitHub Copilot is the most widely adopted AI coding assistant in VS Code. It does more than autocomplete now — it writes full functions, generates tests, and handles natural language to code. For repetitive code, boilerplate, and "I know what I want but don't want to type it" moments, it's genuinely fast.

Unpopular opinion: Copilot is making junior developers worse at problem-solving and senior developers lazier about documentation. The productivity gain is real. The skill atrophy is also real. Use it intentionally, not reflexively. And always read what it generates before you ship it — 45% of AI-generated code contains at least one security vulnerability.

6. Thunder Client — Because Postman Got Too Big for Its Own Good

The take: Thunder Client is a lightweight REST API client built directly into VS Code. Test your endpoints without leaving your editor, without opening another app, without waiting for Postman to load.

Unpopular opinion: Postman in 2026 is bloatware. What started as a simple API testing tool is now a platform with workspaces, teams, flows, and a pricing page with four tiers. Thunder Client does 90% of what most developers actually need in a fraction of the weight. If you're still defaulting to Postman out of habit, try Thunder Client for a week.

7. Tailwind CSS IntelliSense — If You're Using Tailwind, This Is Mandatory

The take: Autocomplete, syntax highlighting, and linting for Tailwind classes directly in your editor. Hovering over a class shows you the exact CSS it generates. This extension makes Tailwind actually pleasant to write.

Unpopular opinion: Tailwind itself is still controversial and that's fine. But if your team has decided to use it, not having this extension is just self-inflicted pain. Arguments about whether Tailwind is good belong in a different article.

8. Path Intellisense — The Smallest Extension With the Highest Return

The take: Autocompletes file paths as you type import statements. That's it. It's tiny, it's fast, and it eliminates an entire category of annoying errors — the ones where you typed ../components/Button when you meant ../../components/Button.

Unpopular opinion: This is the most underrated extension on this list. Nobody talks about it. Everyone who installs it wonders how they lived without it.

9. Docker — If Containers Are Part of Your Workflow

The take: The official Docker extension for VS Code lets you manage containers, images, volumes, and networks directly from the editor. Build, run, inspect logs, and exec into containers without touching the terminal for Docker commands.

Unpopular opinion: If you're running Docker in 2026 without this extension, you're memorizing commands you don't need to memorize. That mental space could go toward something more interesting.

10. VS Code Icons — Last On The List, Not Least

The take: Replaces VS Code's default file icons with a comprehensive set that makes different file types visually distinct at a glance. Python files look different from JavaScript files. Config files are obvious. It sounds cosmetic. It's actually a real time saver when navigating large projects.

Unpopular opinion: Developers who dismiss visual organization as "unimportant" are the same ones who spend 10 seconds finding a file they've opened before. Your environment shapes how you work. Make it work for you.

The Extensions That Didn't Make the List (And Why)

• Bracket Pair Colorizer — VS Code has had built-in bracket pair colorization since 2021. You don't need the extension anymore.
• Auto Close Tag / Auto Rename Tag — Built into VS Code for HTML and JSX. Check your settings before installing.
• Live Share — Great concept, unstable in practice. If you're pair programming regularly, a purpose-built tool handles it better.
• indent-rainbow — Pretty. Doesn't solve a real problem. Skip it.

The Rule Behind This List

Before you install any extension, ask yourself three things:

1. Does VS Code already do this natively?
2. When was the last update? (Anything not updated in 12+ months is a risk)
3. Will I actually use this daily, or is it just satisfying to install?

A tight extension setup makes VS Code fast, focused, and actually pleasant to work in. Every extension you add is a trade-off. Make them deliberately.

Which extensions am I wrong about? Drop it in the comments — I want the pushback.