
By Yamuno Team
24 Jun 2026
6 min read
Most Confluence documentation is written for internal audiences — people who have access to the instance and can navigate the space directly. But plenty of documentation ends up going to people who don't have Confluence access: clients receiving a project handover, stakeholders reviewing a technical spec, partners getting onboarded, or auditors requesting documentation exports.
Confluence's built-in PDF export exists, but it produces bare output: no cover page, no custom headers, no watermarks, and no way to save a consistent format so the next export looks like this one. For internal drafts that's fine. For a client deliverable, it's not.
This guide covers how to export professional, consistently formatted PDFs from Confluence for external distribution using PDF Exporter for Confluence.
The key to consistent output across a team is templates. An admin creates a "Client Deliverable" template once in Confluence Settings. After that, any team member exporting for a client selects that template and gets the same cover page, header, and formatting — without touching any configuration themselves.
Admin step (one time):
User step (every export):
Enable the cover page. For client deliverables, Corporate or Executive style works best:
Set the accent color to your company's primary brand color (hex). Upload your company logo. Add a subtitle field — "Prepared for [Client Name]" or "Confidential — [Date]" — as a manual step per export.
Enable the header with your company name or document series title, centered. This appears on every content page and reinforces the source of the document even when pages are printed individually.
Add page numbers (right-aligned) and a confidentiality notice (left-aligned):
Confidential — [Company Name] Page 1 of 10
This combination is standard for client-facing documentation in most professional services contexts.
For documents that are drafts or under review, enable the watermark with "DRAFT" at 0.15 opacity. Remove it from the template (or create a separate "Client Draft" template) when the document is final.
Enable for any multi-page export. Set depth to 2 (H1 and H2). This is especially important for handover packages and technical specs where clients need to navigate to specific sections.
Enable "Break before H1" so each major section starts on a new page. For longer documents, also enable "Break before H2."
A handover package typically spans multiple Confluence pages — architecture overview, runbooks, configuration guides, contact lists. Export the entire section as a page tree:
Alternatively, if you want a single combined PDF, check all pages under one parent. The exporter bundles them in page tree order.
A single-page export is appropriate for a spec document or proposal:
If the spec has an H1-level structure with multiple major sections, the table of contents and page breaks make it easy to navigate without Confluence access.
For regulatory submissions or audit requests, use a separate "Compliance Archive" template with:
Create this template with watermark enabled by default so it's never accidentally omitted on a compliance export.
If you export a weekly or monthly status report page to send to a client, the template eliminates the manual formatting step entirely. Update the Confluence page with new content, export with the "Client Deliverable" template, and the output is ready to send. The cover page, header, and formatting are consistent every time without any effort.
For clients receiving a complete documentation set (e.g., a full product documentation space), use the space export:
This is useful for project completion handovers, vendor certifications, or any situation where the client needs a complete copy of a documentation space they won't have ongoing access to.
Before the PDF goes to the client:
The preview step takes 30 seconds and catches the issues — wrong accent color, missing logo, leftover watermark — that would otherwise be visible to the client.
Featured App
Convert Between Markdown Files and Confluence Pages Effortlessly
Get product updates and tips straight to your inbox.
No spam, ever.
Confluence spaces accumulate attachments fast — and most of them are never referenced again. Here's how to audit, filter, and clean up attachments across your instance without breaking anything.
Read moreConfluence doesn't have a native charting macro. Here's how to embed fully interactive charts — bar, line, pie, doughnut — directly inside Confluence pages using HTML Macro and Chart.js.
Read moreKeeping docs in GitHub and Confluence in sync is a constant maintenance problem. Here's how to automate it so changes in your repo show up in Confluence without anyone touching a button.
Read more