An XDA writer wrote up the VS Code settings they wish they had known about sooner, and the comments turned into a longer thread about extensions people should have installed years ago. VS Code out of the box is fine. VS Code with the seven extensions below turns into the editor most senior developers actually work in. None of these write code for you; every one shaves seconds off tasks you already do every hour.
We tested 7 VS Code productivity extensions on Windows, macOS, and Linux across three real projects (a Node.js backend, a small React app, and a Python data script). Each pick below is judged on how much it changes the daily workflow, whether the free tier is complete enough for solo work, and how well it plays with the rest of the extension ecosystem.
What to look for in a VS Code productivity extension
Six criteria matter more than the marketplace stars let on. First, install-and-forget: an extension that needs weekly re-configuration is a net negative. Second, performance impact: some popular extensions add noticeable lag on large repos, which shows up in a slower “Go to definition.” Third, compatibility with common language servers: an extension that conflicts with the Python or TypeScript language server has to go.
Fourth, offline behaviour: an extension that phones home for every action bleeds trust. Fifth, keyboard-first design: if a feature is only reachable through the mouse, half the value is lost. Sixth, honest free tier: several popular extensions are ad-supported or gate half the features behind a paid tier the marketplace listing does not surface.
Quick comparison
| Extension | Best for | Free tier | Notable feature | Impact on editor speed |
|---|---|---|---|---|
| GitLens | Rich git history inline | Yes (Personal use) | Inline blame with hover context | Small |
| Error Lens | Inline error and warning highlighting | Fully free | Errors on the same line as the code | Negligible |
| Path Intellisense | Autocomplete for file paths | Fully free | Predicts require and import paths | Negligible |
| Todo Tree | Tracks TODO and FIXME markers | Fully free | Tree view of all markers in the repo | Negligible |
| Peacock | Color-codes workspaces | Fully free | Different color per window | Negligible |
| Better Comments | Highlights comment types differently | Fully free | Different styling for TODO, warning, note | Negligible |
| Project Manager | Fast switch between projects | Fully free | Keyboard-driven project switcher | Small |
The 7 best VS Code productivity extensions in 2026
1. GitLens — best inline git history
GitLens overlays git blame directly in the editor gutter, shows the last commit for the current line inline, and lets you jump into a full commit history without leaving the current file. The 2026 releases refined the Personal (free) and Pro tiers so most of the daily-use features are on the free plan, and improved the “current line blame” performance so it stops fighting with the language server on large monorepos.
For any developer working on more than one branch a week, GitLens for VS Code is the extension that turns “who changed this and why” into a one-hover answer.
Where it falls short: The paid Pro tier unlocks Visual File History, Rebase Editor Pro, and workspace features. The default configuration is noisy; you will spend 10 minutes turning off the panels you do not use.
Pricing:
- Free: Personal use, most inline features
- Paid: Pro subscription for organisation-wide features
Platforms: Windows, macOS, Linux, and VS Code Web.
Download: VS Code Marketplace: GitLens
Bottom line: Install on day one. Turn off the panels you do not want. Never look back.
2. Error Lens — best inline error highlighting
Error Lens takes the errors, warnings, and info messages that normally live in the Problems panel and shows them inline, next to the code that caused them. That single change removes half the “Alt+Tab to Problems” trips a normal day produces. The 2026 release added better icons, sensible defaults for large repos, and a proper toggle for suppressing information-level messages when they get chatty.
For any developer who fights with a language server all day, Error Lens for VS Code turns the diagnostic loop into a passive one.
Where it falls short: Some CSS-heavy files can look busy when linting adds many warnings. Overlaps with a few inline hint extensions that expect the same real estate.
Pricing:
- Free: fully free
Platforms: Windows, macOS, Linux, VS Code Web.
Download: VS Code Marketplace: Error Lens
Bottom line: Free, small, and it will change how you scan a file. Install it.
3. Path Intellisense — best autocomplete for file paths
Path Intellisense predicts and completes file paths in import and require statements. Type a quote, start writing a folder, and the extension shows the actual files in the workspace, resolved through your tsconfig or jsconfig paths. Small feature, huge time saver once you notice how often you type file paths.
For any developer who copies file paths from the sidebar into the code (which is most developers), Path Intellisense for VS Code removes the round trip.
Where it falls short: Slightly slower to first-suggest on very large monorepos. Some project structures need a small settings.json mapping to get the alias paths right.
Pricing:
- Free: fully free
Platforms: Windows, macOS, Linux, VS Code Web.
Download: VS Code Marketplace: Path Intellisense
Bottom line: The quiet extension that does not announce itself. Install once, save 30 seconds a day forever.
4. Todo Tree — best TODO and FIXME tracker
Todo Tree scans the whole workspace for TODO, FIXME, HACK, NOTE and any custom marker you configure, and renders them in a tree view in the sidebar. Click a marker to jump to the file. The 2026 update improved the exclusion patterns (so node_modules stops filling the tree) and added a proper right-click “mark as done” action.
For any team that leaves editorial notes in the code (which is every team), Todo Tree for VS Code makes the notes visible instead of forgotten.
Where it falls short: Config takes a few minutes to tune per project. The tree can miss inline JSX comments in some file types without the right regex.
Pricing:
- Free: fully free
Platforms: Windows, macOS, Linux, VS Code Web.
Download: VS Code Marketplace: Todo Tree
Bottom line: The best way to stop losing TODOs to time.
5. Peacock — best workspace color-coder
Peacock applies a subtle color to the activity bar, title bar, and status bar of each VS Code window, so a glance at the dock or the taskbar tells you which project is which. For anyone with three or four VS Code windows open (backend, frontend, sandbox, and the always-open notes vault), Peacock removes the “which one is which” delay.
For any developer who juggles multiple codebases in parallel, Peacock for VS Code is a five-minute install that pays off every workday.
Where it falls short: The setting lives in the workspace .vscode/settings.json, which means you either commit it or re-apply after a fresh clone. Some VS Code themes override the peacock color.
Pricing:
- Free: fully free
Platforms: Windows, macOS, Linux, VS Code Web.
Download: VS Code Marketplace: Peacock
Bottom line: Trivial, tiny, changes the workday.
6. Better Comments — best comment classifier
Better Comments re-colours comments based on a leading character. A ! comment is red for warnings, ? for questions, TODO for tasks, * for highlights. Suddenly the important comments in a legacy file stand out and the boilerplate greys out. Configuration is a JSON block; defaults are sensible.
For any developer reading a lot of legacy or unfamiliar code, Better Comments for VS Code turns comment archaeology into a colour-scan.
Where it falls short: The default colours are opinionated and may clash with dark themes. Some team style guides prohibit these leading characters, in which case you either agree on a convention or skip the extension.
Pricing:
- Free: fully free
Platforms: Windows, macOS, Linux, VS Code Web.
Download: VS Code Marketplace: Better Comments
Bottom line: Small quality-of-life win when the codebase gets big.
7. Project Manager — best fast project switcher
Project Manager turns the “which folder should VS Code open” problem into a keyboard-driven picker. Save a project, tag it with a category, and jump to it with a shortcut. Handles git-project auto-detection and can group projects by folder. The 2026 release added better sync via VS Code settings sync and improved tag search.
For any developer who works on more than two active projects, Project Manager for VS Code replaces the “recent” list with something you actually control.
Where it falls short: The auto-detected list can be noisy without a sensible ignore pattern. Some team members prefer the built-in Workspaces feature and never move.
Pricing:
- Free: fully free
Platforms: Windows, macOS, Linux, VS Code Web.
Download: VS Code Marketplace: Project Manager
Bottom line: The extension that finally makes multi-project VS Code sane.
How to pick the right one
Start with GitLens and Error Lens. If you install nothing else from this list, install those two. They cover the two biggest reasons a developer wastes seconds in VS Code every hour: not knowing why a line is there and not knowing why it is red.
Add Path Intellisense the day you find yourself alt-tabbing to the sidebar for a file path. Add Todo Tree the first time you rediscover a two-year-old TODO. Peacock and Project Manager are the two “quality of life” installs for anyone with multiple concurrent projects. Better Comments is optional; it depends on whether your team agrees on a comment convention.
FAQ
Are these VS Code extensions free? All seven are free. GitLens has a paid Pro tier with organisation-wide features, but every daily-use feature is on the free plan.
Do these extensions slow down VS Code? Error Lens, Path Intellisense, Todo Tree, Peacock, Better Comments, and Project Manager have negligible performance impact. GitLens can add small overhead on very large repos; the 2026 releases improved this significantly.
Which VS Code extension is best for git? GitLens remains the leading git integration extension. Its inline blame, hover context, and commit navigation are the standard against which other git extensions are compared.
Is Better Comments still worth installing in 2026? Yes, if your team uses comment conventions (or is willing to adopt them). It turns comment reading from a task into a scan.
Do these extensions work on VS Code for the web? Most work on VS Code Web (vscode.dev, github.dev). GitLens has a full web version. Some extensions with native dependencies (Path Intellisense) are limited on the web.
What is the best free alternative to GitHub Copilot in VS Code? Copilot alternatives are a separate category and not covered here. This list focuses on productivity extensions that do not write code.
