Stores & marketplaces

VS Code Marketplace

Developers search extensions from inside their editor.

Visit marketplace.visualstudio.com
Cost
Free

Free to publish. Check current publisher requirements.

Verdict
works

Works: developers search extensions from inside the editor.

Difficulty
Easy

Mostly self-serve. Sign up and post, with light checks.

Effort
Low

About 2 to 4 hours a month.

First result
1 to 2 weeks

A rough range for one person working on it part-time.

Payoff
Compounds

keeps growing while you keep at it.

Best for

Developer tools that run in VS Code.

Not for

Products with no editor use.

Pros

  • Developers search from inside the editor
  • Free

Cons

  • Crowded categories
  • Only for VS Code tools

The full guide

Last verified 2026-10-30

Links checked 2026-10-30 · All links answer

01What it is and who is there

The Visual Studio Marketplace hosts extensions for VS Code. Developers search for extensions from inside the editor, so discovery happens where they work. The audience is large and almost entirely developers. Good names, keywords and a clear README matter for search.

02Cost and what you actually pay for

Publishing is free. You need a publisher account; check the current publisher requirements. Your cost is building and maintaining the extension.

03Is it right for you?

It fits developer tools: linters, themes, language support, AI coding helpers and integrations with your service. It fits poorly for products with no editor use. Categories like themes and AI helpers are crowded.

04Before you start

  • Create a publisher account following the current Marketplace instructions.
  • Read the Marketplace publishing guidelines.
  • A README with a GIF of the extension working.
  • An icon, a clear display name and relevant keywords in the manifest.

05Step-by-step: how to distribute here

  1. Build and test the extension with the official tools.
  2. Write a README that shows what it does in the first screen.
  3. Publish with the official command-line tool.
  4. Share it where developers in your niche gather.
  5. Respond to issues and reviews.
  6. Release updates with a changelog.

06What to post or submit

Display name and description:

[Product]: [what it does] for [language/framework]

README opening:

[Product] [does job] inside VS Code. [GIF]. Install: search "[Product]" in Extensions.

07Common mistakes and do-nots

  • Do not stuff keywords unrelated to the extension.
  • Do not collect telemetry without disclosure and an opt-out.
  • Do not publish without a README.

08How to measure it

  • Track installs and ratings on the Marketplace page.
  • Track sign-ups from the extension to your service, if any.
  • A realistic test: two months after publishing.

09Time budget

  • Before: 5 to 20 hours.
  • Ongoing: 1 to 3 hours a month.

10Pair it with

11Sources

Sources