How to Create a PDF with Sections: A Complete Guide
Organizing a PDF into clear, navigable sections transforms a flat document into something genuinely useful — whether you're building a report, a manual, an ebook, or a multi-part proposal. But "sections" means different things depending on the tool you're using and what you actually need the document to do.
Here's what you need to know about the mechanics, the methods, and the variables that shape the right approach for any given situation.
What "Sections" Actually Means in a PDF
A PDF with sections typically involves one or more of the following:
- Bookmarks (outline navigation) — clickable entries in a sidebar that let readers jump to specific parts
- Heading-based structure — visually distinct titles and subheadings that signal new sections
- Tagged PDF structure — underlying accessibility tags that define document hierarchy for screen readers and assistive tools
- Page breaks and visual dividers — design-level separation between sections within the layout
These aren't mutually exclusive. A well-structured PDF often combines all four. But they're built differently depending on which tool creates the file.
Method 1: Creating Sections from Word Processors 📄
Microsoft Word, Google Docs, and LibreOffice Writer all let you build section structure before exporting to PDF.
The key is using heading styles, not just visual formatting. If you manually bold and enlarge text to look like a heading, that formatting won't carry over as a proper PDF bookmark or structural tag. If you apply Heading 1, Heading 2, and Heading 3 styles from the style panel, those hierarchies are recognized during export.
In Microsoft Word:
- Apply heading styles throughout your document
- Go to File → Export → Create PDF/XPS
- In the options dialog, check "Create bookmarks using: Headings"
- This generates a PDF where each heading level appears as a nested bookmark in the sidebar
In Google Docs:
- Apply heading styles using the style dropdown
- Go to File → Download → PDF Document
- Google Docs automatically maps headings to PDF bookmarks in most cases
In LibreOffice Writer:
- Use the paragraph styles panel to apply headings
- Export via File → Export as PDF
- Under the General tab, check "Export bookmarks as named destinations"
The quality of the bookmark structure depends entirely on how consistently heading styles were applied before export.
Method 2: Using Adobe Acrobat to Build or Edit Sections
Adobe Acrobat (the full version, not just Reader) gives you direct control over PDF bookmarks, even after the file is created.
Creating bookmarks manually:
- Open the PDF in Acrobat
- Navigate to the page or location where you want a section to begin
- Open the Bookmarks panel (View → Navigation Panels → Bookmarks)
- Click the New Bookmark icon and name it
- Repeat for each section, then drag to nest sub-sections under parent bookmarks
Automatically generating bookmarks from structure: If the PDF was created with heading tags already embedded, Acrobat can recognize and generate bookmarks from them via Tools → Accessibility → Add Tags to Document.
Acrobat also lets you edit the document outline — the internal hierarchy that defines reading order and section flow for accessibility compliance. This matters more for formal documents (legal filings, government reports, accessible publications) than for casual use.
Method 3: Design and Layout Tools 🎨
Tools like Adobe InDesign, Affinity Publisher, and Canva Pro approach sections from a design-first perspective.
In InDesign:
- You can create a Table of Contents based on paragraph styles, which then maps to PDF bookmarks on export
- The Export Adobe PDF dialog has a dedicated Bookmarks tab where you specify which styles should generate bookmark entries
- Interactive cross-references and hyperlinks are also preserved
In Canva Pro:
- Canva generates a flat PDF without native bookmarks or tagged structure
- Sections exist visually (page by page) but there's no sidebar navigation
- This is fine for print-focused documents but limited for interactive digital distribution
In presentation tools like PowerPoint or Keynote:
- Slides act as natural sections
- When exported to PDF, each slide becomes a page, but section groupings from the slide panel may or may not carry over depending on the version and export settings
Key Variables That Determine Your Approach
| Factor | What It Affects |
|---|---|
| Source tool | Whether bookmarks generate automatically or need manual work |
| Heading style usage | Whether the PDF inherits document structure on export |
| PDF version/standard | PDF/UA requires tagged sections for accessibility |
| Reader environment | Some mobile PDF viewers don't display bookmark panels |
| Document purpose | Print vs. interactive digital use changes what "sections" need to do |
| File size and complexity | Large documents benefit more from deep bookmark hierarchies |
Accessibility and Tagged PDFs
If your document needs to meet accessibility standards (WCAG, PDF/UA, or Section 508 requirements), sections need more than visual headers and bookmarks. The PDF must be tagged — meaning the file's internal structure explicitly labels each heading level, paragraph, list, and table in a way screen readers can interpret.
Tagged structure is generated automatically from properly styled Word or InDesign exports. It can also be added or repaired manually in Adobe Acrobat Pro using the Tags panel.
An untagged PDF with sections that look correct visually may still fail an accessibility audit. A tagged PDF with a logical heading hierarchy will pass — and also performs better in some PDF search indexing contexts.
The Gap That Only Your Situation Can Fill
The right approach to sectioning a PDF depends on where the document starts (a word processor, design tool, or existing PDF), what the sections need to do (navigation, accessibility, print layout, or all three), and who the audience is. A simple internal report handled in Word and exported with bookmarks is a completely different task from a structured technical manual built in InDesign for digital distribution with accessibility compliance requirements.
The mechanics are learnable — but which combination of tools and settings fits your workflow is something only your specific document, audience, and output requirements can determine.