A colorful coding workspace displays a dark-themed editor beside stacked puzzle-shaped icons on a desk.
Every extension in VS Code costs you something. It adds startup work, takes memory, and gives you one more thing that an update can break. VS Code has also spent years absorbing the jobs of its most popular add-ons. A setup built in 2018 may now carry several extensions that duplicate native features.

How-To Geek's Nimrah Chaudhry listed eight of them. Microsoft's own release notes and documentation back up most of that list. The evidence also shows that "obsolete" is too blunt for a few entries. The better advice is to audit one extension at a time and keep any that still do something the editor can't.

A colorful coding workspace displays a dark-themed editor beside stacked puzzle-shaped icons on a desk. The quick verdict​

ExtensionBuilt-in replacementSafe to drop?
Bracket Pair ColorizerNative bracket pair colorizationYes, for most people
Settings Sync (Shan Khan)Built-in Settings SyncYes, but check its limits
Debugger for Chrome / EdgeBuilt-in browser debuggerYes, for common browser debugging
Auto Close TagBuilt-in HTML auto-closing tagsMaybe, if you need non-HTML languages
Auto Rename TagLinked EditingTest first, especially for JSX and TSX
Local HistoryTimeline local historyYes, for quick recovery
HTML BoilerplateEmmetYes, for standard boilerplate
Git HistorySource Control Graph and TimelineOnly if the native views cover your workflow

Bracket Pair Colorizer​

This is the clearest case. VS Code's August 2021 release (1.60) added native bracket pair colorization. Microsoft's notes say placeholderthe feature was built to fix the performance problems of the popular extension by CoenraadS. The notes also say placeholderthe colors are themeable, with up to six configurable.

Microsoft's engineering write-up explains why a native version beat the extension. placeholderThe extension API couldn't update decorations incrementally, so the extension had to reprocess the whole document on every change. In one test on a TypeScript file of more than 42,000 lines, the extension took about 10 seconds to refresh colors after one bracket was inserted. The core rewrite did the same job in under a millisecond. That is one reported test, not a universal benchmark. The built-in version also works in VS Code for the Web, which the extension couldn't.

What to do: Uninstall the extension and confirm editor.bracketPairColorization.enabled is on. Bracket pair guides are a separate visual aid. They arrived in version 1.61 and are controlled by editor.guides.bracketPairs. Don't confuse the two settings.

Settings Sync​

The built-in feature is unrelated to Shan Khan's extension. Microsoft's documentation says the extension shares settings through a private GitHub Gist, while the built-in version placeholderuses a dedicated service.

The built-in feature first appeared as an Insiders preview in the February 2020 notes for version 1.43. Version 1.48 brought it to Stable as a preview. Microsoft's notes call it a preview there, so I wouldn't describe 1.48 as the "stable" launch.

To turn it on:

  1. Choose Backup and Sync Settings... from the Manage gear or Accounts menu.
  2. Pick the data categories to sync.
  3. Sign in with a Microsoft or GitHub account.

The documentation lists these categories:

  • Settings
  • Keyboard shortcuts
  • Snippets
  • User-level tasks
  • UI state
  • Extensions
  • Profiles
  • Prompts and instructions
  • MCP servers

Limits worth knowing before you remove the old extension:

  • Remote windows: Extensions aren't synced to or from SSH, dev container or WSL windows.
  • Workspace tasks: These aren't synced.
  • Machine-scoped settings: These are excluded by default.
  • Builds: Stable and Insiders use separate sync services unless you choose otherwise.
  • Accounts: Microsoft and GitHub accounts work. GitHub Enterprise Server accounts don't, and neither do Microsoft Sovereign Cloud accounts.
  • Backups: Local backups are deleted after 30 days. The latest 20 remote versions of each category are kept.
  • Size limits: Settings, keyboard shortcuts and user tasks must each be 100 KB or smaller.

If you want a custom backend, you're out of luck. The documentation says custom backends aren't supported.

Debugger for Chrome and Debugger for Edge​

Microsoft's documentation says VS Code includes a built-in debugger for Edge and Chrome. There are three ways to start it.

  • Open Link: Run Debug: Open Link from the Command Palette and enter a URL. If your default browser is Edge, VS Code uses it. Otherwise it looks for Chrome.
  • Launch configuration: Add a launch.json entry with type msedge or chrome. For the file and URL examples, the docs use msedge and tell you to swap in chrome if you prefer it.
  • Integrated browser: Use the editor-browser type to debug inside VS Code itself.

