Comparison pages
How MDCollections compares
MDCollections is not trying to replace Obsidian. The stronger story is MDCollections plus Obsidian: keep plain-text notes and vault compatibility, but add a purpose-built workflow for physical collections and inventory.
MDCollections + Obsidian vs Plain Obsidian Bases
Compare a combined MDCollections-plus-Obsidian workflow with plain Obsidian Bases for people who want Markdown-backed collections and better workflows for physical items.
Read comparison →MDCollections + Obsidian vs Plain Obsidian Notes and Dataview
Compare a combined MDCollections-plus-Obsidian workflow with a hand-built Obsidian setup using notes, templates, frontmatter, and Dataview queries.
Read comparison →MDCollections vs Notion Databases
Compare MDCollections and Notion databases for people deciding between a local Markdown workflow and a cloud-first collection database.
Read comparison →Workflows worth comparing
Obsidian Bases
The closest philosophical match. The real question is often whether plain Obsidian is enough, or whether MDCollections should handle collection capture while Obsidian stays the broader note system.
Obsidian notes plus templates and Dataview
A flexible DIY path, but it pushes the setup burden onto you. MDCollections makes more sense when you want structured capture and mobile workflows without giving up Markdown or Obsidian compatibility.
Notion databases
A strong fit for cloud collaboration and team-friendly tables. MDCollections is stronger when file ownership, local storage, and plain-text portability matter more than shared workspaces.
Where MDCollections should win
- people who want item catalogs in Markdown files they actually own
- Obsidian users who want a purpose-built companion app for collection capture and browsing
- collectors who need barcode scanning, images, locations, and templates in one workflow
- home organizers who want QR-labeled bins and physical storage tracking
- anyone tired of choosing between “fully manual” and “fully locked in”