Dillinger Markdown Editor: 2026 Review and Alternatives
November 11, 2026 · 10 min read
Dillinger Markdown Editor: Features, Limits and Alternatives
The Dillinger Markdown editor is a free, open-source browser editor with a live preview, five cloud connectors and Markdown, HTML and PDF export. Its repository last changed in June 2026. This review checks its claims against its own source code and the live site, then compares it with StackEdit and our editor.
What the Dillinger Markdown Editor Is in 2026
Dillinger is Joe McCann's long-running web editor, and the version at dillinger.io today isn't the one most old reviews describe. Its GitHub repository, joemccann/dillinger, shows a rebuild on Next.js 14 with Monaco, the editing engine inside VS Code. It's MIT-licensed, and the repo's last push was in June 2026.
You open the site and type. There's no signup and no paid tier, and Dillinger's own FAQ says it has no usage limits. The left pane is Monaco, so you get Markdown syntax coloring while you write, plus optional Vim or Emacs keybindings in Settings.
A few extras come from the rebuild:
- Zen mode for full-screen writing, toggled from the toolbar (the README also lists a Cmd/Ctrl+Shift+Z shortcut)
- Scroll sync between editor and preview, on by default
- Import of
.md,.markdown,.txtand.htmlfiles, with HTML converted to Markdown - Image paste, which sends the image to Dillinger's server and inserts it as an inline data URL (5 MB cap per image)
Most coverage of Dillinger dates from its AngularJS years. If a page lists Medium as a connector or says your work lives in cookies, it's describing the old app.
Which Markdown Syntax Does Dillinger Render?
The Dillinger Markdown preview renders with markdown-it, a CommonMark-compliant parser, plus ten plugins. That gives it more syntax than most browser editors. We pasted this into dillinger.io to confirm each piece:
Water is H~2~O and 2^10^ is 1024.
==Highlighted== and ++inserted++ text.
*[API]: Application Programming Interface
The API returns JSON.[^1]
[^1]: Footnotes collect at the bottom of the preview.
Markdown
: A lightweight markup language.
Inline math: $E = mc^2$
@[toc](Contents)
In the preview, H~2~O gets a subscript and 2^10^ a superscript. ==Highlighted== becomes a <mark> and ++inserted++ an <ins> element. "API" gets a hover tooltip, the footnote jumps to a numbered list at the end, and the term and definition form a definition list. KaTeX typesets the math.
The last line is the one people miss. A bare [TOC] stays as plain text in Dillinger, but @[toc](Contents) builds a linked table of contents from your headings.
Raw HTML such as <details> renders too, after DOMPurify strips scripts and style tags. That contradicts older references that say Dillinger ignores HTML.
Two gaps showed up. Mermaid fences display as plain code, not diagrams. Code blocks get highlight.js class names, yet in our test the default preview showed them in a single color. Renderers disagree on details like these, which our guide to how Markdown preview works explains.
Cloud Sync With GitHub, Dropbox, Google Drive, OneDrive and Bitbucket
Cloud sync is the main reason to pick Dillinger over a plain editor. The sidebar has Import From and Save To menus for GitHub, Dropbox, Google Drive, OneDrive and Bitbucket. Each provider uses its own OAuth sign-in.
For GitHub you choose an organization, repository, branch and file. Dillinger opens the file, and saving writes a commit with a message you can edit. We prefer Dillinger for exactly this job: fixing a README or docs page in a repo without cloning it.
Read the permission screen before you approve. The GitHub connector asks for the repo scope, which GitHub's OAuth scopes documentation describes as full access to your public and private repositories. The Google Drive connector requests the full Drive scope rather than per-file access. If that's too broad, use a separate account or skip the connector.
Where Does Dillinger Save Your Text?
Until you save to a provider, your documents live in your browser's local storage. Auto Save is on by default. The current build uses a files key for all documents and a currentDocument key for the open one.
That design explains a common Stack Overflow question from people whose Dillinger text vanished. Clearing site data, using a private window or switching browsers starts you with an empty list. Dillinger keeps no server copy of unsynced drafts, so there's nothing to restore from. Other browser editors share this risk, as our online text editor comparison shows.
If text disappears, open your browser's developer tools before you clear anything. Under Application (Storage in Firefox), Local Storage for dillinger.io holds the files value as JSON with every document body inside.
Pasted images make this fragile. Each one becomes base64 text inside the document, and MDN's storage quota page puts local storage at up to 5 MiB per origin. A few screenshots can fill that.
Exporting From Dillinger: Markdown, HTML and PDF
The Export as menu offers four options:
- Markdown: the raw
.mdfile - HTML: the rendered body in a bare HTML page
- Styled HTML: the same page with Dillinger's CSS embedded (serif body text, styled tables and code)
- PDF: an A4 page with 20 mm margins
All four are requests to Dillinger's server, even the Markdown download. The PDF route launches headless Chromium through puppeteer-core and prints the styled HTML. There's no option for page size, margins or your own CSS.
There's no Word export. If you need a .docx, our Markdown to Word converter produces one on our server, and it counts against the free pool of 3 server operations a day.
Can You Self-Host Dillinger?
Yes. The README asks for Node.js 18 or later, then two npm commands once you've cloned the repo:
git clone https://github.com/joemccann/dillinger.git
cd dillinger
npm install
npm run dev
That starts the editor at http://localhost:3000. For production, run npm run build and then npm start, or deploy to Vercel, which the repo ships a config for.
The connectors need setup. You register an OAuth app with each provider and put its client ID and secret in .env.local. The README lists the permissions to grant, such as Files.ReadWrite and User.Read for OneDrive and repository read and write access for Bitbucket.
Skip that step and your self-hosted Dillinger Markdown editor still edits, previews and saves to local storage. Only the sync menus stop working. If you only need an editor inside your own app, compare JS Markdown editor libraries instead.
PDF export needs Chrome on the host. Outside Vercel or AWS Lambda, the code looks for a local Chrome install or a PUPPETEER_EXECUTABLE_PATH environment variable.
Where the Dillinger Markdown Editor Falls Short
The hosted site showed a sponsored ad in a strip along the bottom of the editor when we tested it. It's a single, small slot, but it's part of the free deal.
Other limits we found:
- No Mermaid. Diagram fences stay as code.
- Drafts are browser-only. Unsynced work is gone if site data is cleared.
- Offline is partial. The site says the editor keeps working once loaded, but we found no service worker, so a reload with no connection usually won't load the app. Exports need a connection too.
- No collaboration. There are no shared documents, comments or version history beyond your Git commits.
- No Word export.
None of these are dealbreakers for quick edits. They matter if you treat Dillinger as your only copy of a document, so it helps to see how it stacks up against two other browser editors.
Dillinger vs StackEdit vs This Site's Editor
For the wider field, see our roundup of the best Markdown editors. Here we compare just three browser editors on the points that differ most.
| Dillinger | StackEdit | This site's editor | |
|---|---|---|---|
| Cloud sync | GitHub, Dropbox, Google Drive, OneDrive, Bitbucket | Google Drive, Dropbox, GitHub, GitLab | None (sign-in saves to My Files) |
| Math | KaTeX, dollar delimiters | KaTeX | KaTeX, dollar delimiters |
| Mermaid diagrams | No | Yes | Yes |
| Footnotes | Yes | Yes (on by default) | No |
| Export | Markdown, HTML, styled HTML, PDF | Markdown, HTML, PDF (may ask you to sponsor first) | .md, HTML, PDF, DOCX |
| Account needed to write | No | No | No |
| Offline | While the tab stays open | Yes, per its site | No |
StackEdit's details come from its own site, welcome file and source code. Its GitHub repository hasn't had a push since July 2023.
Our editor has clear limits of its own. It has no cloud sync, offline mode, footnotes or colored code blocks. Free users can export up to 5,000 characters from the toolbar, and PDF, DOCX and HTML exports share the free pool of 3 a day. Downloading the .md file is unlimited.
Pick the Dillinger Markdown editor if your files live in GitHub, Bitbucket or a cloud drive. Pick our editor if you want Mermaid diagrams and a Word export without connecting any accounts. If you'd rather edit rendered text directly, see our WYSIWYG Markdown editor guide. For offline writing in a free desktop app, read our MarkText review.
Moving a document out of Dillinger takes one step: Export as, then Markdown, or copy the text from the editor pane. Our preview doesn't render footnotes, ==highlight==, the ^sup^ and ~sub~ shorthand, definition lists or @[toc], so rewrite those first. Raw <sup> and <sub> tags work in both editors.
This note uses only syntax that renders in both Dillinger and our editor:
Dillinger Questions, Answered
The Dillinger Markdown editor earns its place when your Markdown lives in a repo or a cloud drive, and its markdown-it plugins cover syntax few browser editors render. Keep its limits in mind: browser-only drafts, no Mermaid and no Word export. For diagrams, KaTeX and a DOCX export without connecting any accounts, open the editor and paste your text in.