What a good PDF export has to get right
Printing a rendered page is where most exports fall over: code blocks break mid-line, tables overflow the margin, and a heading ends up alone at the bottom of a page. Those are typographic problems, and they need typographic answers.
- Page size A4 or Letter, portrait, with margins you can change.
- Headings stay with the paragraph that follows them instead of orphaning at a page break.
- Tables repeat their header row when they run over a page.
- Code blocks wrap or scroll deliberately, never clip.
- Formulas render as typeset math, not as raw LaTeX or a blurry picture.
Review first, then freeze
A PDF is a dead end for the reader: they cannot comment in the margin, and any change means another file with “v3” in the name. So the order matters. Resolve the comments while the document is still live — a review link works without an account — then export once, and send a file that is genuinely final.
If a reviewer does need to comment afterwards, send the review link instead of the PDF. Same text, and their notes land beside the sentence they are about.
Questions this page gets
Do formulas survive the PDF export?
Yes. They are typeset as math, with the same layout engine that produces the Word equations, so an integral looks like an integral and not like a row of symbols.
Can I control page breaks?
Page size, margins and whether a section starts on a new page are settings in the export dialog. Automatic rules keep headings with their content, which handles most cases without manual breaks.
Is there a watermark?
No, on any tier. A watermark on a document someone is sending to a client would make the free tier useless, so there is none.
Where to go next
- AI apps over MCP — how the AI reads the latest text and why it can only suggest changes.
- Peer review without accounts — the step between “finished” and “sent”.
- Connect an AI app — five minutes, one endpoint.
- Working on a Mac? The desktop app opens the same documents from Finder.