All articles

LoveMarkDown · Markdown document packaging

What Is an MDZ File? Share Markdown Without Losing Its Images

Learn why MDZ packages Markdown and local assets together, when it is useful, and how it differs from plain Markdown, ZIP, PDF and a Git repository.

Published Updated
Existing LoveMarkDown Source and Visual workspace, captured for version 1.2, not an MDZ package screenshot.
On this page

You send a Markdown guide to a colleague. The text opens, but the screenshots are missing. Nothing is wrong with the writing: the .md file contains image paths, while the images themselves are still in a folder on your computer.

MDZ gives the document and its local resources one file to travel in. Its main value is a more complete handoff, not a new writing language or a promise of smaller files. The recipient can keep working with Markdown instead of receiving only a flattened, rendered copy.

What is inside an MDZ file?

Under the MDZip specification, .mdz is a ZIP container for Markdown and associated resources. An entry point identifies where reading begins; a manifest can supply metadata and declare document or project mode. A simple single-document package can omit the manifest and use an index.md at its root.

Here is an illustrative layout, not a download or an app screenshot:

setup-guide.mdz
  index.md
  images/
    connection.png
    settings.png

The Markdown still references the image by a relative path:

![Connection overview](images/connection.png)

Sending only index.md leaves that image behind. Sending the complete package keeps the relationship intact. It does not fix an incorrect path or supply a resource that was never included.

The value: a complete handoff with an editable source

Consider a setup guide containing instructions and two screenshots. A useful handoff includes all three files, with the same relative layout the author used. Packaging them together can reduce the chance that someone forwards the text without the screenshots or moves only part of the folder.

The same pattern applies to several everyday jobs:

  • Technical instructions: send the steps and the exact screenshots that explain them, rather than asking the reader to rebuild a folder structure.
  • Training material: distribute a lesson and its local illustrations as one attachment; the next instructor can revise the Markdown source.
  • Review copies: give a colleague an editable document with the images needed to understand the feedback, then produce a PDF for final reading.
  • A dated project handoff: keep selected documents and their assets in a portable snapshot. This is not a replacement for ongoing version control.

These are reasons to choose packaging, not measured claims that it makes every team faster. The practical check is simple: can the recipient open the copy and see the same included images without repairing paths?

MDZ, ZIP, PDF or Git: choose by the next person’s task

FormatA good fitWhat to keep in mind
Plain .md and an asset folderDay-to-day writing and source diffsKeep the folder structure when moving or sharing.
Generic ZIPA collection of arbitrary filesTell the recipient which document to open first.
MDZA packaged Markdown handoff with a known entry pointThe reader needs a compatible tool or an extraction workflow.
PDFReading, printing and fixed page layoutKeep the Markdown source separately for later revision.
DOCXA recipient’s Word-based review workflowConversion may change Markdown-specific constructs or layout.
Git repositoryChange history and collaborative source workAn archive is a snapshot, not branches, diffs or merge history.

MDZ does not need to replace PDF. One can be the editable source package and the other the reading copy. Nor is compression the deciding benefit: already compressed images may not become much smaller inside another archive.

Is every file called MDZ the same format?

No. The extension alone is not a universal interoperability guarantee. MDZip is an independent specification, not a single universally adopted Markdown standard. The wflixu/mdz project also uses ZIP and a manifest, but has its own metadata and asset conventions. Consumers need to understand the profile they are given, not merely recognize the suffix.

Standard MDZip is unencrypted ZIP. LoveMarkDown also supports selected password-protected ZIP and AME 7z document workflows; those compatibility options are not standard MDZip. If another editor must open the result, check its supported container, manifest and password behavior first.

For a straightforward exchange, start with unencrypted ZIP/MDZip and local relative images. A ZIP-based package can also be inspected with a compatible ZIP utility, then read from its entry Markdown file while preserving the asset directories. That fallback does not apply unchanged to a 7z or encrypted file.

Offline portability has a boundary

An included local image can travel with the document. An image still pointing to a remote URL does not become offline content merely because the document is archived. It may need a network connection, disappear later, or require access the recipient does not have.

LoveMarkDown packaging includes supported local resources; it does not automatically download remote images. Resolve missing resources before sharing, and check that you have permission to redistribute included assets. Avoid bundling credentials, private attachments or unrelated working files.

Password protection is an optional distribution choice, not DRM or password recovery. Share the password separately from the file, and check that the receiving tool supports that encrypted format. A compatible AI tool may be able to read the packaged content, but an .mdz suffix does not make every AI service accept archives or images; assess the tool’s data policy before uploading.

A practical MDZ workflow in LoveMarkDown

Start with an ordinary Markdown document and its local images. Keep the source readable; a package is an additional delivery option, not a mandatory workspace.

  1. Preview the document and check the relative image links.
  2. Export MDZ using ZIP/MDZip for the default compatibility path. Address any missing-resource warning instead of sending an incomplete copy.
  3. Open the exported copy and check the text and images. Try it in the recipient’s tool when interoperability matters.
  4. Send that package for an editable handoff, or export HTML, Word or PDF when the recipient needs a rendered copy instead.
LoveMarkDown showing Markdown source beside its editable Visual workspace
The existing Source and Visual workspace, captured for version 1.2. This illustrates Markdown editing, not a new MDZ package test.

As of October 13, 2026, these archive workflows are available in LoveMarkDown Direct 1.3.0. Single-document packages can be edited and saved; multi-document MDZip projects are read-only. The US Mac App Store also lists 1.3.0 as of October 15, 2026; other storefront availability may differ. This guide describes Direct archive workflows, not a cross-channel feature-parity test. Large image-heavy archives can use substantial memory, and password recovery is unavailable.

Choose a LoveMarkDown download or read the MDZ support notes before using a package for a real handoff. The 1.3.0 release article lists the version-specific capabilities and limits; the privacy policy explains local-document and network behavior.

The useful outcome is not simply having a new file extension. It is sending a Markdown document whose included images arrive with it, while keeping a source that can still be inspected and revised.

For the complete Mac workflow, read LoveMarkDown: One Mac Editor, Multiple MDZ Formats.