Stores & marketplaces

Obsidian community plugins

Plugin directory for a loyal note-taking community.

Visit obsidian.md
Cost
Free

Free to use. No paid tier is needed to list or post.

Verdict
slow burn

Slow burn: a loyal note-taking community.

Difficulty
Easy

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

Effort
Low

About 2 to 4 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

Plugins for note-taking workflows.

Not for

Products unrelated to notes.

Pros

  • Loyal note-taking community
  • Free

Cons

  • Review wait
  • Niche audience

The full guide

Last verified 2026-10-30

Links checked 2026-10-30 · The links timed out or loop when we checked. Try them yourself.

01What it is and who is there

Obsidian is a note-taking app, and its community plugins directory lets users add features. Plugins are submitted through Obsidian's releases repository and reviewed before listing. The audience is a loyal group of note-takers, researchers and knowledge workers who customize their setup.

02Cost and what you actually pay for

Publishing a plugin is free. Your cost is development and review time.

03Is it right for you?

It fits tools for notes, writing, research and personal knowledge management, and services that can sync with notes. It fits poorly for products unrelated to notes.

04Before you start

  • Read Obsidian's plugin guidelines and submission requirements.
  • Build the plugin from the official sample plugin.
  • A README with screenshots.

05Step-by-step: how to distribute here

  1. Build and test the plugin in a test vault.
  2. Publish a release on GitHub with the required files.
  3. Submit it to Obsidian's community plugin list, following the current process.
  4. Address review feedback.
  5. Share it in the Obsidian forum and Discord where allowed.

06What to post or submit

Description:

[Plugin] lets you [job] in Obsidian. [Key feature]. Works offline: [yes/no].

07Common mistakes and do-nots

  • Do not send note content to servers without clear disclosure.
  • Do not ignore the review checklist.
  • Do not abandon the plugin after release.

08How to measure it

  • Track downloads on the plugin page.
  • Track GitHub issues and stars.
  • A realistic test: two months.

09Time budget

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

10Pair it with

11Sources

Sources