---
title: "Bulk-update demos"
slug: "/help/demos/publish/bulk-update-demos"
last_updated: "2026-04-15T22:48:17Z"
zendesk_id: 46681023147795
zendesk_url: "https://help.walnut.io/hc/en-us/articles/46681023147795-Bulk-Update-Your-Demos"
locale: "en-us"
category: "Getting Started"
section: "Publishing, Sharing, and Updating Demos"
product: "demos"
topic: "publish"
displayed_sidebar: "demosSidebar"
sidebar_position: 4
tags: ["new features"]
---

## **Overview**

Keeping your demo library accurate and consistent is essential—especially as your product evolves or multiple teams build in parallel. 

Walnut’s **Update** **demos** feature allows you to push changes from a template to all connected demos instantly. Instead of updating each demo manually, you can make adjustments once at the template level and propagate them across every connected demo with a **single action**.

This ensures your entire library stays:

-   Accurate and up to date as product screens or messaging change
-   Consistent across teams and workflows
-   Aligned with your brand and workspace standards
-   Scalable to maintain as your demo library grows

---

## **Where to Find Update Demos**

You can access **Update demos** from the template's **Demo Launcher**.

1.  **Open** **any** **template**.
2.  Click the **Create & Share Demo** button in the top-right corner.
3.  In the **Existing Demos** list, click **Update demos**.

![](pathname:///images/decf4c8633007f10.png)

Walnut will then apply the latest version of your template to all connected demos shown in the Existing Demos list.

---

## **What Happens When You Use Update Demos**

When you click **Update demos**, Walnut:

-   Applies all updates from the template—such as new screens, edited content, structural changes, and section/guide adjustments—to every demo listed under **Existing** **Demos** for that template.
-   Ensures each connected demo automatically reflects the latest version of the template.
-   Preserves demo-specific settings (titles, share links, permissions), while syncing all template-driven elements.

:::note[🏆 Pro Tip]

You can still update individual demos one at a time by clicking the **three-dot menu (•••)** next to any demo in the **Existing** **Demos** list.

:::

---

## **When to Use Update Demos**

![](pathname:///images/f6d2da5fac025ebf.png)

Use **Update demos** whenever a shared template has been updated and multiple demos rely on it. Common scenarios include:

-   Product UI changes (new layouts, updated screens, or redesigned pages)
-   Revised flows, steps, or narrative sequences
-   Messaging or copy updates across key screens
-   Structural improvements (new sections, guides, navigation changes)
-   Brand style adjustments applied at the template level
-   Fixes to bugs or inconsistencies in a widely used template

If multiple teams rely on the same template, **Update demos** ensures every downstream demo receives the latest approved version without needing to be rebuilt or edited manually.

---

## **Best Practices**

-   **Review before updating:** Use preview mode to confirm that template changes look correct before pushing them to all connected demos.
-   **Update after major releases:** Run **Update demos** after significant product or messaging changes so all demos stay aligned.
-   **Communicate changes:** Let internal stakeholders know when a widely used template has been updated so they understand what changed in their demos.

---

## **Related Guides**

-   [Scaling Your Walnut Workspace: Governance, Organization & Content Best Practices](/help/account/scale-workspace)