Pagepress

PagePress — PDF

CLI tool to convert local Markdown files into PDF documents, with built-in templates, syntax highlighting, and Mermaid diagram rendering.

Installation

If pagepress is not installed:

npm install -g @liustack/pagepress@latest
npx playwright install chromium

Before generating PDFs, check whether the local CLI is outdated:

pagepress check-update

If updateAvailable is true, upgrade in place:

pagepress self-update

If the update check returns checked: false, continue using the local CLI and do not block PDF generation on the network check.

If the command is not found, fall back to the install command above.

Decision Tree

When the user asks for PDF output, follow this flow:

1. User has a .md file → render directly with a template
2. User has no file, but wants a report/document → write the Markdown content first (into $ASSETS_DIR), then render it
3. User has raw data or code to summarize → create a Markdown report with headings, tables, and code blocks, then render it

Security: Remote URL inputs are not supported. Only local .md files are accepted.

Template Selection Guide

Pick the template based on the document's purpose:

If the user doesn't specify a template, use default. If they ask for something "fancy" or "polished", use magazine. If they want it to look like GitHub, use github.

Frontmatter

Markdown files support YAML frontmatter. The title field sets the document's <title>:

---
title: Q1 Performance Report
---

# Q1 Performance Report
...

If no frontmatter is present, the title defaults to "Document".

Mermaid Diagrams

PagePress has built-in Mermaid rendering — no preprocessing needed. Standard ```mermaid code blocks in Markdown are automatically rendered into SVG graphics in the PDF. This works with all templates.

Supported diagram types include flowcharts, sequence diagrams, class diagrams, state diagrams, ER diagrams, Gantt charts, and more.

## Architecture

` ```mermaid
graph TD
    A[Client] --> B[API Gateway]
    B --> C[Service]
` ```

Assets Directory

• Ask the user where generated PDFs should be stored.
• Remember the answer as $ASSETS_DIR for the session.
• If the user does not reply or accepts the default, use ${workspaceRoot}/assets.

Options

pagepress -i input.md -o output.pdf --template default

• -i, --input <path> — input Markdown file (remote URLs not supported)
• -o, --output <path> — output PDF path
• -t, --template <name> — template: default, github, or magazine
• --safe — disable external network requests and JavaScript execution
• --wait-until <state> — navigation waitUntil: load, domcontentloaded, networkidle
• --timeout <ms> — navigation timeout in milliseconds

When to use --safe

Use --safe when rendering Markdown that may contain embedded scripts. It blocks all external network requests and disables JavaScript execution in the Chromium renderer. Not needed for normal Markdown-to-PDF workflows.

Temporary Files

[!CAUTION] NEVER scatter generated Markdown files across the user's project. All intermediate files must go into $ASSETS_DIR (the same directory where output PDFs are stored).

This matters because writing temp files elsewhere triggers permission prompts and clutters the project. Keep everything in one place:

1. Write temp files to $ASSETS_DIR — avoids permission prompts and keeps files co-located
2. Clean up after render — delete the temp file immediately after a successful pagepress run
3. Keep only if asked — if the user explicitly asks to keep the source file, leave it in $ASSETS_DIR and report its path

Examples

# Markdown report with default template
pagepress -i report.md -o report.pdf --template default

# Developer docs with GitHub style
pagepress -i api-docs.md -o api-docs.pdf --template github

# Polished whitepaper with magazine layout
pagepress -i whitepaper.md -o whitepaper.pdf --template magazine

# Render with safe mode
pagepress -i untrusted.md -o output.pdf --safe