Visual Studio Marketplace

Developer Tools

Microsoft Corporation · Developer tools & code hosting

Best for: Publishing editor extensions, themes, and language tooling for VS Code.

Overview

The Visual Studio Marketplace is Microsoft's official distribution channel for Visual Studio Code extensions (and separately Visual Studio IDE extensions). Extensions are packaged as .vsix bundles and published through the vsce command-line tool against a publisher identity backed by Azure DevOps. It is the dominant distribution point for the world's most-used code editor, spanning language support, linters, formatters, themes, debuggers, remote-development backends, and AI coding assistants.

Authentication for publishing uses Azure DevOps Personal Access Tokens today, with Microsoft moving publishers toward Microsoft Entra ID-based secure publishing as legacy global PATs are retired at the end of 2026. There is no built-in commerce layer: the Marketplace does not sell licenses or process payments, so commercial extensions enforce licensing and billing through their own backends. Security posture centers on automated malware scanning, extension signing, and reactive policy enforcement rather than a mandatory upfront human review, keeping the barrier to publishing low.

How to build & ship

  1. 1Create an Azure DevOps organization and a publisher on the Marketplace management page
  2. 2Scaffold an extension (e.g., yo code) and define contributions in package.json
  3. 3Generate an Azure DevOps Personal Access Token with Marketplace scope
  4. 4Package the extension into a .vsix with vsce package
  5. 5Publish with vsce publish (or upload the .vsix manually)
  6. 6Optionally verify your publisher domain to earn a verified badge

Key APIs & SDKs

vsce (VS Code Extension CLI)
VS Code Extension API (contribution points, activation events)
Language Server Protocol (LSP)
Debug Adapter Protocol (DAP)
ovsx CLI (Open VSX registry)

Integration types

Authentication & security

  • Primary auth: PAT
  • Also supports: JWT
  • Security review: Not required
  • Extensions are scanned, signed, and subject to malware verification and policy takedowns, but there is no mandatory pre-publication human review.
  • There is no human pre-publication review; extensions go live after automated malware and secret scanning, with rescans and post-publication takedowns handling malicious extensions.
  • Marketplace gallery/API limits are not publicly documented as fixed numbers.

Monetization

Onboarding
$0
Commission
0% (no built-in payments; publishers handle any monetization themselves)
Merchant of Record
None (no merchant of record)

Pros & cons for builders

Pros

  • Very fast, self-service publishing with no manual approval queue
  • Huge built-in audience through VS Code
  • Simple CLI-based workflow (vsce) and free hosting
  • Verified-publisher badges add trust signals

Cons

  • No upfront review means malicious/typosquatted extensions do slip through
  • No native paid-extension/monetization model on the Marketplace
  • Tied to Microsoft's proprietary marketplace (Open VSX needed for non-MS editors)