> 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/documentation/zh/publish/pdf-export.md).
# 导出 PDF
导出你的 GitBook 内容的 PDF 副本
### 允许读者导出你已发布内容的 PDF 版本
要为访问你的网站的访客启用或禁用 PDF 导出功能 [已发布的文档站点](/docs/documentation/zh/publish/publish-a-docs-site.md)，打开 **自定义** 在站点侧边栏中，然后导航到 **配置 → 页面操作**。然后，你可以切换 **导出为 PDF** 的开或关。
此设置决定是否 **你已发布内容的读者可以以 PDF 格式下载内容**。此功能仅适用于 **Essential 和 Ultimate 站点**.
### 将你自己的内部内容导出为 PDF
无论您如何配置已发布的文档站点，Pro 或 Enterprise 套餐下组织中的所有已登录成员都可以将内部知识库中的某个页面或整个章节导出为 PDF 文件。
{% hint style="warning" %}
请注意，在将内部内容导出为 PDF 时，目前不支持跨章节链接。
{% endhint %}
#### 导出单个页面
1. 打开你要导出的页面，然后打开该页面的 [操作菜单](/docs/documentation/zh/can-kao/gitbook-ui.md#the-actions-menu)
，位于页面标题旁边。
2. 选择 **导出为 PDF > 当前页面**.
3. 等待页面加载完成，然后点击右上角的 **打印或另存为 PDF** 右上角的按钮，可打开浏览器的打印菜单。
4. 在此，你可以按照浏览器的常规流程将页面保存为 PDF，或在 PDF 查看器中打开它。
#### 导出整个章节
1. 打开 [操作菜单](/docs/documentation/zh/can-kao/gitbook-ui.md#the-actions-menu)
，位于页面标题旁边，然后选择 **导出为 PDF > 所有页面**。或者，打开该章节的 **操作菜单**
在 [章节标题](/docs/documentation/zh/can-kao/gitbook-ui.md#space-header) 并选择 **导出为 PDF** 在下拉菜单中。\
\
*注意：此操作在变更请求中不可用。*
2. 等待页面加载完成，然后点击右上角的 **打印或另存为 PDF** 右上角的按钮，可打开浏览器的打印菜单。
3. 在此，你可以按照浏览器的常规流程将页面保存为 PDF，或在 PDF 查看器中打开它。
---
# 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/documentation/zh/publish/pdf-export.md?ask=&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.
