Feature Request: Option to Name Exported PDFs After Page Title Instead of Site Name

[jakobganschow-zoom]

Summary
When using GitBook’s built-in “Export to PDF” functionality, the downloaded file name defaults to the site title (e.g., Zoom Technical Library.pdf), regardless of which page is being exported. It would be very helpful if GitBook could automatically name exported PDFs based on the current page title instead.

---

Current Behavior

• Exporting any page via … → Export → PDF → Current Page always generates a file named after the site (e.g., Zoom Technical Library.pdf).
• This behavior is consistent across all pages, so each PDF export has the same filename.
• Users can manually rename the file afterward, but this adds friction and inconsistency.

---

Desired Behavior

• When a user exports a specific page, the generated PDF file name should automatically match that page’s title (e.g., AI Companion.pdf instead of Zoom Technical Library.pdf).
• Ideally, this could be configurable — for example:
  • %page_title%.pdf (default)
  • %site_title% - %page_title%.pdf

---

Why This Matters

• Makes exported files easier to organize and identify when multiple PDFs are saved.
• Reduces manual renaming and potential confusion, especially for large documentation libraries.
• Provides a more professional and user-friendly export experience for readers and contributors alike.

---

Example

Page	Current Export Filename	Proposed Filename
AI Companion	Zoom Technical Library.pdf	AI Companion.pdf
Zoom Node	Zoom Technical Library.pdf	Zoom Node.pdf
Zoom Phone	Zoom Technical Library.pdf	Zoom Phone.pdf

---

Additional Context
This request originated from a user observation while reviewing internal documentation updates — they appreciated GitBook’s export feature but found it inconvenient that all files shared the same name regardless of content. Having the export filename automatically match the page would be a small but meaningful quality-of-life improvement.

---

Would it be possible to make the export filename dynamic based on the current page title?
Thanks for considering this enhancement — it would greatly improve usability for teams managing large GitBook libraries.