Prepare a screen recording for a useful step-by-step guide

Choose one task with an observable finish

Pick a task such as inviting a teammate, enabling a reminder, or exporting one report. Separate unrelated tasks into their own recordings so each guide has a clear purpose.

Identify the finish first. A confirmation, updated setting, or downloaded file gives the reader a way to check their work. Include required permissions in the introduction.

Prepare a safe, readable workspace

Close unrelated tabs and notifications. Use a test account. Check both the page and surrounding browser or desktop areas for private information you do not want in the recording.

Keep text readable in the exported guide. Choose a screen or window containing the task, and keep controls within that area. On Mac, check Screen Recording permission; Accessibility permission is needed for global click tracking.

Record the complete path

Begin on the page your reader will recognize. Move steadily and pause when a menu opens or a result appears. Keep the final state visible long enough to capture it.

After stopping, inspect the frames before AI drafting. Remove duplicates, accidental clicks, and private information. Aryanna’s browser demonstration uses fictional screens; capture your own task in the desktop source package.

Choose an export for the handover

Use Markdown with images for editable team documentation, or a standalone HTML guide for instructions in one file. The current build can export a captioned WebM video; it records silent video, so narration is separate.

Check the actual export before sending it. The reader should see every step without access to your workspace. Keep the source recording for tasks that change frequently so you can replace the affected guide.

Put the steps to work.

See the capture, review, and export workflow. Review how recordings and AI requests are handled before using private information.