The Reddit thread has some good discussion about the feature
https://old.reddit.com/r/ObsidianMD/comments/1mtxh52/obsidia...
The solution I used before bases is eh... pretty hacky.
```meta-bind-js-view {memory^inputText} as title --- const toShow = context.bound.title || "TKTK"; const str = `\`\`\`meta-bind-button label: New Project Idea - ${toShow} icon: "" hidden: false class: "" tooltip: "" id: "" style: primary actions: - type: templaterCreateNote templateFile: Templates/Project.md folderPath: Project Ideas fileName: ${toShow} openNote: true \`\`\``; return engine.markdown.create(str) ```
Using a base you can manage, sort and filter your files and their propreties (ex add a rating, price, or deadline proprety to your files or only show files from my movie folder where my proprety is set to [this])
The base doesn't DO anything you couldn't do by hand, it just allows you to do it faster, as you could always modify a file propreties by hand in that file, or search for it using the search features.
The propreties you add are stored in plain text on top of your markdown files The base is stored in a very readable format similar to yaml to the .base file you can see in obsidian.
Here is the generated .base file for a test Movies folder : views: - type: table name: Movies filters: and: - file.folder == "All/Movies" order: - file.name - tags - Watch Date columnSize: file.name: 167
I think there was (probably still is) a plugin that did something similar to bases that I tried before and didn’t really like conceptually.
On top of that, you can add other properties to the view, especially one like modified date, which updates every time you modify the file. This is useful for seeing which files you haven't looked at in a while. Old concepts often apply to new ones, but we sometimes forget to check back to make that connection explicit."
Maybe it's a bit harder to understand, as it's a more mushy than the usual relational database.
> The idea is that you can store properties, or metadata about the current file, in Obsidian notes. For example, if I have a note about Decoder, I might put the name of the host and a list of episodes. For each episode that I want to take notes on, I might write down which guests were on, what date it came out, or the episode number. What Bases allows you to do is visualize a certain kind of note as a table or eventually as a Kanban view or another type of view. So, it’s like a visualization layer on top of the data that you already have. We just make it really easy to create that database from the bottom up.
> It’s kind of like a backward database because all the data is already in there. You’re just looking at it and saying, “Show me all notes that have the ‘books’ tag,” for example, or a link to “Casey.” Then, I get a table and then I have all my metadata, which I can edit. It’s quite powerful if you’re someone who enjoys tracking books that you read, or the movies that you watch, the places that you go, the articles you’ve read. You can very easily create these structures or do project management.
Sounds like a View.
https://blacksmithgu.github.io/obsidian-dataview/
I often want to answer questions like:
- When was the last time I chatted with this person - What did we talk about - Who haven't I spoken to in a while
For now, I’m just sticking to using it for daily notes, but I feel there’s so much I’m missing.
For bases to work I need to split my stuff up into tiny documents but I'd prefer to have one big document with separate sections. For example I keep one document `book-recommendations.md` with many small sections for books I'd like to read. I can't search through that with bases unless I split those out into many small files in with one recommendation each.
The Obsidian dev team has been really responsive to feedback from those of us in the beta, and I'd encourage people to look at the changelog to see that in action (e.g. changing the syntax to be more object oriented, smoothing over UI issues, etc)
Obsidian Bases - https://news.ycombinator.com/item?id=44058972 - May 2025 (13 comments)
I even started just writing the daily journal all in one file because that gives me that but it's starting to get a little big.
Say you're setting up a media log of your engagements and you want to track completed season for a show-- if you're doing a handful of shows, this isn't a big deal. Over 100 shows, averaging 4 seasons -- that's 400 "completions", one file each. Plus another 100 files for the media metadata itself. That's 500 files that can be simply represented by 500 lines of a spreadsheet, even if you're duplicating title, year, etc. over and over.
The sharding of data into tiny files is what makes it difficult to use anywhere outside of Obsidian. If Obsidian Bases used the full power of YAML front-matter data properly, that'd be SO much better.
It's still faster, more efficient to use a spreadsheet. For anything more than what a spreadsheet can handle-- I would use SQLite.
I hope the API has support to allow extensions---I see that it is on the Roadmap[0].
I'm particularly interested to see how this integrates with Canvas and other note types.
Very happy that Bases is officially launching. My experience so far has been great. It can definitely replace the "Projects" plugin for me, maybe the "Dataview" plugin as well? Hope it can rival Notion Databases in the future, e.g. by adding a Kanban view.
The lack of something like Notion databases / tables was the last thing stopping me from migrating over; I found this feature really helpful for organizing my thoughts and tasks as I want them organized, and not having it would have been a noticeable UX regression for me.
With this launch, I'll take a deeper look. It's that simple: it provides a feature many want, largely because it's seen as a killer feature of comparable closed platforms.
Does anyone know what JS library (presumably) they are using to display, filter, sort the table?
In particular, I love how you select text/blocks in Notion and how every line is a "block". I really wish other editors did that as well. In fact, it's probably the main reason why I haven't moved away from Notion.
Also, I'm still waiting for the org mode comment from a seasoned emacs user. :)
I love the dataview flexibility and multiple display options.
I’ve moved my Chinese vocab list to Bases (I already had all data in front matter so it was easy) and it’s much much nicer and faster than Dataview
However, for task lists, Dataview still works better imo
Is it possible to embed `Bases` in existing notes? Or do they always have to be standalone files?
Currently I have lots of files with embedded Dataview queries in files. I’d like to replicate that with this new functionality.
It's also open source, unlike obsidian which is proprietary
No more need to evaluate AnyType or similar apps.
Obsidian rocks.