Convert Markdown to Standalone HTML
What "standalone" means, why a self-contained file outlives a screenshot, and how to export one you can email or open offline.
What a standalone file contains
A standalone HTML export is a single file that carries its own content and the styles needed to make it readable. There is no external stylesheet to load, no script to fetch, and no dependency on the site you exported from. You can move the file to a USB stick, email it, or open it in five years with the site long gone, and it still looks the way it did when you made it.
Why a link-only export fails
A converter that emits HTML with a link to a remote stylesheet produces a file that looks broken the moment it is opened without a network, and one that may render differently on a different machine or after the stylesheet changes. The content is still there, but the reading experience is tied to something outside the file. That is the opposite of what a document export is for.
When a standalone file is the right deliverable
Email it as an attachment, commit it next to the source so the rendered view travels with the markdown, or drop it into a folder that is synced and read on a device without a markdown app. Anywhere the reader should see exactly what you see, a standalone file is the answer. A screenshot is the wrong tool because it is an image: unsearchable, unzoomable, and useless for copy and paste.
What breaks an export in practice
Three things: an external stylesheet link, a remote image with no local copy, and a script that draws part of the content. The first is the most common and the easiest to miss, because a converter that links a stylesheet produces a file that looks fine on your machine and broken everywhere else. The second is visible only offline. The third means part of the document is not in the file at all. A good export inlines or drops all three, which is why the file is bigger than the markdown it came from.
Accessibility that survives the export
A standalone file should keep its structure: real headings in order, real lists, a language set on the html tag, and text that reflows when the window narrows. Converting to images, or dropping the heading levels into bold paragraphs, destroys all of that. Keep the markdown structural and the export stays navigable by screen readers and readable on a phone, which is what a document is for.
Keeping the export small
A standalone file is only useful if it is light enough to email and fast enough to open. Inline styles belong in the head, not repeated on every element; images should be resized before they are embedded, because a single full-resolution photo can outweigh the whole document; and fonts should be system fonts rather than downloaded ones, which add megabytes for a marginal look. A good export is a few hundred kilobytes for a long document, not several megabytes.
Check before you send
Open the exported file in a browser with the network disabled. If it renders fully and nothing shifts when you scroll, it is genuinely standalone. If images or styles are missing, the file has an external dependency you did not notice. Run that check once on your first export of a given document and you will trust every later one.