2026-09-09 · 9 min read

MDedit 2026: No-Telemetry Cross-Platform Markdown Editor

A small Tauri/Rust Markdown editor that draws its privacy line in the filesystem: no account, no telemetry, no upload, and writes scoped only to the file you save.

I have a rule about Markdown editors now. After testing a dozen of them this year, the split that actually matters is not split-pane versus WYSIWYG, and it is not open-source versus paid. It is whether the app can honestly say where your words go when you are not looking. Several popular editors can only gesture at an answer, and a couple quietly phone home with usage data by default. So when MDedit landed on Show HN on September 7, 2026 with a README line I had to read twice, I went to verify it myself.

The line was this: "MDedit has no account, telemetry, document upload, or server-side rendering. Documents remain local. Remote transmission of documents is out of scope." Most privacy pages soften that sentence with asterisks and marketing weasel words. MDedit wrote it as a hard guarantee, and then backed it up with an engineering detail in the same README that most editors would never admit to. This article is about why that detail matters, what MDedit actually does, and where it fits in a Markdown stack that ends with you publishing clean rich text.

Full disclosure before we go further

I should be honest about the numbers, because a lot of the buzz around this one is overstated. MDedit is not a wildly popular release. The Show HN post carried 2 points and 6 comments at the time I checked, and the repository on GitHub had a handful of stars as of September 9, 2026. It is MIT-licensed, created September 4, and pushed as recently as September 9, so it is being actively maintained — by one developer, from the look of it. Do not install it expecting a mature, battle-tested product with a big community. Install it because the privacy architecture is genuinely interesting and different, and because watching a tiny project push a strong real claim is exactly how you learn what to demand from the big ones.

The privacy claim worth reading slowly

Every "offline" editor can say it does not upload your files. Far fewer can say where the boundaries actually are at the operating-system level. MDedit's README makes two concrete engineering statements:

• Desktop exports use Tauri's native save dialog, which dynamically grants write access only to the selected destination — the app has no wildcard filesystem scope.
• Document saves and private recovery storage remain behind validated Rust commands.

What that means in practice on Windows: when MDedit needs to write, the operating system asks you where, and MDedit gets a narrow permission for exactly that location — not blanket access to your whole Documents folder, not an install-time confession that it may read anything on the drive, and not a renderer process with broad file privileges. In a Tauri app, the webview front-end runs with the least privilege, and every filesystem action that matters has to cross a validated Rust command boundary. The wildcard-scope statement is the kind of detail a privacy team writes when it has actually thought about the threat model, rather than when it is filling a compliance checkbox.

The rest of the README is consistent with that hardening. Recovery snapshots are stored locally so an unexpected shutdown restores your tabs, active document, and per-tab workspace state. A "Recent" menu remembers the last 20 files you opened or saved, and its history stays on the device. There is no account to log into, because there is no server. That is the entire privacy model, and it is coherent: MDedit is a local tool that does local things and nothing else.

What MDedit actually does

Strip away the privacy positioning and MDedit is a capable, conventional Markdown editor. The tabbed workspace keeps independent editing state per document, and you switch between Edit, Split, and Preview modes. Features include GitHub-flavored Markdown with task lists, tables, footnotes, and callouts; syntax highlighting; Mermaid diagrams and KaTeX math; per-document find-and-replace with whole-word and regex modes; desktop image and attachment import that copies assets into an assets folder beside the file; a table of contents; light and dark themes; and exports to HTML, PNG, PDF, CSV, and SVG.

A few small details show the developer thought about writing workflows. External-change detection fires every three seconds while the window is visible and when it regains focus, so if another tool touches your file on disk, MDedit offers a side-by-side compare instead of silently clobbering your edits. Closing the app always asks first, and with dirty documents it offers Save All & Quit, Quit and Restore Next Time, or Discard All & Quit. Attachments are capped at 20 MiB each, and HTML exports embed local images while PNG and PDF include them — which matters when you later want a self-contained document to publish.

# The part that wins me over is boring
#
# MDedit keeps a draft on disk with no account, no telemetry,
# and writes scoped to the exact file you save. When the draft
# is done, the publish step is separate:

## 1. Write and save locally in MDedit      -> draft.md
## 2. Open md2rich.com
## 3. Paste the Markdown in, copy rich HTML
## 4. Drop the HTML into LinkedIn / X / Medium / Notion

