Top 20 VS Code Extensions Every Developer Should Install in 2026
A curated, opinionated list of the 20 best VS Code extensions in 2026, grouped by what they actually do for you. Skip the bloat, install only what helps, and turn Visual Studio Code into a sharper daily driver.
The reason VS Code won the editor war is its extension marketplace. With more than 60,000 extensions in 2026, you can shape the editor into anything — a Python data-science notebook, a Rust IDE, a database client, a Postman replacement. The catch: install too many and the editor crawls. Install the wrong ones and they fight each other.
This is a tight, opinionated list of 20 extensions that earn their keep on almost any developer's machine in 2026. They are organised by purpose so you can pick what you actually need. None of them are bloated, all are actively maintained, and most are free.
Code Quality and Formatting
These four belong on every machine, regardless of language.
1. Prettier — Code formatter. The opinionated formatter for JavaScript, TypeScript, JSON, CSS, HTML, Markdown, and YAML. Enable editor.formatOnSave and never argue about whitespace again.
2. ESLint. Inline lint warnings for JavaScript and TypeScript. Pairs perfectly with Prettier — Prettier formats, ESLint catches bugs and bad patterns.
3. EditorConfig for VS Code. Reads .editorconfig files and matches indentation and line endings to whatever the project uses. Saves you from "wait, is this 2 spaces or 4?" every time you switch repos.
4. Error Lens. Surfaces errors and warnings inline on the same line, instead of hiding them in a hover. Once you try it you cannot go back.
AI and Pair Programming
The category that changed the most since 2023.
5. GitHub Copilot + GitHub Copilot Chat. The default AI pair-programmer — autocomplete, chat, agent mode, code review. Free for students and most open-source maintainers; cheap for individuals.
6. Continue. Open-source AI assistant that lets you bring your own model — Claude, GPT, local Llama via Ollama. Great if you want privacy or model choice.
Git and Source Control
VS Code's built-in Git is good; these make it great.
7. GitLens. Inline blame, file history, branch comparisons, commit graph. The single best Git extension ever made.
8. GitHub Pull Requests. Review and merge PRs without leaving the editor — diffs, comments, status checks all inside VS Code. Pairs with Git Branching, Merging & Pull Requests.
9. Git Graph. A visual commit graph for any repo. Especially useful for understanding messy merge histories.
Web Development
10. Tailwind CSS IntelliSense. Autocomplete, hover previews, and lint warnings for Tailwind classes. Essential if your stack uses Tailwind.
11. Auto Rename Tag. Renames the closing HTML/JSX tag when you rename the opening one. Tiny extension, huge daily wins.
12. Live Server. One-click local development server with live reload for static HTML/CSS/JS. Perfect for tutorials and quick prototypes.
Language Support
Pick the ones that match your stack — none of them are bloated.
13. Python + Pylance. Microsoft's official Python pair — type-checking, debugging, Jupyter, virtual env detection. The standard for Python in VS Code.
14. rust-analyzer. First-class Rust language server. Inlay hints, refactors, fast type-checking. The Rust experience in VS Code rivals JetBrains.
15. Go. The official Go extension — testing, debugging, gopls integration. Set it up once and forget about it.
Productivity and Quality of Life
16. Path Intellisense. Autocompletes file paths in import statements. Saves countless typos.
17. Code Spell Checker. Catches typos in identifiers, strings, and comments. You will be surprised how many slip through code review.
18. TODO Tree. Aggregates TODO, FIXME, HACK comments across your repo into a single side panel. Stops technical debt from disappearing.
Working with Data and APIs
19. REST Client. Write .http files with GET, POST, PUT requests and run them inline. Postman alternative that lives in your repo and gets committed to git.
20. Database Client. Connect to PostgreSQL, MySQL, SQLite, MongoDB, Redis from inside VS Code. Browse tables, run queries, edit rows — never alt-tab to a separate DB tool again.
How to Pick the Right Subset
You do not need all 20. A reasonable starter pack:
- Universal: Prettier, ESLint, Error Lens, EditorConfig.
- Git: GitLens, GitHub Pull Requests.
- AI: GitHub Copilot (or Continue).
- Plus 1–3 language-specific extensions for whatever you actually write.
That is around 8–10 extensions, and your VS Code will feel light and powerful. Add others when you hit a real need, not before.
Common Mistakes Beginners Make
- Installing 50+ extensions on day one. Each one adds startup time and memory. Install only what you actively use.
- Running two formatters simultaneously. Prettier + a language-specific formatter often conflict. Pick one per file type and disable the others.
- Forgetting to enable format-on-save. Without it, half of these extensions are wasted.
- Not reading extension permissions. Some marketplace extensions are sketchy — stick to publishers with high install counts and recent updates.
- Skipping
.vscode/extensions.json. Add a recommended-extensions file to your repo so the whole team gets the same setup.
Quick Reference
- Browse extensions:
Cmd+Shift+X, then search. - Show running extensions: Command Palette → "Developer: Show Running Extensions" — find what is slowing you down.
- Recommend extensions to your team:
.vscode/extensions.jsonwith arecommendationsarray. - Disable per-workspace: extension → cog → "Disable (Workspace)".
- Profiles: keep different extension sets for web, data, work, personal — bottom-left gear → Profiles.
Rune AI
Key Insights
- A lean ~10-extension setup beats a 50-extension one for speed and stability.
- Universals: Prettier, ESLint, Error Lens, EditorConfig.
- Git workflow: GitLens + GitHub Pull Requests.
- AI: GitHub Copilot or Continue, not both.
- Commit
.vscode/extensions.jsonso the whole team gets the same recommendations.
Frequently Asked Questions
Are these all free?
Will too many extensions slow VS Code down?
What about themes and icon packs?
Should I use both Copilot and Continue?
How do I keep extensions in sync across machines?
Conclusion
The right ten extensions can shave hours off your week. Start with the universal four (Prettier, ESLint, Error Lens, EditorConfig), add GitLens and Copilot, then layer language-specific tools as your stack demands. Trim ruthlessly — a lean VS Code is a fast VS Code.