Moving from Pages to Databases in Notion: A Practical Guide
Learn when and how to transition from page-based organization to database-based workflows in Notion for better automation and collaboration.
How to export Notion proposals to PDF (without properties)
Learn how to export a Notion proposal to a clean, client-ready PDF—including how to hide properties, reduce layout issues, and improve formatting.
TABLE OF CONTENTS
If you want a client-ready PDF from Notion, the most reliable approach is to hide (or remove) database page properties, keep the layout simple, and export a clean “print view” page instead of your working database record.
Many teams draft proposals in Notion because it's fast to write, easy to collaborate, and great for templating. The problem starts when you need to deliver a professional PDF that looks like a traditional proposal document.
The core issue: database page properties and export formatting
If your proposal is a database page, Notion shows page properties at the top by default. When exported, those properties often end up in the PDF output.
Goal: make the proposal page itself the “document,” and treat properties as internal metadata.
Quick wins for cleaner Notion PDF exports
1) Hide properties before exporting
- In the page view, open the page’s properties panel.
- Hide the properties that are not meant for the client.
- Export to PDF.
If you only need to do this occasionally, this is the simplest approach.
2) Create a client-ready “print view” page
Instead of exporting directly from the working proposal page:
- Create a new page called something like Proposal (Client Version).
- Paste or sync only the sections you want the client to see.
- Export that page.
This approach avoids accidental internal fields and makes it easier to standardize formatting. For a related guide on managing what external viewers can see, read Notion Vendor Portal: Hide Fields and Track Changes.
3) Use simple structure that exports well
Notion exports best when your page is:
- One main column
- Simple headings (H2, H3)
- Short paragraphs
- Minimal nested toggles
4) Use a “cover” section that reads well as page 1
Include:
- Client name (anonymized in templates)
- Project name
- Prepared by
- Date
Then keep the rest of the document in a predictable section order.
Why headers and footers are hard in native Notion export
Notion’s built-in PDF export does not currently provide full Word-style control over:
- Per-page headers
- Per-page footers
- Page numbering styles
- Font embedding and layout rules
If headers and footers are a strict requirement, a common solution is to export to HTML or PDF, then apply branding, headers, and footers in a second step using a PDF tool.
Recommended delivery pattern (reliable)
- Build and iterate in Notion.
- Produce a client-ready print view.
- Export the print view.
- If needed, add headers and footers in a PDF tool.
When to stop fighting the export
If the proposal must be “pixel-perfect,” the most stable approach is:
- Draft content in Notion
- Generate a final PDF using a document tool designed for layout control
This keeps Notion as the system of record while the final PDF stays client-grade.
Get help setting up your proposal workflow
Building a repeatable Notion proposal workflow—template, client-ready print view, and clean export—usually takes a few iterations to get right. If you'd rather skip the trial-and-error, book a ZoomFlow session. One of our consultants will build it with you in real time and you'll own the workflow when the call ends.
Related Posts
How to Build a Secure Notion Client Portal (Multi-Tenant) Without Duplicate Databases
Learn how to build a secure Notion client portal using linked databases and filtered views. Give each client access to their own data — no duplicate databases.
Notion Vendor Portal: Hide Fields and Track Changes
Build a Notion vendor portal without exposing private properties. Learn a safe database split pattern plus an audit log event database to track every status change.
