# depapel vs Browser Print

Browser Print is useful when you already have a rendered page and need a quick
PDF copy. depapel is a better fit when the source is Markdown and the output
needs document features instead of whatever the browser print dialog produces.

## Use depapel when

- You want PDF and DOCX from the same Markdown source.
- The document has fenced code blocks, tables, task lists, images, or Mermaid diagrams.
- You need themes, syntax highlighting, page breaks, page numbers, and repeatable layout behavior.
- You want to paste Markdown, upload a `.md` file, or import a public GitHub, GitLab, or Bitbucket file URL.

## Use browser Print when

- The content is already rendered in the browser and a quick visual copy is enough.
- You do not need DOCX, Git import, Markdown-aware layout, or document themes.
- You are printing an existing web page rather than converting Markdown source.

## Decision points

depapel supports Markdown paste, upload, Git file import, PDF, DOCX,
syntax-highlighted code, page-break and page-number directives, Mermaid, and
tracked proof artifacts. Browser Print depends on the current page CSS and
print dialog.

## Product-backed proof

- [Markdown to PDF](/markdown-to-pdf)
- [Layout brief PDF proof](/proof/layout-brief.pdf)
- [Markdown to DOCX](/markdown-to-docx)
- [depapel vs Pandoc](/compare/depapel-vs-pandoc)

## Limitation

depapel is not a browser-page screenshot tool. If the source is already a
custom web page with interactive layout, browser Print or a browser automation
flow may be simpler.