How to Create Automatic Documentation from Videos
Most teams record a product walkthrough for video -- and then sit down to write the same walkthrough again as written documentation. That is the same work done twice. SlickVid's automatic documentation feature removes the second pass: enable one checkbox before recording and every page navigation is captured as a screenshot, timestamped and ordered, alongside your video.
How automatic documentation works
When you tick Create automatic docs in the SlickVid extension panel, the recorder captures a screenshot of the visible tab every time you navigate to a new URL. Those screenshots are uploaded with your recording events and passed to the AI processing pipeline alongside the video and Whisper transcript.
The result is a project that contains both a polished video and the raw material for written docs -- ordered screenshots, one per page navigation, each tied to the exact moment in the recording where the transition happened.
Screenshots are taken at the moment of navigation, not continuously. This keeps file size low and keeps the output relevant -- you get one image per step, not one image per second.
How to enable it
Open the SlickVid extension by clicking the icon in your Chrome toolbar. In the panel that appears, you will see three checkboxes: Special FX, Record audio, and Create automatic docs. Tick Create automatic docs before you click Start Recording.
That is the only step. The setting is saved, so it stays on for future recordings until you turn it off.
What you get
After the recording is processed, your SlickVid project contains:
| Without automatic docs | With automatic docs enabled |
|---|---|
| Polished video with narration and scene cards | Same polished video |
| No screenshots from the session | One screenshot per page navigation, timestamped |
| Written docs require a separate pass | AI can generate step-by-step docs from video + screenshots |
| Single output format | Video and documentation from a single recording session |
When to use it
Onboarding flows. Record yourself going through your own product's onboarding once. The video becomes the marketing demo; the screenshots become the help center walkthrough. Same five minutes of recording, two assets.
Internal SOPs. Teams that document processes for new hires spend hours screenshotting each step manually. Record the process with automatic docs on and the screenshots come out ordered and timestamped with no extra effort.
Support documentation. When a user asks how to do something, record yourself doing it. The screenshot sequence gives you the images you need to publish a written how-to alongside the video answer.
Release notes. Shipping a new feature? Record a walkthrough with automatic docs on. You get the launch video and the screenshots for the changelog entry in one pass.
Automatic documentation removes the second recording session. Tick one checkbox, record your workflow once, and get a polished video and an ordered set of step screenshots from the same session. For teams that produce both video content and written documentation, this is the fastest path from a product walkthrough to published assets.