Now the same paragraph you type:

"MDedit keeps drafts **local**, renders *Mermaid* and KaTeX,
and exports to HTML, PNG, PDF, CSV, and SVG."

Paste that source through md2rich and it comes out as
proper rich text: bold and italic preserved, list bullets
kept, code blocks fenced — no \n literals, no stray
asterisks leaking into the published post.

Where I put MDedit in my stack

MDedit occupies a specific slot: the quiet, private authoring end. It is deliberately not an AI editor — no DeepSeek, no OpenAI wrapper, no Ollama hook, no server-side rendering at all. That is a real contrast with the editors I tested earlier this month, and it is the reason I reach for it on drafts I do not want a model (or a vendor) to see before I am ready. It is also cross-platform where some of its privacy-minded cousins are not: there is a Windows NSIS installer, an MSI, a portable .exe, a macOS Apple-silicon .dmg, and an Ubuntu/Debian .deb. Markdown Buddy, which I praised in August as the native-macOS single-purpose editor, only runs on macOS. MDedit is the closest thing to that philosophy that follows you to Windows and Linux.

That file-permission model is the cleanest part of the story to borrow, even if you never install MDedit. When you are choosing any writing or conversion tool, ask three questions the README answers outright: Does it have an account I am pressured to create? Does it send telemetry by default? And can it honestly describe the filesystem scope it requests? The tool that answers "no, no, and here is the exact boundary" is the one that treats your drafts as yours. The tool that hedges on any of the three is asking you to trust a marketing page over an architecture.

Two real Markdown-to-rich-text examples

Since the whole point of writing in Markdown is shipping the result somewhere richer, here are two blocks you can drop into md2rich to see the pipeline end to end. The first is a short, mixed-format paragraph a newsletter author would paste into LinkedIn:

Last week I moved my long-form drafting to a private,
no-telemetry editor. **Why**: I finally stopped trusting
apps that "store locally" but still phone home with usage
data. My default is now an editor whose *save dialogs*
grant write access to one file at a time — nothing more.

- No account
- No server-side rendering
- Files stay on my disk

The swap took an afternoon. Publishing still goes through
md2rich so the rich text lands clean on LinkedIn.

The second example shows a pattern I use for longer pieces that cross to X Articles or Medium: a short Markdown file with a heading, a task list, and a fenced code block. Converting it with md2rich keeps the heading as a heading and the code block fenced, instead of pasting a wall of raw text into the platform editor:

# My private-first writing checklist

- [x] Draft in a no-telemetry local editor
- [x] Keep the source file on disk, under version control
- [ ] Convert to rich text with md2rich
- [ ] Review the rendered HTML before publishing

The command that never leaves your machine:

    md2rich converts on the client, nothing uploads.

Both examples convert through md2rich entirely client-side — the site is a pure front-end tool with zero upload, which is the same privacy-first philosophy MDedit applies on the editing side. Write local, convert local, paste the finished rich text. No cloud in the middle.

Caveats worth typing in red

• Very early. A few stars, one main developer, created four days before its Show HN. Expect rough edges and fast iteration.
• Unsigned builds. macOS will warn about an unidentified developer; Windows will show a SmartScreen prompt. That is a friction cost of no paid notarization, not malware.
• WSL filesystem limitation. Replacing existing files on non-Windows-ACL filesystems (including WSL) is not yet supported when native permissions must be preserved — the README suggests Save As to a new filename as the workaround.
• Portable Windows build needs WebView2. If the Microsoft Edge WebView2 runtime is missing, use the NSIS installer.

The bottom line

MDedit is not going to replace your whole writing life, and it does not need to. It is a small, honest, cross-platform editor whose real contribution is that it states the local-only guarantee plainly and backs it with a no-wildcard-filesystem-scope design. For private drafting that travels between Windows, macOS, and Linux, that is a genuinely useful niche in 2026 — especially when so many "offline" editors quietly reserve the right to phone home.

When the draft is done, the publish step is separate and should stay that way. Keep your Markdown source local in an editor you trust, then turn it into rich text for LinkedIn, X Articles, Medium, or Notion with a converter that runs entirely in your browser. Try md2rich to convert your next finished draft.