10 Essential Free VS Code Extensions for Developers in 2026: Boost Your Productivity
Let’s be real — your editor is your workspace. If you're spending 8+ hours a day in VS Code, you better make it work for you. In 2026, the ecosystem is richer than ever, but most devs still over-install and under-optimize. I’ve trimmed my setup down to the essentials: tools that save keystrokes, reduce context switching, and actually improve code quality — all for $0.
Here are 10 free extensions I use daily across frontend, backend, and infrastructure work. No hype. No bloat. Just productivity.
1. Prettier - Code Formatter
Auto-formatting isn’t optional anymore. Prettier ensures consistent code style across your team without PR debates.
Install it, then add this to your .vscode/settings.json:
{
"editor.defaultFormatter": "esbenp.prettier-vscode",
"editor.formatOnSave": true,
"editor.formatOnPaste": false
}
Pair it with a .prettierrc config and forget about whitespace wars.
Pro tip: Use
Shift+Alt+Fto format on demand. Works on JS, TS, CSS, JSON, Markdown — and now even HTML in Svelte and Vue.
2. ESLint
Prettier handles formatting. ESLint catches bugs. Use both.
Install dbaeumer.vscode-eslint, then ensure ESLint is in your project:
npm install eslint --save-dev
npx eslint --init
VS Code will underline issues in real time. No need to wait for CI.
Bonus: Add this to auto-fix on save:
{
"editor.codeActionsOnSave": {
"source.fixAll.eslint": true
}
}
Now unused vars, bad promises, and console.log slips get caught before commit.
3. GitLens — Supercharge Git Inside VS Code
Git blame, history, and code ownership should be one click away. GitLens does that — and more.
Hover over any line and see who changed it and when. Jump to the commit. Compare branches visually.
It also adds code lens links above functions:
// [15 days ago] @jane - Refactored for performance
function processUserData(user) { ... }
No more git log --oneline -S "function name" in terminal.
Use
Ctrl+Shift+Gto open the Git graph. Filter by branch, author, or file. It’s like GitKraken, but inside your editor.
4. Error Lens
Why scroll through the Problems tab when errors can highlight themselves?
Error Lens underlines and inlines errors and warnings right in your code:
const result = someAsyncCall(); // [Promise is not awaited] - Use await or .catch()
It’s subtle but game-changing. You see issues in context.
Works with ESLint, TypeScript, Python linters, and more.
Install
usernamehw.errorlens. No config needed. Just works.
5. Bracket Pair Colorizer (Built-in Now, But Enable It!)
Wait — this isn’t an extension anymore? Correct. As of 2025, it’s baked into VS Code. But most people don’t turn it on.
Add this to your settings:
{
"editor.bracketPairColorization.enabled": true,
"editor.guides.bracketPairs": "active"
}
Now nested brackets light up in matching colors. No more “which } closes this if?” at 2 a.m.
Pair with Indent Rainbow (
oderwat.indent-rainbow) for even clearer nesting.
6. Thunder Client
Tired of switching to Postman or curl for API testing? Thunder Client is lightweight, fast, and lives right in VS Code.
Send GET, POST, auth headers, and even save collections — all without leaving your editor.
POST https://api.example.com/users
Content-Type: application/json
Authorization: Bearer xyz123
{
"name": "John Doe",
"email": "john@example.com"
}
Use
Ctrl+Alt+Tto open it. Great for testing local backends during full-stack dev.
7. Code Runner
Need to test a quick JS snippet or Python script? Code Runner executes code files in-place.
Select a block:
console.log([1, 2, 3].map(x => x ** 2));
Right-click → “Run Code”, and output appears in the output panel.
Supports 30+ languages: Node, Python, Ruby, Go, even PowerShell.
Set it to use integrated terminal:
{
"code-runner.runInTerminal": true
}
Avoids output truncation and lets you interact with scripts.
8. Path Intellisense
How many times have you typed ./src/compon... and guessed the folder name?
Path Intellisense auto-completes file paths in imports:
import Header from './components/Header'; // Autocompletes as you type
No more “Module not found” from a typo in a path.
Works with
.js,.ts,.jsx,.tsx, and even image imports.
9. Todo Tree
Find all your // TODO: and // FIXME: comments in
☕ Playful
Top comments (0)