Ultimate web developer setup 2026: VS Code

This is the first of three setup guides, one per editor worth your attention in 2026. The other two cover Sublime Text, the fast one you pay for, and Zed, the new one built by Atom's creators as an apology. We start with VS Code because, statistically, you're already using it.

VS Code won the editor wars years ago, and it won them the boring way: free, cross-platform, good enough at everything, with an extension for anything. Which is exactly why the "ultimate setup" for it in 2026 is not what it was in 2019. Back then the game was addition, stacking extensions until your editor could do everything. VS Code has absorbed so many former must-have extensions into the core product that most setup guides are recommending you install things it already does. The ultimate VS Code setup is a fast one, and fast means minimal.

First, uninstall

Before adding anything, audit what you've accumulated. Open the Extensions panel and be honest. Auto Close Tag and Auto Rename Tag: built in for years (editor.linkedEditing handles the renaming). Bracket pair colourisation: built in, and the native version is dramatically faster than the old extension. Path autocomplete for imports: largely built in via IntelliSense. Every extension you keep runs code in your editor's process, and a bloated VS Code gives away the one advantage it has left over the two faster editors in this series. If you haven't invoked an extension in a month, it's not part of your setup, it's bloat.

The extensions that still earn a place

Six, for a typical front-end or full-stack web workflow:

• Prettier, set as your default formatter with format-on-save. Arguing about formatting is a hobby; Prettier is a decision. If your project uses Biome instead, install that and skip Prettier, but pick exactly one.
• ESLint, wired to your project config, so problems appear where you're typing rather than in CI twenty minutes later.
• Error Lens, which prints errors inline at the end of the offending line instead of hiding them in hover tooltips. The single biggest quality-of-life extension on this list.
• GitLens, mainly for line-by-line blame and history. The free tier does everything most people need.
• Tailwind CSS IntelliSense, if you use Tailwind. Non-negotiable if so, pointless if not, which is a decent summary of Tailwind generally.
• Code Spell Checker, because recieve in a variable name will otherwise outlive your employment.

That's the lot. Notice what's absent: no Live Server (Vite's dev server replaced it in any modern project), no themes-of-the-week, no AI extensions beyond whatever your team has standardised on. Copilot is built into the product now and switched on or off in one place; treat AI assistance as a team decision, not an extension impulse buy.

Settings worth changing

Everything else lives in settings.json. The defaults are sensible; these are the deviations that pay rent:

{
  "editor.formatOnSave": true,
  "editor.defaultFormatter": "esbenp.prettier-vscode",
  "editor.linkedEditing": true,
  "editor.stickyScroll.enabled": true,
  "editor.fontFamily": "JetBrains Mono",
  "editor.fontLigatures": true,
  "files.trimTrailingWhitespace": true,
  "explorer.compactFolders": false,
  "workbench.editor.limit.enabled": true,
  "workbench.editor.limit.value": 8
}

Sticky scroll pins the current function's signature to the top of the viewport while you scroll its body, and once you've had it you won't go back. The editor tab limit stops the fifteen-open-tabs situation that everyone claims not to have. JetBrains Mono is free and easier on the eyes across a long day than the default; Fira Code if you prefer your ligatures more stylised.

One structural feature worth adopting in 2026: Profiles. VS Code lets you keep separate named profiles, each with its own extensions and settings, so your writing setup doesn't load your debugging toolchain and vice versa. It's the sanctioned answer to extension sprawl, and almost nobody uses it.

Learn the editor you already have

The ultimate setup is mostly the ultimate user. Four things that repay an afternoon: the command palette (Ctrl/Cmd+Shift+P) for everything you currently hunt through menus for; Ctrl/Cmd+D to select the next occurrence of the current word, which turns most repetitive edits into one fluent motion; Ctrl/Cmd+P to jump to any file by fuzzy name, because the file tree is for orientation, not navigation; and the built-in source control view, which handles staging, committing and conflict resolution well enough that you may not need a separate Git client at all.

Where VS Code loses

Honesty section, because every editor in this series gets one. VS Code is an Electron app, and no amount of tuning changes that. On a big machine you won't care. On a modest laptop, you will feel the weight: slower startup, higher memory, occasional input latency at exactly the moments you're most impatient. The two companion articles in this series exist because of that paragraph. If what you want is the fastest possible pure editing experience and you'll pay for it, that's the Sublime Text article. If you want VS Code's modern feature set rebuilt natively for speed, with AI designed in rather than bolted on, that's the Zed one.

But if you stay, and most of you will, stay deliberately. The default editor deserves better than a default setup, and in 2026 the best VS Code setup is the one carrying the least. Install six things, configure ten lines, learn four shortcuts, and delete the rest. Your editor was never the problem. Your 2019 extension list was.