MdWrk vs Obsidian
Use this comparison when local-first Markdown authoring, package reuse, and extension contracts matter.
MdWrk is best evaluated as a local-first Markdown workspace and package platform. Obsidian is widely used for personal knowledge management and linked note collections. This page frames the practical difference for authors and developers evaluating Markdown workflows.
| Criteria | MdWrk | Obsidian |
|---|---|---|
| Local-first authoring | Browser and PWA-centered Markdown workspace with local persistence as a core boundary. | Local Markdown files are central, with a different app and plugin model. |
| Package reuse | Renderer, editor, theme, extension, and lander packages are documented as reusable surfaces. | Typically evaluated as an app and plugin ecosystem first. |
| Extension contracts | Governed package and manifest surfaces keep extension behavior explicit. | Plugin behavior follows Obsidian's ecosystem and product model. |
Choose MdWrk when you need browser availability, reusable package adoption, governed extension contracts, and static product documentation that explains the boundary clearly.