> For the complete documentation index, see [llms.txt](https://gitbook.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook.com/docs/publish/pdf-export.md).

# PDF export

Export a PDF copy of your GitBook content

### Allow readers to export a PDF version of your published content

To enable or disable PDF export for visitors to your [published docs site](/docs/publish/publish-a-docs-site.md), open **Customize** in the site sidebar and navigate to **Configure → Page actions**. From there, you can toggle **Export as PDF** on or off.

This setting determines whether or not **readers of your published content can download it in PDF format**. This feature is only available for **Essential and Ultimate sites**.

### Export your own internal content as PDF

However you decide to configure your published docs sites, all logged-in members of an organization on a Pro or Enterprise plan can export a page, or an entire section, from your internal knowledge base as a PDF file.

{% hint style="warning" %}
Note that links across sections are not currently supported when exporting internal content to PDF.
{% endhint %}

#### Export an individual page

1. Open the page you want to export, then open the page’s [Actions menu](/docs/reference/gitbook-ui.md#the-actions-menu)

   <picture><source srcset="/files/YjlF3Z9KMYv9aQiFzZKD" media="(prefers-color-scheme: dark)"><img src="https://1050631731-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNkEGS7hzeqa35sMXQZ4X%2Fuploads%2F89MTSo5XRpPMVr1T0rxS%2Factions.svg?alt=media&amp;token=2b5d001e-560a-4f29-8d22-de8163725ca1" alt="The Actions menu icon in GitBook"></picture>

   next to the page title.
2. Select **Export to PDF > Current page**.
3. Wait for the page to load, then click the **Print or save as PDF** button in the upper right to open your browser’s Print menu.
4. From here, you can save the page as a PDF or open it in your PDF viewer using the typical process for your browser.

#### Export an entire section

1. Open the [Actions menu](/docs/reference/gitbook-ui.md#the-actions-menu)

   <picture><source srcset="/files/YjlF3Z9KMYv9aQiFzZKD" media="(prefers-color-scheme: dark)"><img src="https://1050631731-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNkEGS7hzeqa35sMXQZ4X%2Fuploads%2F89MTSo5XRpPMVr1T0rxS%2Factions.svg?alt=media&amp;token=2b5d001e-560a-4f29-8d22-de8163725ca1" alt="The Actions menu icon in GitBook"></picture>

   next to the page title and choose **Export as PDF > All pages**. Alternatively, open the section’s **Actions menu**

   <picture><source srcset="/files/HXFvPsjDqbaBEhpH0WKJ" media="(prefers-color-scheme: dark)"><img src="https://1050631731-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNkEGS7hzeqa35sMXQZ4X%2Fuploads%2FPnnI41SqLSaKBNwT98fW%2Factions-horizontal.svg?alt=media&amp;token=99754200-a354-4ffe-931e-aa6322ea7395" alt="The Actions menu icon in GitBook"></picture>

   in the [section header](/docs/reference/gitbook-ui.md#space-header) and choose **Export as PDF** in the drop-down menu.\
   \
   *Note: This action is not available within a change request.*
2. Wait for the page to load, then click the **Print or save as PDF** button in the upper right to open your browser’s Print menu.
3. From here, you can save the page as a PDF or open it in your PDF viewer using the typical process for your browser.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://gitbook.com/docs/publish/pdf-export.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
