Markdown that reads like the finished thing
Headings, bold, lists and highlights render in place. The syntax appears only where your cursor is, so the source is always one keystroke away and never in the way.
Your notes stay
exactly where they are.
mado is a Markdown editor that opens a folder on your own disk and edits the files in place — in a browser tab, with nothing uploaded anywhere.
Open a folderFree · nothing to installChrome, Edge, Arc, Brave or Opera
1
Point it at a folder
Your browser asks once for permission to that folder — and only that folder. Nothing else on your disk is visible to the page.
2
Write
Notes open, save and stay plain Markdown files. The same files your other tools already read, byte for byte.
3
Close the tab
Everything is already on disk. There is nothing to export, sync or download — the folder was the document all along.
There is no server to send anything to
The editor is a static page. Once it has loaded, every read and write goes through the permission your browser granted to one folder — no account, no upload, no copy in anyone else's hands, and it keeps working offline.
What it does
PDFs beside the note
Drop a paper in and it opens in a pane next to your writing. Quote a passage and the quote arrives with a citation that points back at the page it came from.
Tables you can actually edit
Real cells, column widths that give the prose column the slack it needs, and a right-click menu for rows and columns — over pipe-table source a plain text editor still understands.
Links between notes
[[Wiki links]] resolve across the folder, with autocomplete over your own note titles and headings.
Diagrams and maths
Mermaid diagrams and KaTeX render inline, from the fenced blocks you already write.
Your folder, your structure
No library, no database, no import step. Rename a file in Finder and mado sees a renamed file, because that is all it ever was.
Before you click
- It needs a Chromium browser. Opening a folder from a web page is only offered by Chrome, Edge, Arc, Brave and Opera today. Safari and Firefox will say so rather than half work.
- Permission is per folder, per session. Reopening a recent project asks again — that is the browser's rule, and the reason the page can be trusted with the folder at all.
- Deleting puts notes in the project's own trash. A web page has no system Trash, so a deleted note moves to a
.trashfolder inside your project, where you can still get it back.