> For the complete documentation index, see [llms.txt](https://helpdocumentation.gitbook.io/user-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocumentation.gitbook.io/user-documentation/dynamic-experiences/dynamic-experience-pdf/create-a-dynamic-pdf-experience.md).

# Create a Dynamic PDF Experience

### **Steps To Create Dynamic PDF** 

1. Go to **Dynamic Experience** → Select **PDF Experience**.
2. Click on **Create New PDF** (top right) → Choose **Simple PDF** (for basic use case).
3. Add required elements like **Heading, Text, Image**, and insert additional **Pages** if needed.
4. Reorder, navigate, or delete pages using the **Page Navigator**.

#### Add Variables (For Dynamic Content)

5. Go to **Variables** → Click **Add Variable** → Define variable name and set a **Fallback Value** (used for preview/testing).

#### Customize Content

6. Select a **Heading/Text Block** → Insert the created variable → Customize font family, size, alignment, color, and styling from **Properties**.
7. Add an **Image** by uploading a file or pasting an image URL.
8. (Optional) Add a **Page Break** to move content to the next page.

#### Create Dynamic Table (For Invoices / Reports)

9. Create a new variable → Select **JSON Mode** → Add dummy JSON array data in fallback.
10. Insert a **Table Component** → Enable **Dynamic Table Mode** → Select the JSON variable as data source → Preview table with dummy data.

#### Save & Generate PDF

11. Give the template a clear **Template Name** → Click **Save**.
12. Go to **API Section** → Generate API Key (if not created) → Use it to generate PDFs programmatically.

#### Storage & Tracking

13. Go to **Storage Settings** → Enable **Cloud Storage** (Use your own credentials or platform storage up to 1GB).
14. Check **Credit History** to track PDF generation usage and deductions.

Your dynamic PDF template is now ready for use in invoices, reports, automations, or API-based generation.

{% embed url="<https://youtu.be/GB4-xJ45QDc?si=JAWrAnUZ7xtNsxbv>" %}


---

# 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://helpdocumentation.gitbook.io/user-documentation/dynamic-experiences/dynamic-experience-pdf/create-a-dynamic-pdf-experience.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.