Stores & marketplaces

JetBrains Marketplace

Plugin store for IntelliJ-based editors.

Visit plugins.jetbrains.com
Cost
Free

Free to publish. Paid plugins follow JetBrains terms. Check current terms.

Verdict
slow burn

Slow burn: a plugin store for IntelliJ-based editors.

Difficulty
Medium

Needs preparation, a review, or a steady habit before results.

Effort
Medium

About 5 to 10 hours a month.

First result
2 to 4 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 for JetBrains IDEs.

Not for

Non-developer products.

Pros

  • Plugin store for IntelliJ-based editors
  • Developers pay for good plugins

Cons

  • Smaller than VS Code
  • Platform-specific build

The full guide

Last verified 2026-10-30

Links checked 2026-10-30 · All links answer

01What it is and who is there

JetBrains Marketplace hosts plugins for IntelliJ IDEA, PyCharm, WebStorm and other JetBrains IDEs. Developers install plugins from inside their IDE. The audience is professional developers, many of whom pay for tools. Paid plugins can be sold through the marketplace under JetBrains' terms.

02Cost and what you actually pay for

Publishing free plugins is free. Paid plugins follow JetBrains' marketplace terms; check the current terms before setting prices.

03Is it right for you?

It fits developer tools for Java, Kotlin, Python, JavaScript and other languages JetBrains IDEs support. It fits poorly for non-developer products. JetBrains' platform has its own SDK, so building takes work.

04Before you start

  • A JetBrains account and vendor profile.
  • Read the plugin development guidelines and marketplace approval rules.
  • A plugin built with the IntelliJ Platform SDK and tested on current IDE versions.

05Step-by-step: how to distribute here

  1. Build and test the plugin on the IDEs you support.
  2. Upload it and wait for approval.
  3. Write a description with screenshots or a GIF.
  4. Share it with developer communities using JetBrains tools.
  5. Update for new IDE versions.

06What to post or submit

Description:

[Plugin] adds [feature] to [IDE names]. [Benefit]. Works with [languages].

07Common mistakes and do-nots

  • Do not ignore compatibility with new IDE releases.
  • Do not collect data without disclosure.
  • Do not ship without a clear description.

08How to measure it

  • Track downloads and ratings in the vendor dashboard.
  • Track sales for paid plugins.
  • A realistic test: two to three months.

09Time budget

  • Before: 10 to 30 hours.
  • Ongoing: 2 to 4 hours a month.

10Pair it with

11Sources

Sources