Use this page to understand how exported demos are reused and updated over time.
Projects help teams manage change
Recordings live inside projects so teams can organize demo work, revisit older walkthroughs, and keep improving them over time.
That matters because demos often need updates as the product changes. A project gives the team a consistent place to return to when a flow needs to be revised.
Reuse starts with export
A finished demo becomes portable after export.
Once exported, the same bundle can be embedded in multiple places as long as it is hosted at a stable public URL. That makes a single authored demo reusable across landing pages, docs, onboarding, support content, and other browser-based contexts.
Re-export when the walkthrough changes
If the same recording is updated, you can export it again and replace the hosted bundle with the latest version. Re-exporting the same recording is free.
A new export is only needed when you create a new recording.
Typical reasons to re-export include:
- the same recording was updated and the hosted bundle needs the latest version
- step wording or overlay guidance changed
- the demo needs better polish before publishing
What export does and does not do
Export creates a portable bundle that can be self-hosted and embedded where needed.
Export does not publish the demo to your website automatically. Hosting and deployment happen in your own environment after the bundle is downloaded.