Open a folder of .md files — an Obsidian vault, a repo's docs, a notes directory — browse the tree, edit each file in the full Markdown editor, and save straight back to disk. Nothing is uploaded.
An Obsidian vault, a repository's docs/, a notes directory. Every .md, .markdown, .mdx and .txt file inside it is listed, each one opens in the full Markdown editor, and Save writes back to the same file. Nothing is uploaded — the folder never leaves your computer.
Point it at an Obsidian vault, a repository's docs/ directory or a notes folder. Every .md, .markdown, .mdx and .txt file inside is listed in a collapsible tree with per-folder counts and a filter box. .git, node_modules, .obsidian and other dot-directories are skipped.
Ctrl/Cmd+S or the Save button writes to the file you opened, through the browser's File System Access API. There is no download-and-replace step and no copy in a temp folder.
Edits are written 1.5 seconds after you stop typing. The status bar says "Saved to disk" only after the write completed, "Unsaved changes" until then, and "Could not save — permission needed" if the browser refused — never what the code intended.
Before every write the file is read back. If Obsidian, a sync client or another editor changed it since you opened it, you are shown the choice instead of losing one version.
The same editor as /editor: colour-coded source, live preview, working spell check and Grammarly, find and replace, GitHub callouts, KaTeX and Mermaid, and twelve export formats.
The folder handle is remembered in your browser (IndexedDB, on your device). Next visit, one click reopens it — the browser may ask you to confirm access again, which is how the API keeps you in control.
Create a file in the current folder without leaving the page. Names are checked, .md is added if missing, and an existing file is never overwritten. Renaming and deleting are deliberately left to your file manager.
The folder is read and written by your browser on your machine. Open the Network tab while you edit — no request carries a file name, a path or a byte of content.
A Markdown file is plain text, so opening a whole folder of them has always meant a desktop program: VS Code, Obsidian, Typora, or an IDE. Those are the right choice for a full workday. For the other cases — a machine where you cannot install software, a quick fix to three READMEs in a cloned repository, a vault you want to check from a browser profile that has no Obsidian — the browser can now do the job itself, and can do it without sending the folder anywhere.
Chrome, Edge, Opera and other Chromium-based browsers on Windows, macOS, Linux and ChromeOS — the File System Access API that grants a web page read and write access to a folder ships there. Firefox and Safari have not implemented it, so on those browsers the page offers a plain file picker instead: files open in memory and Save downloads a copy. The page tells you which mode you are in rather than pretending.
No. The browser hands the page a handle to the folder and every read and write happens locally. Nothing about the folder — not the names, not the paths, not the content — is sent to a MarkdownTools server. The optional cloud workspace is a separate feature and is not involved here.
Yes. Open the vault folder and its notes appear as a tree; the .obsidian settings directory and .trash are skipped. Obsidian-specific syntax such as [[wikilinks]] and callouts is preserved as text — the preview renders GitHub-style callouts and standard Markdown, so a wikilink shows as written rather than resolved. If Obsidian is open at the same time and rewrites a note, the editor notices before saving and asks which version to keep.
The File System Access API grants write access per session by default. The page remembers which folder you opened, but the browser generally wants a fresh confirmation before a page may write to it again — recent versions of Chrome and Edge can remember the choice if you let them. That confirmation is a deliberate safety step, and the reason "Reopen last folder" is a button rather than something that happens on page load.
The listing stops at 5,000 Markdown files and 12 levels of nesting, and says so when either cap is reached rather than silently truncating. Individual files above 5 MB are refused for editing to keep the page responsive. A typical vault or documentation folder is well inside all three limits.
No. Both are destructive, and a web page with write access to your notes should do as little of that as possible. Create new files here; rename and delete in your file manager or in Obsidian, then reopen the folder.
The browser shows its leave-page warning while a file has edits that have not reached disk. Switching between files saves first, and if that save fails you are asked before the edits are discarded.
The single-document editor with local autosave and twelve export formats.
Open one .md file and read it rendered, with an outline and reading styles.
Wikilinks, callouts, embeds and tags with copyable examples.
Find broken links and anchors across a document before you publish it.
Tidy spacing, list markers and table alignment in one pass.
Every element with its syntax and rendered output.