> For the complete documentation index, see [llms.txt](https://docs.zingy.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zingy.ai/app-editor/page-editor/page-preview.md).

# Page Preview

The page preview feature enables you to assess a functional version of your page while designing it. Accessible through the Preview button located in the [main toolbar of the page editor](/app-editor/page-editor/page-editor-tour.md#main-toolbar), this allows you to test and evaluate the appearance and functionality of your page in real-time.

### Responsive Design

Page preview enables you to view your page across different screen sizes, including Desktop, Tablet, and Mobile. Located in the toolbar at the top, you can utilize the provided buttons to seamlessly switch between the various screen sizes.

<figure><img src="https://3401585094-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmnBepgycwgisXr9ya1N4%2Fuploads%2FIHPZUwOGSLLRc03dOobP%2Fimage.png?alt=media&amp;token=74000368-4259-40da-91cc-5387effffabd" alt=""><figcaption><p>Page Preview Toolbar with screen size buttons</p></figcaption></figure>

### Features

Using the page preview feature, you can test the following:

* The functionality of various widgets such as [Data Table](/app-editor/page-editor/built-in-elements/data-table.md), [Stripe Payment](/app-editor/page-editor/built-in-elements/stripe-payment.md), [Form](/app-editor/page-editor/built-in-elements/form.md), etc.
* Custom Javascript and CSS files
* The effectiveness of your [Page Flow](/app-editor/page-flow.md) logic in guiding users through different interactions and processes.

### Limitations

The following are some of the limitations in page preview when it comes to testing your page:

* [Link](/app-editor/page-editor/built-in-elements/link.md) elements with their [URL](/app-editor/page-editor/built-in-elements/link.md#href) set to another page in your app will not work.
* Custom JavaScript within your app that necessitates access to user peripherals such as the camera or microphone will not function.


---

# 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://docs.zingy.ai/app-editor/page-editor/page-preview.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.