# depapel vs md2docx

md2docx speaks directly to Markdown-to-Word buyers. depapel is the better fit
when the same Markdown needs both PDF and DOCX output, proof-backed features,
and one route for README or document handoff flows.

## Use depapel when

- You want both PDF and DOCX from the same Markdown source.
- You need themes, syntax-highlighted code blocks, tables, Mermaid, page breaks,
  or page numbers in the exported document.
- You want GitHub, GitLab, or Bitbucket file URL import plus tracked proof
  artifacts.
- You need one converter for review PDFs and editable DOCX handoff.

## Use the other tool when

- You are evaluating a Word-first tool and the deciding factor is a DOCX-specific
  templates or limitations story.
- You want a converter whose public surface is centered on Word-only docs,
  changelog, or template guidance.
- PDF and Git import are not part of the decision.

## Decision points

depapel emphasizes Markdown-aware PDF and DOCX output, tracked proof artifacts,
and public Git file URL import. md2docx is the better fit when the evaluation
is centered on a Word-first story rather than the broader Markdown handoff
surface.

## Product-backed proof

- [Open DOCX proof](/proof/layout-brief.docx)
- [Markdown to Word](/markdown-to-word)
- [Markdown to DOCX](/markdown-to-docx)
- [GitHub README to PDF](/github-readme-to-pdf)
- [depapel vs Pandoc](/compare/depapel-vs-pandoc)

## Limitation

depapel does not claim custom Word templates, mail merge, or DOCX-only
publishing automation. If those become the deciding requirements, use a
converter built around that Word-first workflow.