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.
macOS 14+ · In development
As fluid as Bear, as open as a folder
Markit is a native macOS Markdown editor. Syntax 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.
Not released yet — signing and notarisation aren't wired up, so there is nothing to download today. The editor further down this page is the real one, though: you can type in it right now.
Editor screenshot (Kami theme)
Write a line before you download anything
The block below is Markit's actual editor, running in your browser — same code, same typographic rules. It just has no disk to write to.
Nothing is saved, and there is no file tree, no tabs, no splits — those belong to the native shell. About 500 KB on first load.
01
Three decisions shape everything else
Real WYSIWYG
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.
Chinese typesetting, taken seriously
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.
02
What already works
This is not a roadmap. Everything below runs today.
- Saving won't wreck your diff
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.
- Tabs and four-way splits
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.
- Several folders, without blurring meaning
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.
- Findable
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.
- Wikilinks and tags
[[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.
- Drop anything in
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.
- Three themes, fonts included
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.
- Export
Export a self-contained HTML file (images inlined as data URIs, so a single file is enough to send someone) or a PDF.
03
What we deliberately don't do
This section says more about the product than the feature list does.
No invented syntax
Your files have to open correctly in VS Code, so nothing outside GFM gets added — not even ==highlight==.
No prose in a database
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.
No real-time collaboration
Writing alone isn't good enough yet. A second front can wait.
No plugin marketplace, no accounts, no sync service
iCloud and Dropbox already sync your folder. We don't need to do it a second time.
04
One page as proof
We laid out every piece of Markdown syntax the editor supports inside an essay you can actually read. This site and the app share one set of design tokens and one typographic standard — even the tint behind a callout comes from the same formula.
05
Questions people ask
- Can I download it yet?
Not yet. Signing and notarisation aren't wired up. When the first build is ready, this page gets a download button.
- Will it cost money?
Pricing isn't decided. What is decided: it will never hold your files hostage. Stop using it and your .md files still open.
- Is there a Windows version?
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.
- How is this different from Obsidian or Typora?
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.
- Does anything get uploaded?
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.