One document.
One HTML file to send.

Give the reader one file, not a folder to assemble.

A Markdown document may rely on a sibling image folder. Standalone HTML packages the rendered document and accessible local images into one browser-readable file. Remote images you approve for export can be embedded too.

Before
Project update.md
Project update-assets/
└── chart.png

After export
Project update.html

This is a file you can send, not a hosted page or a public web address. The recipient opens the downloaded HTML in a browser.

Export the document in Zizeg.

1. Open and check the Markdown.If Zizeg is your default .md app, double-click the file. Read it in Preview, or use Split to inspect the source beside it; your chosen default view opens automatically. Make sure local images appear correctly.
2. Choose File → Export → Export to HTML…Give the new file a name and choose its destination.
3. Choose what belongs in the export.Leave Include front matter unchecked unless the document’s metadata should be visible. If remote images are present, choose which to embed.
4. Open the exported file in a browser.Check the headings, lists, tables, and images before sending it.

The export uses the document currently open, including recent edits, and follows your Preview typography. It leaves the editable Markdown source in place.

Not sure what the opening metadata is for? See the YAML front matter guide for a worked example and how to edit it in Source.

Know what travels inside the file.

Accessible local images and approved remote images are embedded as data. That means a displayed chart or screenshot doesn’t have to travel as a separate asset file with the HTML copy.

Ordinary links are different. A web link still leads to its website; a link to another local document does not become an embedded copy of that document. Include separately linked files when the recipient needs them.

Unapproved or failed remote images become placeholders instead of remaining live image URLs. The export is self-contained for its rendered content and embedded images, not an archive of every linked resource.

Try the exact copy you intend to send.

Open the saved HTML, not just the original Markdown. Check that the important images and tables appear. If a local picture was missing at export time, repair its path or replace it and export again.

Some mail systems or organizations restrict HTML attachments. If the recipient cannot receive one, export a PDF instead. Neither format requires them to install Zizeg.

The recipient can read the exported snapshot. Later edits to your .md file won’t update a copy you already sent; export and send a new version when needed.

Choose HTML for reading without fixed pages.

Standalone HTML is useful for a report, handover note, or reference document someone will read in a browser. PDF is usually the clearer choice for a fixed-page deliverable or printing. Markdown is the better handoff when the recipient needs to keep editing the source.

See Markdown, PDF, or HTML: which should you send? for the decision table and examples.

You can have Zizeg open finished exports automatically under Preferences → Export, making the final check part of your routine.