AiCoN

Home / Posts / Dillinger

WRITE, PREVIEW, EXPORT
Actual Dillinger editor showing a fictional Markdown handoff note beside its rendered preview
Unenlarged crop of the actual editor, 29 October 2026. Fictional note, not a logo.

Dillinger: preview Markdown and export a readable page

By AiCoN | Published 29 October 2026 | Sources checked 29 October 2026

Markdown is convenient to write, but raw punctuation is not always what you want someone to read. Dillinger gives you an editor and live preview, then exports the document. We imported a fictional handoff note, downloaded styled HTML and reopened the actual file to check its formatting. The important privacy detail: its policy says HTML and PDF exports are processed on the server.

Quick facts

Why use it beside a chatbot?

A chatbot can draft Markdown. Dillinger gives you a dedicated place to edit that source, see the rendered page beside it and export the actual document. That helps catch a malformed list or table before you share it. This is a writing and formatting workflow, not an AI accuracy check or a claim that the editor improves the facts.

Our styled-HTML check

On 29 October 2026 we used Import to open a fictional sample.md. The note contained Handoff note and Next steps headings, the word fictional in bold, Draft the summary and Review the links as list items, and a Task/Owner table with Draft/A and Review/B.

We checked the live preview, opened Export as and chose Styled HTML. The browser downloaded sample.html. We reopened that actual file in a browser and inspected the page. Both headings, the bold word, the two bullet points, table headers and all four data cells were present. We also checked those elements in the downloaded HTML rather than relying only on the preview.

Actual downloaded styled HTML opened in a browser with headings, bold fictional text, bullets and Task Owner table
Unenlarged crop of sample.html opened in a browser. This is the actual downloaded document, checked 29 October 2026, not a reconstruction.

The file contained inline page styling plus an external KaTeX CSS import. Our note did not use maths. We did not establish that the export is fully self-contained or works offline, and we did not test rendering in an email client, CMS or office application.

Try a non-sensitive note

  1. Open Dillinger. Start with fictional content, especially when checking an export route.
  2. Use Import to select a Markdown file, or write in the editor. Our test used file import rather than a connected cloud account.
  3. Compare source and preview. Check heading order, bold text, list boundaries and every table row.
  4. Keep a copy of the Markdown source. Browser autosave is useful, but clearing browser storage can remove drafts according to the policy.
  5. Choose Export as > Styled HTML. Reopen the download and inspect it in the application where it will be used before sharing.

Importing a file and linking a cloud account are different actions. We did not link Google Drive, GitHub, Dropbox, OneDrive or Bitbucket, and none is needed for the route tested here.

Local drafts, server exports

The official privacy policy says documents and editor settings live in your browser's localStorage and that it does not persist document contents on its servers. It separately states that HTML and PDF exports are generated on demand by the server, with submitted Markdown processed transiently and not retained after the response.

Those statements describe different stages. Do not turn browser editing into a claim that an HTML export never leaves the device. We used invented content and did not audit requests, retention, browser storage or security. Use an approved workflow for confidential notes.

The policy also describes cloud-provider connections, but we did not authorize or test any. A document visible on one browser is not proof that it has been backed up or synced elsewhere.

What this test does not establish

Sources