All data in Bases is stored in your local Markdown files and their properties — nothing is locked in a proprietary database. The view configuration is saved as a
.base file or embedded in a code block.What you can do with Bases
Table view
Display files as rows with columns for each property. Sort, filter, and edit values inline. Add summaries to calculate totals and averages.
Cards view
Display files as a gallery grid with optional cover images. Great for visual collections like books, films, or places.
List view
Display files as a bulleted or numbered list. Control which properties appear and how they are formatted.
Map view
Display files as pins on an interactive map. Requires the Maps plugin. Great for travel plans and location-based notes.
Use cases
Bases works well for any collection of notes that share common properties:- Project tracking — filter by status, sort by due date, group by owner.
- Reading lists — track books with author, genre, rating, and read status.
- Travel plans — pin locations on a map, attach notes for each place.
- Content calendar — plan posts with publish date, topic, and status.
- Research library — organize papers with tags, authors, and annotation links.
How Bases works
A base reads files from your vault and displays their properties as structured data. You define which files to include using filters (by tag, folder, or a custom expression), then configure views to display and interact with those files. Each base can have multiple views. Each view can have its own layout, filters, sort order, and visible properties — so the same set of notes can be presented in different ways for different purposes.Enable Bases
Learn more
Create a base
Learn how to create a
.base file and embed a base in a note.Views
Explore layouts, filtering, sorting, and grouping.
Formulas
Create computed properties using data from other properties.
Bases syntax
Reference for the
.base file format.