I spend a good part of every day in Markdown files: CLAUDE.md and AGENTS.md, specs, plans, READMEs. Most of the time I read them rendered, and that is exactly where I spot the typo or the sentence I want to change. Switching to the source, finding the same spot among the asterisks and brackets, fixing it and switching back gets old quickly.
Editors that let you type into the rendered view exist, but many of them work the same way under the hood: parse the file into a tree, apply your edit to the tree, and print the tree back out as Markdown. That last step is where things go wrong. The printer has its own opinions. *emphasis* turns into _emphasis_ , list numbers get renumbered, tables get realigned, line breaks move. You fix one word and your Git diff shows forty changed lines.
Splat is a native macOS Markdown editor I wrote in Rust, with the source and a live preview side by side. Both panes are editable, and the rule for the preview is strict: an edit in the preview may only change the bytes it has to .…