Launch guideBrowser and IDE extensions
How to launch a JetBrains plugin
JetBrains Marketplace reviews plugins against published approval guidelines before they go live, and it's strict about the listing itself: short names, no marketing adjectives, an English summary in the first 40 characters. Most discovery happens inside the IDE's plugin search, so the name and tags do more work than any launch post.
Updated · platform facts checked against the official docs linked below
At a glance
Where people find JetBrains plugins
- In-IDE plugin search: Most installs start from the Plugins settings panel, which searches name, description and tags.
- The language community: Plugins for a specific language or framework spread through its forums and chats.
- GitHub: Open-source plugins get found and trusted through their repos.
- Show HN or dev newsletters: Only for plugins with a broad audience.
Assets to prepare
| Asset | Spec or guidance |
|---|---|
| Plugin name | 1–4 words, max about 20 characters; no word "plugin", no JetBrains product names or other trademarks.[1] |
| Description | English first; the first 40 characters are a summary used on cards; no adjectives like "simple" or "professional".[1] |
| pluginIcon.svg | Optional but recommended; no default template logo or text-only icon.[1] |
| Screenshots | Minimum 1200×760, showing the real IDE, text legible.[1] |
| EULA | You must provide your own end user license agreement.[2] |
| Tags | At least one; they work as search filters.[1] |
Store and listing rules
What the platform itself says, with a link to the page we checked.
- Plugins must meet JetBrains Marketplace approval guidelines before upload; open-source plugins need a source code link.[2]
- Ads in the plugin are prohibited under the upload terms.[2]
- JetBrains doesn't publish a fixed approval time in its upload docs, so leave slack before your announcement.[2]
A 4-week launch timeline
Week 1 · four weeks out
- Pick a short, specific name that passes the naming rules.
- Write the first 40 characters of the description as a plain summary.
- Create a vendor profile.
Week 2 · three weeks out
- Take 1200×760 screenshots in a real project.
- Write the EULA or choose an open-source license.
- Choose tags.
Week 3 · two weeks out
- Upload and wait for approval.
- Write docs or a landing page.
- Prepare a post for the language community.
Week 4 · launch week
- Fix anything the moderators flag.
- Plan the first update based on beta feedback.
- Set up a feedback channel (GitHub issues or email).
Launch-day checklist
- Check the listing on the Marketplace website and in the IDE search.
- Post in the language or framework community with a screenshot.
- Link the listing from your GitHub README and docs.
- Add the plugin to LaunchRanked for a permanent page.
After launch: SEO steps
Launch boards reset; search pages don't. These steps keep people finding you after launch week.
- Write a page for each task the plugin does, with the IDE and language named.
- Link from your GitHub README to the Marketplace listing and vice versa.
- Keep change notes current in plugin.xml so each release says what changed.
Common mistakes
- Names like "Super Helper Plugin for IntelliJ" that break the naming rules.
- Marketing adjectives in the description.
- Screenshots at a small size or of an empty project.
Templates for this launch
- 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.
- Changelog entryA changelog entry template grouped by Added, Changed, Fixed and Removed, written for users rather than commit logs, with a filled example.
- Directory listing descriptionWrite directory and launch-site listings once: a 60-character tagline, a 160-character short description and a long version, with a filled example.
FAQ
How long does JetBrains plugin approval take?
JetBrains doesn't state a fixed time in its upload documentation. Upload early and don't announce a date until the plugin is approved.
What are the naming rules?
1–4 words, ideally 20 characters or fewer, no word "plugin", no JetBrains product names, trademarks or emoji.
What size should JetBrains Marketplace screenshots be?
At least 1200×760, showing the real IDE with legible text.
Can I show ads or promos inside a JetBrains plugin?
No. The upload terms prohibit ads, meaning commercial messages meant to promote a business, product or service. Put that on your website instead.
Sources
Checked . Platforms change their rules; open the source before you rely on a number.
Related launch guides
- How to launch a VS Code extensionVS Code extension launch guide: vsce publishing, icon and README rules, 30-keyword limit, pre-releases, Open VSX for other editors, and SEO.
- 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 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.
- How to launch a Chrome extensionChrome extension launch guide: Web Store image sizes, 132-character summary, review times, single-purpose rule, Edge Add-ons, and SEO beyond the store.