The Ultimate Guide to Standalone HTML & Offline Wiki Export for Markdown

A Markdown file is a great place to write a document and an awkward place to send one. The person you are sending it to may not have a Markdown viewer, will not see your Mermaid diagrams as diagrams, and will judge the work by how it looks when they open it.

Exporting to HTML solves that, but "export to HTML" covers several genuinely different outputs. This guide walks through each one, what lands inside the file, and which to pick.

If you have not styled the document yet, that step comes first: turning raw AI Markdown into presentation-grade HTML covers the presentation styles an export then carries with it.

---

1. What an exported document actually is

A Prisment export is a single .html file you can open by double-clicking it. There is no build step, no static-site generator, no server, and nothing to install on the other end.

Worth being precise about what that means, because "HTML export" is used loosely elsewhere:

• The Markdown is already converted. The file contains finished HTML, not Markdown plus a parser. Nothing re-parses your document when the reader opens it.
• The reading interface is real. The exported page has a header, an optional document index, a style picker and a focus mode — not a bare wall of text.
• It is a document, not an app. No account, no telemetry, no phone-home for your content.

---

2. Exporting one document

The Single File tab offers three outputs: a styled HTML page, the raw source file, or Print / PDF. Which one you want depends entirely on what the recipient will do with it.

Open Export and the single-document tab offers three cards:

The second card follows the file you are exporting: a .md file offers its Markdown, an .html file offers its raw HTML, a .yml file offers the YAML. It is a plain download of the source, with no conversion applied.

Print / PDF

This one does not download a file — it opens your browser's print dialog, where Save as PDF is a destination alongside your printers. What gets printed is the document alone: the file tree, the toolbar and, in split view, the Markdown source are all left off the page, and the presentation style's colours and typography are kept rather than stripped. Headings stay with their sections and tables are not split down the middle of a page break.

Reach for HTML when the recipient will read on a screen, and Print / PDF when the artifact has to be paper, an email attachment, or something filed against a ticket.

If your workspace has several files open, a Target document dropdown at the top of the dialog picks which one you are exporting — useful when the file you want is not the one currently on screen.

---

3. Exporting a whole workspace

The Multiple Files tab offers three outputs: All HTML Pages for independent documents, All Interlinked Wiki for documents that link to each other, and All Source Files for the originals. All three deliver a ZIP.

The multi-file tab is where the more interesting choices are. The filter field above the tree narrows it by name or by a pattern such as *.md, and Select All then acts on what the filter shows — so a whole folder of specs, or only the Markdown, is two clicks.

Workspace Export (All HTML Pages)

Every selected file becomes its own standalone HTML page, delivered as a ZIP. Each page stands alone completely — hand someone one file out of the ZIP and it still opens and still looks right.

Use this when the documents are independent: a folder of specs, a set of meeting notes, one report per client.

Interlinked Wiki (Recommended)

The same files, but exported as a browsable documentation site. Each page carries a file tree sidebar, and links between your documents are rewritten to point at the exported pages rather than at .md files that would 404.

Use this when the documents reference each other — an onboarding guide, an API handbook, an internal knowledge base. It is the difference between a pile of pages and something a reader can navigate.

For a worked example, building a solution design pack exports prose, live Mermaid diagrams and an OpenAPI contract as a single interlinked site.

All Source Files

The third card skips HTML altogether and gives you the selected files in a ZIP exactly as they are — Markdown, CSV, YAML, JSON and HTML alike, each at its place in the tree. Reach for it on a handover, when the recipient wants the editable source rather than the readable artifact, or to get the files out of a browser workspace that lives only inside the app.

---

4. How offline caching works

An exported page fetches its stylesheet and diagram runtimes from cdn.prisment.io on first open, caches them, and needs no network from then on. Opened for the very first time with no connection at all, it falls back to showing the complete text rather than a blank page.

An exported HTML file references its presentation styling and interactive diagram engines from cdn.prisment.io.

1. First Opening: The document fetches its CSS and diagram runtimes and immediately caches them via browser cache and service worker primitives.
2. Subsequent Openings: The file opens instantly with zero network requests, even when completely offline (on an airplane, in an air-gapped facility, or in a secure enterprise environment).
3. Guaranteed Fallback: If opened on a machine with zero internet connection on the very first try, the page gracefully displays the complete text content without throwing blank-page errors.

---

5. Summary

Pick HTML Page to send one document, Interlinked Wiki to send a set that cross-links, All Source Files for a handover, and Print / PDF when the copy must work with no network at all.

Prisment's export system is designed to make sharing documentation as simple as sending a single file. Whether you need a one-off technical RFC, a print-ready PDF, a ZIP of independent pages, or a multi-page interlinked wiki pack, your team gets publication-grade readability with zero server configuration.

The style an export carries is whatever the document had when you exported it — including one you built yourself. See designing custom document themes.