Obsidian Plugins: How to Choose Without Getting Lost

Over 1,000 community plugins exist for Obsidian. Here's how to avoid the configuration rabbit hole and find the ones worth keeping long-term.

There are over 1,000 community plugins for Obsidian on GitHub. I know because I’ve spent an embarrassing amount of time browsing them.

The temptation is real — each plugin promises to solve a problem you didn’t know you had. But plugin hunting early on is one of the most effective ways to avoid actually using Obsidian for thinking and writing.

Plugins are tools. Most of the time, you don’t need them yet.

Start with core plugins

Obsidian ships with a set of official core plugins: Daily Notes, Backlinks, Graph View, Workspaces, and more. These cover a surprising amount of ground. Before reaching for community plugins, I’d exhaust what’s already built in.

Community plugins should answer a specific frustration — not a hypothetical one. “This would be nice” isn’t a good reason. “I do this manually every day and it’s slowing me down” is.

What I’ve kept long-term

Most plugins I’ve tried didn’t stick. A few became load-bearing parts of my system.

Dataview treats your notes as a database. Using frontmatter fields — tags, dates, status — you can build dynamic lists that update automatically. I’ve had it installed since 2021. It replaced a lot of manual index maintenance: “books I read this month,” “notes without a permanent home,” lists like that.

Spaced Repetition brings Anki-style review into Obsidian itself. Rather than notes going cold after you write them, you get periodic prompts to revisit. I use it less for memorization and more for keeping ideas alive over time.

Calendar is a small one — a visual calendar that links to daily notes. It sounds trivial, but if your workflow is built around daily notes, navigating by calendar is faster than searching by filename.

Workspaces saves panel layouts. I have different configurations for writing, research, and review. Switching modes takes one click instead of manual rearrangement.

The risk side

Community plugins run in the .obsidian folder as external code. You’re trusting the developer. This isn’t a reason to avoid plugins, but it is a reason to be selective — stick to plugins with active maintenance and visible community adoption.

More practically: the more plugins you install, the harder it becomes to understand what your system is actually doing. My rule is to delete rather than just disable plugins I’m not using. A smaller, well-understood set beats a large, opaque one.

Building your own

In 2024, I hit a wall where no existing plugin did exactly what I needed. I built one.

I’d never written TypeScript before. I used ChatGPT as a patient tutor and worked through it section by section. The result was a plugin shaped around my own thinking process — something no off-the-shelf tool would have given me.

I’m not suggesting everyone build plugins. But the option exists, and that matters. Obsidian’s architecture lets you bend the tool toward yourself rather than adapting yourself to the tool. That’s the design philosophy in its most literal form.