DEV Community

Orbit Websites
Orbit Websites

Posted on

Top Free VS Code Extensions for Developers in 2026

Top Free VS Code Extensions for Developers in 2026

Let’s be real — your editor is your second home. If you're spending 8+ hours a day in VS Code, you better make it fast, smart, and tailored to your workflow. In 2026, the extension ecosystem is richer than ever, but most devs still only use the obvious ones. Here are the free extensions I actually use daily — the ones that save keystrokes, prevent bugs, and keep me from going insane.

No fluff. No sponsored picks. Just tools that make coding less tedious.


1. Error Lens — See Errors Inline, Not in Panels

You know that moment when you fix one error, save, and get 10 new ones in the Problems tab? Yeah, me too. Error Lens changes that by showing errors and warnings right next to the code.

![Error shown inline under a line of code]

No more hunting through the Problems panel — it’s right there.

Install it and forget it. It works out of the box with TypeScript, Python, ESLint, and most linters.

// Optional: tweak severity display in settings.json
{
  "errorLens.enabledDiagnosticLevels": ["error", "warning", "info"],
  "errorLens.fontStyle": "underline wavy #ff0000"
}
Enter fullscreen mode Exit fullscreen mode

Why it matters: Immediate feedback > context switching.


2. CodeSnap — Share Clean Code Snippets (No More Screenshot Cropping)

Need to paste code in Slack, email, or a PR? Stop using Cmd+Shift+4. CodeSnap generates beautiful, syntax-highlighted images with one click.

  • Preserves your theme
  • Removes line numbers if you want
  • Copies to clipboard as PNG

Right-click in your editor → “Capture Code Snippet”. Done.

No more blurry screenshots or manually formatting code blocks.


3. Todo Tree — Never Lose Track of // TODO Again

We all leave // TODO comments. Most of them rot. Todo Tree aggregates them into a searchable sidebar.

// TODO: Refactor this mess before launch
// FIXME: API returns 500 on empty payload
// HACK: Temp fix for timezone bug — revisit
Enter fullscreen mode Exit fullscreen mode

After installing:

  • Open the Todo Tree view (Ctrl+Shift+P → “Todo Tree: Focus on Tree View”)
  • It instantly scans your project

You can customize tags and colors in settings:

"todo-tree.highlights.defaultHighlight": {
  "type": "text",
  "background": "#FF9900",
  "foreground": "#000"
},
"todo-tree.general.tags": ["TODO", "FIXME", "HACK", "BUG"]
Enter fullscreen mode Exit fullscreen mode

Pro tip: Use it with GitLens to see who added the TODO and when.


4. Prettier + EditorConfig — Enforce Consistency Without Arguments

Arguing about tabs vs spaces? Indent size? Line endings? Stop. Use Prettier and EditorConfig for VS Code together.

Install both, then add .editorconfig:

root = true

[*]
indent_style = space
indent_size = 2
end_of_line = lf
charset = utf-8
trim_trailing_whitespace = true
insert_final_newline = true

[*.md]
max_line_length = 0
trim_trailing_whitespace = false
Enter fullscreen mode Exit fullscreen mode

And .prettierrc:

{
  "semi": true,
  "trailingComma": "es5",
  "singleQuote": true,
  "printWidth": 80
}
Enter fullscreen mode Exit fullscreen mode

Now, every team member formats code the same way — no PR comments about whitespace.

Enable format-on-save:

// settings.json
{
  "editor.formatOnSave": true,
  "editor.defaultFormatter": "esbenp.prettier-vscode"
}
Enter fullscreen mode Exit fullscreen mode

5. Better Comments — Make Comments Actually Useful

Most comments are noise. Better Comments helps you write ones that matter by color-coding based on prefixes.

// Just a regular comment (gray)

// TODO: Need to validate input here (red)

// ? Is this the best approach? (blue)

// ! This will break if user is null (bold red)

// FIXME: Temp workaround — remove after API update (yellow)
Enter fullscreen mode Exit fullscreen mode

It’s trivial, but it makes code reviews faster. You scan and instantly see what needs attention.

Customize colors in settings if the defaults clash with your theme.


6. GitLens — Git Built Right Into Your Editor

Yes, VS Code has basic Git support. But GitLens is the upgrade you didn’t know you needed.

Features I use daily:

  • Blame annotations on the current line
  • Commit lens — see who changed what and when
  • Compare branches visually
  • Undo last commit without touching the terminal

Hover over any line:

const user = getUser(id); // Joe (2 commits ago): "Fix null user crash"
Enter fullscreen mode Exit fullscreen mode

Also: Ctrl+Shift+P → “GitLens: Open Changes with Previous Revision” to diff against any commit.

If you’re still typing git log -p to figure out why something broke, you’re wasting time.


7. Thunder Client — No More Postman for Simple APIs

I used to switch to Postman or curl. Now I use Thunder Client — a lightweight REST client built into VS Code.

  • Send GET/POST/PUT requests

Professional

Top comments (0)