Launch guideBrowser and IDE extensions
How to launch a VS Code extension
VS Code extensions publish through the command line with vsce, and your README becomes the Marketplace listing. There's no human review queue to wait on, which makes the launch mostly about the listing and the README. Also publish to Open VSX: editors built on VS Code's open-source base use that registry, and it's a separate account and command.
Updated · platform facts checked against the official docs linked below
At a glance
Where people find VS Code extensions
- Visual Studio Marketplace: Searched from the Extensions view inside VS Code and on the web; your name, description and keywords are what people search against.
- Open VSX Registry: Used by VS Code-based editors that can't use Microsoft's Marketplace.
- Hacker News (Show HN): Developer tools that people can install and try in a minute do well.
- The language or framework community: An extension for a framework launches best in that framework's Discord, forum or subreddit.
- GitHub: An open repo with a good README brings stars, issues and links.
Assets to prepare
| Asset | Spec or guidance |
|---|---|
| Icon | 128×128 PNG minimum, no SVG.[1] |
| README | Becomes the listing. Images must use HTTPS URLs; user SVGs are blocked except from trusted badge providers.[1] |
| galleryBanner | Set galleryBanner.color (hex) so the header matches your icon.[1] |
| Keywords and categories | Up to 30 keywords; pick categories users actually filter by.[1] |
| Animated GIF | The core command in action, at readable zoom. |
| CHANGELOG.md | Shown on the listing; start it at launch. |
Store and listing rules
What the platform itself says, with a link to the page we checked.
- You need a publisher identity in package.json. Microsoft says global Azure DevOps personal access tokens are being retired and recommends Microsoft Entra ID-based authentication for automated publishing; check the current guidance before setting up CI.[1]
- Pre-release versions use
vsce publish --pre-releaseand need VS Code 1.63.0 or later; Microsoft suggests even minor versions for releases and odd for pre-releases.[1] - Open VSX needs an Eclipse account matching your GitHub username, a signed publisher agreement, an access token and a namespace created with
ovsx create-namespace.[2]
A 4-week launch timeline
Week 1 · four weeks out
- Create the publisher and set up authentication.
- Write the README as a sales page: problem, GIF, commands, settings.
- Make the 128×128 icon and pick the banner color.
Week 2 · three weeks out
- Choose keywords and categories.
- Ship a pre-release to friends and collect issues.
- Create the Open VSX namespace.
Week 3 · two weeks out
- Fix what testers hit; write the CHANGELOG.
- Set up CI publishing to both registries.
- Draft the Show HN post (template).
Week 4 · launch week
- Publish the stable version to both registries.
- Make a landing page or docs page on your own domain.
- Prepare posts for the framework community.
Launch-day checklist
- Confirm both listings render the README and images correctly.
- Post Show HN with a link people can install from immediately.
- Post in the language or framework community with the GIF.
- Add it to LaunchRanked with a link to your docs page.
- Triage GitHub issues within the day; early responsiveness shows in reviews.
After launch: SEO steps
Launch boards reset; search pages don't. These steps keep people finding you after launch week.
- Give the extension a docs page on your own domain; Marketplace pages rank mostly for the extension's name.
- Write pages for the specific errors or tasks it solves ("fix X in VS Code").
- Keep the CHANGELOG current; it signals maintenance.
- Add repository topics on GitHub so it shows in topic pages.
Common mistakes
- Relative image paths or SVG images in the README that don't render on the Marketplace.
- Forgetting Open VSX, so users of other VS Code-based editors can't install it.
- Stuffing all 30 keywords with loosely related terms.
- No CHANGELOG, so updates look like nothing changed.
Templates for this launch
- Show HN postA Show HN template that follows Hacker News rules: a plain title, a link people can try, and a first comment on why you built it and how it works.
- Changelog entryA changelog entry template grouped by Added, Changed, Fixed and Removed, written for users rather than commit logs, with a filled example.
- Release notesRelease notes for a notable launch or version: what's new, why it matters, how to use it, upgrade steps and known issues, with a filled example.
- Launch thread for XA copy-paste launch thread for X: hook, problem, demo, how it works, proof, offer and ask, with a filled example and the 280-character rule.
FAQ
How do I publish a VS Code extension?
Create a publisher, add it to package.json, and publish with vsce. Microsoft is retiring global Azure DevOps tokens, so check its current authentication guidance for CI.
Why don't my README images show on the Marketplace?
Images must resolve to HTTPS URLs, and SVGs are blocked unless they come from trusted badge providers.
What is Open VSX and do I need it?
It's an open registry used by VS Code-based editors that can't use Microsoft's Marketplace. Publishing there reaches those users; it uses the ovsx CLI.
How many keywords can a VS Code extension have?
Up to 30 in package.json. Use the terms people would search in the Extensions view.
Sources
Checked . Platforms change their rules; open the source before you rely on a number.
Related launch guides
- How to launch a JetBrains pluginJetBrains Marketplace launch guide: upload and approval, name and description rules, 1200×760 screenshots, tags, and how IDE users actually find plugins.
- How to launch a CLI toolLaunch a command-line tool: install paths (Homebrew tap vs core, winget, npm, pip), terminal GIFs, Show HN and docs that rank for the problems it solves.
- How to launch an npm packageLaunch an npm package: package.json fields, provenance and trusted publishing, a README that sells, and where JavaScript developers look.
- How to launch an open-source projectLaunch an open-source project: README and repo setup, GitHub topics and social preview, Show HN rules, awesome lists, and docs that rank on Google.