Start with what the recipient needs to do.
| Need | Send | Remember |
|---|---|---|
| Edit the source or continue the project | Markdown (.md) | Include local assets and preserve relative paths. |
| Read or print a fixed-page deliverable | Check pagination, table size, and included images. | |
| Read a document in a browser | Standalone HTML | Embed needed images and check whether HTML attachments are accepted. |
There is no need to make every recipient use your editor. Keep the Markdown as your working file, then create the copy that suits the handoff.
For a finished client report: usually PDF.
The client wants a stable document they can read, forward, or print. They don’t need to edit your Markdown source. A PDF gives you a clear page-based deliverable.
Before sending, check that the title, page breaks, tables, and images look right. Keep metadata out unless it belongs in the client copy. Use the Markdown-to-PDF walkthrough for the export steps.
Send the editable source separately only if it is part of the agreed handoff.
For a browser-readable reference: standalone HTML.
A colleague needs to read a project update with a few screenshots and tables. They don’t need fixed pages, and they can receive an HTML file. A standalone export can put the rendered text and images in one document.
They can open that file in a browser without installing a Markdown editor. Check any links to other files—embedding the pictures does not automatically bundle every linked attachment.
Use the standalone HTML guide. If their mail system rejects HTML attachments, PDF is a practical alternative.
For a project collaborator: Markdown and its assets.
A collaborator or coding agent needs to change the document, not just read the finished result. Send the .md and the files it depends on, keeping their folder relationship.
An editable handoff
Handover/
├── Plan.md
└── Plan-assets/
└── diagram.pngThe recipient should receive the folder contents together. If you create an archive, keep this structure when it is extracted.
Ordinary Markdown remains usable across many editors, although specialized syntax can render differently. The recipient does not have to use Zizeg. If images break after the move, see the image-path repair guide.
Keep the working document separate from the delivered copy.
Continue editing your Markdown source, and export a fresh PDF or HTML snapshot when the document changes. A previously sent copy does not update automatically.
In Zizeg, reading the source is free in Preview, Source, or Split. Editing and export require a one-time purchase or an active subscription. If you want an alternative editable version before experimenting, use File → Save As… (⇧⌘S).
Choose names that help people recognize the version they received. That is often more useful than sending all three formats without explaining which one they should use.
Before you send it, ask four questions.
- Does the recipient need to read, print, or edit?
- Can they open the chosen format in their environment?
- Have you included the images and other files they actually need?
- Are you sending the intended version without unwanted metadata?
Once those answers are clear, the format choice becomes straightforward. Send the readable snapshot or the editable source that matches the job.
