> For the complete documentation index, see [llms.txt](https://docs.storylane.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.storylane.io/recording-demos/recording-screenshot-demos.md).

# Recording Screenshot Demos

* [Screenshot demo overview](#screenshot-demo-overview)
* [How to capture screenshot demos](#how-to-capture-screenshot-demos-now-with-ai)
* [Advance recording setting](#advance-recording-settings)

### 🖼️ Screenshot demo overview

With screenshot demos, Storylane captures images (screenshots) with each click along your recording flow. Screenshot demos are perfect to build quick, guided demos that *do not require on-screen edits.*

* **Build faster demos** - Screenshot demos are typically much quicker to capture, create, and load
* **Multi-media** **support** - Screenshot demos support images, videos, and GIFs for more flexibility
* **Zoom and blur** - Screenshot demos support zoom and blur to focus attention and anonymize PII
* **Multi-window support** - With screenshot demos, capture screens across different tabs and windows

### 📸 How to capture screenshot demos (Now with AI!)

1. Open the product screen you want to capture
2. Launch Storylane's Chrome extension
3. Select **Screenshot demo**
4. Toggle "Add content with AI" to auto-generate guides
5. Select **“Record new demo”** or **“Add to existing demo”**
6. Click through your product screens, each step is auto-captured
7. Select **Finish recording** once you've capture your screens
8. Your full flow opens in preview mode, ready for editing!

{% hint style="info" %}
Need a little help with storytelling? Let Storylane's AI help. Toggle "Add content with AI", select an AI tone, and click around to capture your product. We'll automatically generate contextual guides based on your clicks!
{% endhint %}

{% @storylane/embed subdomain="app" linkValue="1rglpvszzx16" url="<https://app.storylane.io/share/1rglpvszzx16>" %}

### ⚙️ Advance recording settings

A few useful tips to level-up your demo recording game:&#x20;

1. **AI Tones**: Pick a tone based on your use case to generate contextual guides based on your clicks.&#x20;
2. **Auto zoom**: Select the gear icon and toggle "Auto zoom" to automatically focus your viewers' attention on key areas of your product screen (this can always be added manually in the editor too)
3. **Video movements:**  Trying to capture your product in motion? Toggle "Record video movements" to automatically record clips of product moment (you can alway add your own video clips in post too)&#x20;
4. **Video screens:** Add external videos (mov, .mp4 files, etc.) to your screenshot demos. To add videos to a new demo, select "Create demo" in the Storylane dashboard and upload video files of your choice. For existing demos, head to the Storylane editor > select "Add step" > Select the "Video" tab > and upload video files of your choice. You may also trim, speed up, and mute/unmute the video in the editor.

<figure><img src="/files/7V97Wmhkp31FJCmdqdyF" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
If you need help or have any questions, feel free to contact us at <support@storylane.io>.
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.storylane.io/recording-demos/recording-screenshot-demos.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.