diff --git a/guides/data-apps.mdx b/guides/data-apps.mdx
index 3f89ef98..82858c8d 100644
--- a/guides/data-apps.mdx
+++ b/guides/data-apps.mdx
@@ -122,6 +122,14 @@ When the agent wires up an export control, it can offer the user:
 
 Exports respect the same permissions, user attributes, and export limits as exports started from a chart or dashboard. Rows are generated by Lightdash and streamed to the browser as a real file download - the app itself never serializes the data.
 
+### Exporting to PDF
+
+You can ask the agent to add a PDF download button to any app — for example, "add a download as PDF button to the header" or "let me export this report as a PDF". This works especially well with the **PDF report** template, which is laid out for print, but you can add PDF export to any app.
+
+PDF exports are **image-based**: the app rasterizes the rendered pages in the browser and writes them into a PDF file. The output captures exactly what's on screen, including charts, tables, and styling, but the text in the PDF is not selectable or searchable. The file is generated in the iframe and downloaded directly — nothing is sent to the Lightdash backend.
+
+For text-heavy reports where you need selectable text, use the browser's built-in **Print → Save as PDF** option instead.
+
 ## Themes
 
 You can create shared themes to give your data apps consistent styles and instructions across your organization. A theme bundles CSS rules, fonts, images, and a `skill.md` instructions file that the agent uses when building the app. When creating a new app, you can choose which theme to apply, and you can set a default theme for the org.