---
title: "Autoplay a demo"
slug: "/help/demos/edit/structure/autoplay"
sidebar_position: 24
tags: ["guided demos","settings","autoplay","autoplay guides","autoplay screens","non-guided demos","hybrid demos","unguided demos","blog link"]
topic: "edit/structure"
last_updated: "2026-09-18T17:31:35.642Z"
zendesk_id: 32068509108115
zendesk_url: "https://help.walnut.io/hc/en-us/articles/32068509108115-Autoplaying-Demos"
locale: "en-us"
category: "Explore Walnut "
section: "Glow Up Your Demos ✨"
product: "demos"
displayed_sidebar: "demosSidebar"
---

## **Overview**

**Autoplay** lets you create a more passive, guided viewing experience by automatically advancing screens or guide steps after a set duration.

This is especially useful when you want a demo to feel more like a lightweight product tour, looping showcase, or self-running presentation.

In Walnut, autoplay can be configured in two ways:

**Globally** at the template level for all screens or all guide steps

**Locally** on selected screens or selected guide steps only

Autoplay works well for embedded product tours, event demos, kiosk-style experiences, and guided stories where you want viewers to watch rather than click through every step manually.

---

## **Global vs Local Autoplay**

Walnut gives you flexibility to apply autoplay broadly across a template or only where it is needed.

**Global autoplay** applies autoplay to **all screens** or **all guide steps** in the template.

**Local autoplay** applies autoplay only to **specific screens** or **specific guide steps**.

If a global autoplay setting is turned on, it takes precedence over local autoplay settings for that same behavior type.

**Best practice:** Use **global autoplay** when you want a fully passive experience across the whole demo. Use **local autoplay** when only certain screens or guide steps should advance automatically.

For example, you might use local autoplay on an intro screen, a hero walkthrough, or a short sequence of announcement-style guide steps, while leaving the rest of the demo interactive.

---

## **Set Autoplay for All Screens**

Turn this on when you want every screen in the template to advance automatically after a set delay.

1. Open the template in **Edit** mode.
2. Open **Template Settings**.
3. Open the **General** section.
4. Scroll to **Autoplay All Screens**.

   ![Autoplay all screens setting in Walnut template general settings](pathname:///images/f5cfe586084f8447.png)

5. Turn **Autoplay All Screens** on.
6. Set the **delay duration** in milliseconds.
7. Optional: turn on **Show Control Bar** if you want viewers to pause or resume autoplay.
8. Optional: turn on **Loop** if you want the demo to restart automatically after the final screen.
9. Click **Save**.

Once enabled, the template will advance screen by screen using the timing you defined.

---

## **Set Autoplay for All Guide Steps**

Turn this on when you want guide steps to play automatically in sequence across the template.

**Good to know:** When autoplay is enabled for all guide steps, Walnut follows the existing guide order. Individual guide steps cannot override that sequence.

1. Open the template in **Edit** mode.
2. In the right-hand toolbar, click the **Guides** icon to open the Guides panel.
3. In the Guides panel, click the **gear** icon to open guide settings.

   ![Guides panel gear icon and settings access in Walnut editor](pathname:///images/07b45e7d4dc45692.png)

4. Open the **Autoplay** section.

   ![Autoplay section in Walnut guide settings](pathname:///images/7b5e1f24123c526a.png)

5. Turn **Autoplay All Guide Steps** on.
6. Set the **delay duration** in milliseconds.
7. Optional: turn on **Show Control Bar** if you want viewers to pause or resume playback.
8. Optional: turn on **Loop** if you want the guide sequence to restart automatically after the final step.
9. Click **Save**.

Once enabled, guide steps will progress automatically based on the template’s guide order and timing configuration.

---

## **Set Autoplay for Selected Screens**

Use local screen autoplay when only certain screens should advance automatically.

1. Open the template in **Edit** mode.
2. In the left-hand screen list, right-click the screen you want to autoplay and select **Autoplay screen**.

   ![Autoplay screen option from Walnut screen menu](pathname:///images/f99c2485928467f5.png)

3. Set the **delay duration** in milliseconds.
4. Click **Done**.

Repeat this process for each screen that should autoplay.

**Note:** Per-screen autoplay only runs when guides are not active. If the Template has guides, screen autoplay will not advance. Use **guide step autoplay** instead, or hide or remove the guides.

---

## **Set Autoplay for Selected Guide Steps**

Use local guide autoplay when only certain guide steps should advance automatically.

1. Open the template in **Edit** mode.
2. Click the **Guides** icon in the right-hand toolbar to open the Guides panel.
3. Select the guide step you want to edit.
4. In the Editor, on the step's own toolbar on the canvas, click the **Settings** gear. This is not the gear in the Guides panel list.
5. Turn on **Autoplay guide step** and set the **display duration**.
6. Click **Done**.

Repeat this process for each guide step that should autoplay.

**Good to know:** Step autoplay is available for **Modal**, **Point**, and **Beacon** steps.

**Scope:** Guide autoplay is set per step, or for all guide steps at once with **Autoplay All Guide Steps** in the guides settings. There is no per-guide setting. If **Autoplay All Guide Steps** is on, it takes precedence over a step's own setting.

---

## **Troubleshooting**

**Autoplay is set but the demo skips it or stays put?** Check whether the Template has guides.

Per-screen autoplay only runs when guides are not active. If the Template has guides, screen autoplay will not advance, even when **Autoplay screen** is set correctly.

To check, click the **Guides** icon in the Editor's right-hand toolbar. If the Guides panel lists any guides, the Template has guides.

To fix it, use **guide step autoplay** instead (see **Set Autoplay for Selected Guide Steps** above), or hide or remove the guides.

---

## **Guides with Audio Files**

If a guide step includes an audio file, Walnut will play the **full audio track** before advancing to the next guide step, regardless of the autoplay delay you set.

This ensures the audio experience is not cut off early when guide autoplay is enabled.

**Related resource:** [**Convert Text to Speech**](/help/demos/edit/guides/text-to-speech-in-guides)

---

## **Summary**

Autoplay helps you turn a Walnut demo into a more passive, polished, self-running experience.

Use **global autoplay** when you want consistent behavior across the full template, and **local autoplay** when only specific screens or guide steps should advance automatically.

When audio is included, Walnut always prioritizes full audio playback before moving forward.

**Final takeaway:**  
Autoplay is most effective when paired with a clear narrative, intentional timing, and the right format for your audience, especially for embedded tours, kiosk demos, and lightweight guided showcases.