VS Code Extensions: The Complete List (2026)

VS Code extensions are the plugins that transform a lightweight editor into a fully-featured development environment tailored to your stack — and with over 30,000 extensions in the marketplace, choosing the right ones is the difference between a productive workflow and a cluttered one.

What You’ll Learn

• The essential VS Code extensions for Python, JavaScript, and Git workflows
• How to sync settings across machines and recommend extensions to your team
• Performance tips to keep VS Code fast with many extensions installed
• Which extensions to avoid and why

Why Extensions Matter

VS Code alone is a text editor. Extensions add language support, debugging, linting, formatting, Git integration, Docker management, and AI assistance. The right set of extensions makes your editor feel like it knows what you’re trying to do.

Doda Browser uses a shared VS Code workspace configuration with recommended extensions so every developer has the same setup from day one.

Learning Path

    flowchart LR
  A[VS Code Basics] --> B[Essential Extensions]
  B --> C[Language-Specific Tools]
  B --> D[Productivity Extensions]
  C --> E[Workspace Config<br/>You are here]
  D --> E
  style E fill:#f90,color:#fff
  

Essential Extensions by Category

Python Development

• Python (ms-python.python) — IntelliSense, debugging, virtual environments, Jupyter
• Pylance (ms-python.vscode-pylance) — Fast, language-server-powered type checking
• Python Test Explorer (littlefoxteam.vscode-python-test-adapter) — Visual test runner
• Black Formatter (ms-python.black-formatter) — Auto-format with Black

{
  "[python]": {
    "editor.defaultFormatter": "ms-python.black-formatter",
    "editor.formatOnSave": true
  },
  "python.analysis.typeCheckingMode": "basic"
}

JavaScript / TypeScript

• ESLint (dbaeumer.vscode-eslint) — Real-time linting with auto-fix on save
• Prettier (esbenp.prettier-vscode) — Opinionated code formatting
• JavaScript Debugger (ms-vscode.js-debug) — Built-in but keep it enabled
• npm Intellisense (christian-kohler.npm-intellisense) — Auto-import npm modules
• Path Intellisense (christian-kohler.path-intellisense) — File path autocomplete

{
  "editor.codeActionsOnSave": {
    "source.fixAll.eslint": "explicit"
  },
  "editor.defaultFormatter": "esbenp.prettier-vscode",
  "editor.formatOnSave": true
}

Git Integration

• GitLens (eamodio.gitlens) — Inline blame, commit search, file history, branch visualization
• GitHub Pull Requests (GitHub.vscode-pull-request-github) — Review and manage PRs from within VS Code
• Git Graph (mhutchie.git-graph) — Visual commit graph in a dedicated tab

Docker

• Docker (ms-azuretools.vscode-docker) — Manage containers, images, and Docker Compose
• Dev Containers (ms-vscode-remote.remote-containers) — Develop inside containers

Themes and Visual

• Material Icon Theme (pkief.material-icon-theme) — File-type icons for quick scanning
• One Dark Pro (binaryify.one-dark-pro) — Popular syntax theme
• Error Lens (usernamehw.errorlens) — Inline error and warning highlights

Productivity

• GitHub Copilot (GitHub.copilot) — AI-powered code suggestions
• Live Share (ms-vsliveshare.vsliveshare) — Real-time collaborative editing
• Todo Tree (Gruntfuggly.todo-tree) — Highlight and manage TODO/FIXME comments
• Bookmarks (alefragnani.Bookmarks) — Navigate large files with bookmarks
• Remote - SSH (ms-vscode-remote.remote-ssh) — Edit files on remote servers

Workspace Recommendations

Share recommended extensions with your team via .vscode/extensions.json:

{
  "recommendations": [
    "dbaeumer.vscode-eslint",
    "esbenp.prettier-vscode",
    "eamodio.gitlens",
    "ms-python.python",
    "ms-python.black-formatter",
    "GitHub.copilot",
    "pkief.material-icon-theme"
  ],
  "unwantedRecommendations": [
    "hookyqr.beautify",
    "ms-vscode.vscode-typescript-next"
  ]
}

When team members open the project, VS Code prompts them to install the recommended extensions.

Settings Sync

Enable Settings Sync from the gear icon in the bottom-left corner. Your extensions, settings, keybindings, and UI state sync across machines via your GitHub or Microsoft account.

# To check sync status from CLI
code --status | grep -i sync

Expected output:

Settings Sync: Enabled
Last Sync: 2 minutes ago
Extensions: 24 synced

Performance Tips

Too many extensions slow down VS Code. Follow these guidelines:

1. Disable extensions per project — Use Extensions > Disable (Workspace) for project-specific tools
2. Avoid duplicate-function extensions — Don’t install both Prettier and Beautify
3. Use profiles — Create separate profiles for different workflows (Python dev, frontend, writing)
4. Startup performance — Run Developer: Show Running Extensions to see which ones slow startup
5. Turn off unused language features — Disable JavaScript validation if you use TypeScript

{
  "typescript.validate.enable": false,  // If you only use ESLint
  "extensions.autoCheckUpdates": false,
  "extensions.autoUpdate": false
}

Extensions to Avoid

• Beautify — Deprecated; use Prettier instead
• JavaScript Booster — Largely superseded by Copilot
• Multiple CSS/JSON formatters — They conflict; pick one

Common Errors

1. ESLint and Prettier Conflicts

Rules overlap and create save loops. Install eslint-config-prettier and add "extends": ["prettier"] to your ESLint config.

2. Too Many Extensions Installed

30+ active extensions slow startup by 2-10 seconds. Audit quarterly. Disable workspace-specific ones.

3. Missing Python Interpreter

The Python extension shows “Select Python Interpreter” if it can’t find one. Open the command palette and run Python: Select Interpreter.

4. Sync Conflicts Between Machines

If settings sync fails, use Settings Sync: Show Synced Data to inspect conflicts. Choose one machine as the source.

5. Extensions Not Activating

Check the Output panel (View → Output) and select the extension’s log channel. Reload the window if needed.

6. Copilot Not Suggesting

Ensure Copilot is enabled for your language. Check the Copilot status in the bottom-right corner of the status bar.

Practice Questions

1. How do you recommend extensions to your team? Create a .vscode/extensions.json file with the recommendations array. VS Code prompts team members to install them.

2. What is the best way to avoid ESLint/Prettier conflicts? Use eslint-config-prettier to disable ESLint rules that overlap with Prettier.

3. How do you disable an extension for a specific workspace? Right-click the extension and select “Disable (Workspace)”.

4. What should you do if VS Code starts slowly? Run Developer: Show Running Extensions to identify startup-time hogs. Use profiles to load only needed extensions.

5. What tool syncs VS Code settings across machines? Settings Sync, accessible from the gear icon. It syncs to GitHub or Microsoft account.

Challenge: Create a .vscode directory in one of your projects with extensions.json, settings.json, and launch.json. Share it with a teammate and verify they get the recommended extensions prompt on opening the project.

FAQ

What’s Next

Built by the developers of Doda Browser, DodaZIP, and Durga Antivirus Pro. Updated 2026-06-19.