Beautiful exports: PDF and DOCX¶

A PDF is still what people ask for when a document needs to leave the browser. Lawyers want PDFs. Compliance wants PDFs. Clients who aren't technical want PDFs. Print wants PDFs.

OpenDocs gives you one from any published doc — no separate tool, no Pandoc incantations, no wrestling with page breaks.

Getting a PDF¶

From the CLI:

opendocs export my-doc --format pdf --output ./my-doc.pdf

From the article page, there's a Download PDF button at the top. (It's on this page too — try it.)

You get back a typeset PDF with:

• Real typography — not "browser-print-a-webpage" typography.
• Syntax-highlighted code blocks.
• Proper page breaks and headers.
• A table of contents for long docs.
• Your workspace logo and brand color in the header (Pro+).
• A branded footer with your company name, tagline, and link (Pro+).

DOCX too (Pro+)¶

opendocs export my-doc --format docx --output ./my-doc.docx

Opens cleanly in Word, Google Docs, LibreOffice — every editor respects the styles. Headings come in as real Heading 1 / Heading 2 styles, not bold text pretending to be headings. Your reviewers can track-changes it, comment on it, send it around without anything breaking.

Branding¶

Free workspaces get OpenDocs' defaults — Arial, our purple accent, a small "Made with OpenDocs" footer. Fine for personal use. Pro and Team workspaces can customize:

• Brand color — one hex value, applied to accents, callouts, link underlines.
• Export font — pick from Arial, Inter, IBM Plex Sans, Lato, Merriweather, or Vollkorn. Serif for formal reports, sans for internal docs.
• Footer — your company name, a tagline, a link (like https://acme.com).
• Hide the OpenDocs wordmark on exports. Clients don't need to know how the doc was made.

Change any of these in Workspace Settings → Branding, and the next export picks them up. No re-publishing, no version bump.

Exporting in bulk¶

Need PDFs of every doc in a workspace for a compliance audit? Batch it:

opendocs export doc-1 doc-2 doc-3 doc-4 doc-5 --format pdf --output ./exports/

The CLI ships a zip with a manifest. Limit is 10 posts per export command; split longer lists into groups of 10.

What a clean export preserves¶

The output keeps:

• Code blocks — with the same Shiki syntax highlighting as the web view.
• Tables — properly sized columns, no wrapping disasters.
• Images — embedded at source resolution.
• Blockquotes and callouts — styled, not flat.
• Table of contents — auto-generated from headings, clickable in PDF viewers.

No "this rendered on the web but looks weird on paper" surprises.

When to use which format¶

Short version: PDF for "final, read-only." DOCX for "someone's going to edit this next."

Next → Pricing and CLI source code