How to open an Obsidian vault without Obsidian

An Obsidian vault is a folder. Inside it are .md files and whatever images you dragged in, plus a hidden .obsidian folder holding settings, plugins and workspace state. That is the entire format. There is no database, no proprietary container and no export step, and any app that can open a folder of Markdown can open your vault.

So the question is not can something else open it. It is what survives when something else does.

What travels

• The words. Obviously, but worth saying: your notes are text, and text is the most portable thing in computing.
• Standard Markdown. Headings, lists, tables, code fences, links, images, footnotes. Anything that is CommonMark or GitHub Flavored Markdown reads the same anywhere that implements them properly.
• Wikilinks. [[Note title]] is not standard Markdown, but it is common enough that a serious app will resolve it, including aliases and heading anchors.
• Tags and frontmatter. #tag inline and YAML at the top of the file. Both are conventions rather than standards, and both are widely supported.
• Callouts. Obsidian’s > [!note] syntax has become the de facto standard for the idea, and some apps implement it.
• Canvas files. Obsidian’s .canvas files use JSON Canvas, an open format. Another app implementing it opens the same board.

What does not

• Your plugins, entirely. This is the big one. If your notes are full of Dataview queries, they are text in a code fence that another app will show you as a code fence. Whatever the plugin was rendering, it was rendering at read time and it is not in the file.
• Your theme and layout. Everything in .obsidianis Obsidian’s. Panes, hotkeys, CSS snippets, the lot.
• Block references. The ^block-id anchors stay in your files as text. Whether anything resolves them is another question.
• Anything a plugin stored outside the file. Some keep their own state in .obsidian/plugins. That state does not come with the notes.

Notice the shape of that list: everything you lose is something a plugin was doing, and everything you keep is in the file. That is a fair summary of what plain files buy you and what they do not.

The safe way to do it

1. Copy the folder. Work on the copy for a week. Nothing in this post is risky, and there is still no reason to test on the only version you have.
2. Open the copy in the new app. If it offers to import rather than to open, stop and read carefully: importing usually means your notes are about to live somewhere that is not a folder.
3. Check a hard note. Not a test note. Pick your worst one: nested lists, a table, a callout, an image, some frontmatter.
4. Save it, then diff the folder. If you keep your vault in git, git diff after an hour of use is the most useful five seconds in this whole process. If you do not, copy the file first and compare afterwards.

Step four is the one that matters and almost nobody does it. An app that reformats your files on save, renumbers a list you deliberately wrote as 1. 1. 1., or rewrites your YAML into its own preferred key order, has made a decision about your notes without telling you. You will find out eventually, usually as an enormous diff on a day you were doing something else.

What to open it with

Anything, honestly. TextEdit will show you a note. A folder of Markdown is readable in every editor ever written, and that is the reason to keep notes this way.

If you want an app that treats the vault as a vault rather than as a pile of text files, Skein is one option: it is a native Mac app, it is free, and it reads the same wikilinks, tags, frontmatter, callouts and .canvas files, with no import step. Its round-trip test suite exists specifically to prove that a file it opens and saves comes back byte for byte identical, because the promise above is worth nothing if the app quietly rewrites what it reads.

It also does not read .obsidian, so your Obsidian setup sits there untouched and Obsidian opens the folder exactly as it did before. You can run both against the same vault while you decide, which is the thing a database format never lets you do.

Other reasonable answers: Logseq OG if you want an outliner and open source, iA Writer or any plain Markdown editor if you only want to write, and Obsidian itself if it turns out the plugins were the point after all. Your files do not mind either way, which is precisely what you chose them for.

Checked 14 August 2026. I make Skein, which is named above, so weigh that accordingly. If something in this post is wrong, tell me.