> For the complete documentation index, see [llms.txt](https://help.craftsmanplus.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.craftsmanplus.com/play/preview-and-share/preview.md).

# Preview

Play your project exactly as users will, test CTAs and dynamic content, and check it at any screen size.

**Preview** plays your project the way users will experience it, using the same player as the exported playable. Use it to test interactions, scene flow, and responsiveness before you share or export.

Preview always plays your latest changes, including ones you haven't saved yet.

***

### Opening Preview

Click the **Preview / Path View** button (the play icon) in the editor toolbar, or press **Alt + Cmd + P** (Alt + Ctrl + P on Windows). Preview opens in place of the editor, with [Pathview](/play/preview-and-share/pathview.md) beside it.

To return to the editor, click the back arrow in the top left or press **Esc**.

The name of the scene that's playing is shown at the top of the screen.

***

### Controls

Below the playable:

* **Mute / Unmute** turns sound on and off. Preview opens with sound on.
* **Restart** plays the project again from the first scene.
* **Portrait** and **Landscape** switch orientation.
* **Size** sets the screen shape the playable is shown at, like **2:1** or **16:9**, or choose **Custom...** to enter your own.

You can also drag the edges of the playable to resize it freely and check how your layout responds. The size then reads **Responsive**.

| Shortcut       | What it does              |
| -------------- | ------------------------- |
| **P** / **L**  | Portrait / Landscape      |
| **1** to **5** | 21:9, 2:1, 16:9, 4:3, 1:1 |
| **M**          | Mute or unmute            |
| **R**          | Restart                   |
| **Esc**        | Close Preview             |

***

### Testing CTAs and Actions

Preview runs your actions as they'll run live, with a few safeguards so you stay in the editor:

* **Launch URL** opens a **CTA Triggered** dialog instead of leaving the page. It lists the **iOS**, **Android**, and **Desktop** links the CTA would open on each device. Click a link to open it in a new tab.
* **Call Number** opens a **Call Triggered** dialog showing the number instead of placing a call.
* **Fire Tracker** really sends the tracking request, so third-party trackers will record it.

To see which analytics events your playable fires, open the [Analytics Event Monitor](/play/preview-and-share/analytics-event-monitor.md) from the header. Preview doesn't send data to your ANALYTICS dashboard.

***

### Testing Dynamic Content

If your project uses [Dynamic Content](/play/properties/dynamic-content.md), a dropdown appears below the playable for each type of condition, like **Time**, **Device**, or **Location**. Choose a value to see the content users would get, or **Fallback** to see what shows when no condition matches. See [Previewing and Testing](/play/properties/dynamic-content/previewing-and-testing.md).

***

### Sharing

Click **Share Link** in the header to create a link anyone can open, with a QR code for testing on a phone. See [Share Link](/play/preview-and-share/share-link.md).

{% hint style="info" %}
Layers you've hidden in the editor that no action shows don't appear in Preview, the same as in the export.
{% endhint %}

#### Animated Banners

For Animated Banner projects, Preview plays the banner as it's exported. Pathview, the Analytics Event Monitor, and the size and orientation controls aren't available.


---

# 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://help.craftsmanplus.com/play/preview-and-share/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.