Obsidian Bases Just Changed Everything

Obsidian Bases introduces a new core plug-in that turns any set of notes into a fast, queryable database—so users can filter, sort, and view thousands of notes instantly without relying on external tooling. The practical payoff is immediate: instead of hunting through a vault or building complex dashboards, people can create “bases” that surface exactly the notes they need (favorite quotes, active projects, recently modified items) with columns and views that behave like a lightweight Airtable-style interface.

The walkthrough starts from scratch. After enabling access (the feature is tied to Obsidian’s versioning and early access via a Catalyst license), creating a base is done through Obsidian’s command palette. Once a base exists, it searches the entire vault rather than being trapped inside a single “database” container—sidestepping a common pain point from other note systems where content can be fragmented across separate databases. From there, the key mechanism is properties plus filters. A user can add a property such as “collection contains quotes,” which links a base to a set of quote notes; applying that filter collapses a massive note collection (10,000+) down to a manageable subset (roughly 70 quotes in the example).

A major focus is replicating the feel of Data View, a popular third-party plug-in used in IdeaVerse Pro. The transcript shows how to build a quotes table with columns like rank and author, then sort by rank so the highest-rated quotes float to the top. Obsidian Bases currently has some rough edges—properties aren’t always obvious in the UI until users type search terms, and formatting/capitalization can be adjusted at the table level without rewriting metadata across every note. Even so, the results are functional and responsive.

Three “best features” anchor the argument for why Bases matters. First is speed: large tables scroll smoothly even with tens of thousands of files, while Data View can become sluggish or freeze during heavy table rendering. Second is multiple views per base: the same base can host different filtered views (e.g., “quotes by rank over four” and “top eight quotes”), and those views can be switched quickly. Third is embeddable views: specific filtered tables can be embedded inside other notes using Obsidian’s linking syntax, letting users drop bespoke database slices into agendas and workflows.

The examples extend beyond quotes. Attempts to recreate a “recently modified” Data View layout highlight current limitations around timestamp formatting and clean folder display. A projects example uses the ACE folder framework (active/simmering/sleeping) to show how Bases can filter by folder path and switch between “all projects” and “active projects,” though the UI may show file paths more messily than desired.

Beyond mechanics, the transcript turns to implications. Bases elevate the importance of Obsidian properties, which can shift thinking from freeform serendipity toward structured, database-like planning. There’s also uncertainty about how AI will interpret bases, since the underlying base format is essentially a compact filtering note rather than a fully rendered dataset. For non-coders, advanced filtering via formulas and functions may be hard today, but community examples and AI-assisted coding could reduce that barrier.

Overall guidance is cautious optimism: Bases is early, promising, and likely to iterate quickly. The recommended approach is to try one or two bases and rebuild useful existing Data View setups—using speed and embeddable views now, while watching for improvements like better property discovery, note counts, and richer formatting.