The 1.60 release notes confirm the old standalone debugger was retired. placeholderThey say the legacy debuggers were removed from the product and marked deprecated on the Marketplace. They add that most users, who hadn't opted out of the new JavaScript debugger, would see no change. If you still need the old one, for example to debug Node.js 6, the deprecated extension and the legacy-chrome launch type remain available.

Browser debugging in VS Code works with source maps, and the docs cover attaching to an already-running browser started with --remote-debugging-port. Don't assume every niche feature of every old extension has an identical replacement. The documented workflows are covered.

Auto Close Tag​

VS Code 1.16 (August 2017) added built-in HTML tag closing. Typing > after an opening tag inserts the closing tag, and typing / in a closing tag completes the matching name. The setting is html.autoClosingTags.

The release notes also say something the How-To Geek piece glosses over. They credit the Auto Close Tag extension's author and add that the extension has more features, in particular that it can work with languages other than HTML. So before you uninstall it, test your real file types. The JavaScript and TypeScript settings the article mentions weren't independently confirmed in the documentation I reviewed, so verify them in your own language mode.

Auto Rename Tag and Linked Editing​

The native counterpart is Linked Editing. It's off by default. Turn it on with "editor.linkedEditing": true. Editing one tag then updates its partner.

Don't mix this up with auto-closing. One inserts a closing tag as you type. The other keeps a pair in sync as you edit. They need separate checks.

The caveat matters here. Even How-To Geek warns that JSX and TSX support depends on your TypeScript version and setup. Developer commentary from 2021 on CSS-Tricks reflects the same frustration, with one commenter reporting that the native setting seemed to work only in HTML files, not JSX or PHP. That is an old, anecdotal report, and behavior may have changed since. It does show why you should test a representative project before uninstalling.

Local History​

VS Code 1.66 (March 2022) added local file history to the Timeline view. Depending on configuration, each save can create an entry holding the file's full contents. You can compare it with the current file, restore it, delete it or rename it.

Defaults from that release:

  • Enabled by default (workbench.localHistory.enabled)
  • Maximum file size of 256 KB
  • 50 entries per file
  • 10-second merge window
  • Configurable exclusion patterns

It's a local safety net, not a Git replacement. Git gives you repository history and collaboration. Local history gives you "undo, but with a memory." Files over the size limit won't get snapshots, so don't rely on it for large generated files.

HTML Boilerplate and Emmet​

Emmet is built in. VS Code's documentation describes it as support for snippets and expansion with no extension required. placeholderIt's enabled by default in HTML, JSX, XML, CSS, SCSS, Sass, Less and Stylus files, and in languages that inherit from them, such as Handlebars and PHP.

Typing ! and expanding it gives you a basic HTML document. For other languages, use the emmet.includeLanguages setting. For example, a mapping like "javascript": "javascriptreact" is a commonly used pattern. Custom snippets go in a snippets.json file, and emmet.extensionsPath points to its folder.

Emmet covers standard boilerplate. If your boilerplate extension scaffolds project-specific templates, Emmet won't replace that. I couldn't verify the article's "around 2016" date for Emmet's arrival, so I've left it out.

Git History​

This is the entry where "you don't need it" is weakest, and How-To Geek says as much. The built-in tools divide the job:

  • Source Control Graph: Shows repository commits and branch relationships, including incoming and outgoing commits when an upstream exists. You can select a commit to inspect changed files, open diffs, compare with a branch or tag, or cherry-pick.
  • Timeline: Shows history for one file, including Git commits and local saves. It can compare two committed versions of that file, but only that file.
  • Git blame: Identifies the commit and author behind a line.

One safety note from the documentation: the graph's Checkout (Detached) action leaves HEAD detached. Create a branch before making commits you want to keep.

My advice is to try the native views for ordinary commit browsing, file history and blame. If you miss a specific interface feature, keep the extension.

How to run the audit​

  1. Disable one extension, don't delete it. Reload VS Code.
  2. Use the built-in equivalent on a real project, not a toy file.
  3. Check the edge cases: JSX and TSX for tag features, large files for Local History, remote windows for sync.
  4. Reinstall the extension if something you need is missing.
  5. Move to the next one.

This is a reasonable cleanup, not a mandate. The evidence supports "VS Code now has a built-in alternative, with these boundaries." It doesn't support the claim that every reader should uninstall all eight. And "popular" doesn't mean "installed on your machine and costing you anything." Check your Extensions view first.

 

References

  1. GitHub - microsoft/vscode-emmet-legacy: Emmet features via extension for Visual Studio Code using the new API · GitHub github.com
  2. 8 super-popular VS Code extensions you don't actually need anymore How-To Geek 2026-10-08T21:00:14+00:00
  3. Bracket pair colorization 10,000x faster code.visualstudio.com