Portable output
Confirm exactly what gets exported. A single HTML file is simple to move; a folder can also work when its relative asset paths remain intact.
Deployment and handoff guide
Self-host an interactive demo without trapping it in a platform.
A self-hosted interactive demo is a walkthrough you can place on infrastructure you or your client controls. This guide explains when a standalone HTML export is the right format, what to inspect, and what ownership does—and does not—solve.
Choose the format first
“Self-hosted” can describe three different things.
| Format | Best when | You operate | Important tradeoff |
|---|---|---|---|
| Standalone screenshot export | You need a portable, controlled story that can be handed to a client. | The exported files and hosting location. | It is not a live app; interface changes require new screenshots and a fresh export. |
| In-product tour library | You are guiding authenticated users inside software you maintain. | The application integration, targeting, releases, and data handling. | It depends on your application and engineering lifecycle; it is not a separate sales demo. |
| Hosted demo platform | You want managed links, capture workflows, analytics, collaboration, and frequent updates. | Usually content and account configuration. | The vendor operates the delivery platform and may be required for the demo to remain available. |
These formats solve different jobs. A downloadable export is useful for file ownership and handoff; it does not automatically provide analytics, authentication, lead capture, or managed updates.
What to inspect before choosing an export.
Editable source
Decide whether you need only the finished demo or the builder and source code used to create it. Those are separate forms of ownership.
Offline behavior
Open the export with the network disconnected. Check whether fonts, scripts, images, navigation, and the closing action still behave as expected.
Content boundaries
Screenshot exports contain the screens and copy you place inside them. Remove credentials, personal data, and confidential customer information before delivery.
Five deployment checks
Test the file before you hand it over.
- Open it locally.
Use a clean browser window and walk through every Back, Next, Finish, restart, and closing-link state. - Test the intended host.
Upload it to the client-approved static host and confirm the exact public URL returns the expected file. - Check smaller screens.
Review text, controls, highlights, and images at desktop and mobile-sized widths. - Review accessibility basics.
Navigate with a keyboard, confirm focus is visible, and check that labels and contrast remain understandable. - Record the handoff.
Give the client the final export, editable project source when included, host location, update process, and agreed support boundary.
Ownership is not the same as maintenance.
Owning an export lets the client retain and host that version. It does not keep screenshots synchronized with a changing product, operate the hosting account, or guarantee compatibility with future browser or security requirements. Put update responsibility and hosting ownership in the project scope.
Create a client brief or plan the five-step story before building.
Downloadable source kit
Build offline, export one HTML file, and hand it off.
The $149 Agency Interactive Demo Kit includes a browser-based screenshot builder, editable HTML/CSS/JavaScript, three synthetic examples, and storyboard, discovery, QA, accessibility, hosting, quote, and handoff guides. It does not include hosted links, automatic capture, analytics, custom implementation, or ongoing support.
One-time purchase. Applicable tax is shown at checkout. No revenue or conversion result is promised.