The file is the only truth
What you get is a plain .md on disk, not a row in a database. Put it in git, drop it in iCloud, open it in VS Code — all of it just works. You can leave for another tool any day, and your writing stays where it is.
Markit is a native macOS Markdown editor — for the Markdown you write, and for the pile your AI tools leave behind. Syntax is for parsers, the page is for you: it renders as you type instead of sitting in your way — and what lands on disk is an ordinary .md file. Commit it, sync it, open it in VS Code, or stop using Markit altogether. Your writing never needs migrating.
Markit is on the Mac App Store — macOS 14 or later, one universal build for Apple silicon and Intel. Rather not install anything? The online editor is the real editor too: open it, click the pen at the top right, and start typing.


What you get is a plain .md on disk, not a row in a database. Put it in git, drop it in iCloud, open it in VS Code — all of it just works. You can leave for another tool any day, and your writing stays where it is.
Asterisks and hashes turn into bold and headings the moment you type them, and the line under the cursor doesn't fall back to raw syntax. Chinese input stays uninterrupted — that was verified before a single line of feature code was written.
A 720px measure, automatic spacing between Latin and Chinese, emphasis dots instead of slanted glyphs, punctuation that never hangs wrong. Every one of those was decided against a written standard, not eyeballed.
This is not a roadmap. Everything below runs today.
Line endings, BOM and frontmatter are preserved byte for byte. Writes are atomic, so a killed process never leaves half a file. Conflicts are detected by content hash rather than mtime, which sync services rewrite for no reason. Fix a typo and the diff is one line.
Visual editing, raw source and reading, from the segmented control at the top right or with ⌘E and ⌘/. Source view is a real editor — the whole file, frontmatter included. Leaving reading view returns you to whichever editing view you came from, not always the visual one.
Select a passage, give it a colour and, if you like, a note — while editing or in reading view. Each of the eight colours has a name you can change (Key point, Question, Quote…), so the colour says what it means, and any annotation can become a to-do you check off. Notes sit in the margin beside the text, the sidebar gathers them across all your documents, and full-text search reaches inside them. None of it is written into the .md: edit a passage lightly and its highlight finds it again; delete it and the note waits in a list of its own instead of vanishing.
Drag a file from the sidebar, a link inside a document, or a whole tab — whichever edge of the editor you drop it on is where it splits. Quit and reopen: the layout is still there.
Open one file in two panes and the reading pane keeps up as you type — unsaved text included, without touching the disk or your dirty state. Drafts go only to panes in reading view; if nobody is looking, not a byte crosses.
The sidebar can hold several folders at once. But [[links]], relative image paths and rename scans resolve only inside the folder the document itself lives in — opening one more folder never changes what an existing document means.
One index per folder, with full-text search that actually works for Chinese. Quick open, full-text search, the command palette and backlinks all share a single panel; ⇥ moves between them.
[[Name]] and #nested/tags, written the way Obsidian writes them. Renaming a file tells you how many files it will touch before it touches them, then updates every reference.
Images, PDFs and media open as preview panes; code and CSV open as read-only syntax-highlighted views; an http link opens as a browsing pane. Each takes its own pane beside your document.
Mermaid diagrams and Markmap mind maps draw themselves in place, and show their source again when the cursor enters. One that fails to draw falls back to an ordinary code block rather than a blank hole. $…$ and $$…$$ go through KaTeX, in editing and reading alike.
Warm paper, cool white and dark, optionally following the system. Body text uses LXGW WenKai, bundled offline — the app has no networked runtime dependency at all.
English, German, French, Spanish, Japanese, Korean, Simplified and Traditional Chinese — the same eight this site speaks. Following the system is the default, and for Chinese it goes by script rather than region, so a Hong Kong system gets Traditional.
Export a self-contained HTML file (images inlined as data URIs, so a single file is enough to send someone) or a PDF. Your highlights and notes go along only if you tick the box for them — by default, the copy you send is clean.
AI tools generate plans, reports and meeting notes faster than anyone reads them. Here is what Markit does with a folder full of them.
Headings, tables and diagrams included. The sidebar holds several folders at once, so the docs/ of three different repositories can sit side by side without their [[links]] bleeding into each other.
A pane you haven't touched picks up the change as it lands. A pane holding unsaved work only tells you, and never overwrites it — so you can keep editing while the tool next door keeps generating.
Generated Mermaid is often subtly wrong. One that won't render falls back to an ordinary code block you can read and fix, instead of a blank rectangle. Markmap and KaTeX draw in place the same way.
Highlight the parts you're unsure of in the Question colour and write down what's unclear. Then press ⌥⌘E: the For AI template puts your request first — “Answer the questions in my notes one by one” is one preset, or write your own — followed by each passage with your note, numbered so the reply can say “on point 3”. The preview shows the length in estimated tokens before you copy it into whichever assistant you already use. Reading notes, a to-do list, quotes only, JSON or a template of your own cover the other uses.
The app has no networked runtime dependency at all. Whatever you were drafting, whatever your AI drafted for you and whatever you marked in it stays on your disk — until you copy it out yourself.
This section says more about the product than the feature list does.
Your files have to open correctly in VS Code, so nothing outside GFM gets added — not even ==highlight==. The highlights you make in Markit stay with Markit — in the app, or in your browser when you use the online editor — never in the file.
Bear can invent syntax because Bear owns the storage. We chose files, so we give up that freedom. A deliberate trade, not an unfinished one.
Writing alone isn't good enough yet. A second front can wait.
iCloud and Dropbox already sync your folder. We don't need to do it a second time.
AI is already writing. What's missing is the other end — reading it, and keeping it somewhere it won't rot. So the app doesn't reach the network, and nothing here goes to a model on its own. When you want to ask an AI about what you've read, Markit lays out your questions and you choose where to paste them.
We laid out the Markdown syntax you actually use every day — headings, lists, tables, callouts, code — as one essay you can read straight through, and it is the first document the online editor opens. This site and the app share one set of design tokens and one set of typographic rules; even the tint behind a callout comes from the same formula.
On the Mac App Store: macOS 14 or later, universal for Apple silicon and Intel. If you'd rather not install anything, the online editor works in Chrome or Edge — mount a folder from your disk and edits are written back to those .md files a second after you stop typing (⌘S writes immediately). Highlights and notes work there too, kept in that browser rather than shared with the Mac app.
The Mac App Store page always shows the current price — the one place that can't go stale. What won't change: it will never hold your files hostage. Stop using it and your .md files still open.
It's a v2 goal. The editor layer has been written under cross-platform constraints since day one — no file paths in the web layer, a requestId reserved in the bridge protocol. It's the shell that has to be rewritten. Until then, Windows can use the online editor — Chrome and Edge mount a local folder just the same.
The data model is close to Obsidian: files as truth, wikilinks, tags. The editing feel is closer to Bear: true WYSIWYG, no syntax markers. And Chinese typesetting has been a first-class concern since the first commit.
No — not by a single byte. They live in Markit's own library on your Mac, so the file opens exactly as before everywhere else. Rename or move the file, in Markit or in Finder, and they follow it. The price is that they don't travel with it: to take them somewhere else — to a colleague, another tool or an AI — export them with ⌥⌘E as Markdown, plain text or JSON, or tick the box to include them when you export HTML or PDF. In the online editor they live in your browser instead and aren't shared with the Mac app.
No. The app has no networked runtime dependency and bundles its own fonts. This website has no forms and no analytics either — see the privacy policy.