Capture screenshots from a video or browsing recording
Docs Agent turns a moment in a video into a documentation screenshot. Point it at a second of a video and it extracts that frame as a PNG, saves it with your documentation files, and adds the markdown reference in the page you are writing. The video can be one you upload or the recording the agent makes while it browses.
Before you begin
Section titled “Before you begin”You need:
- An EkLine account with Docs Agent enabled.
- A repository connected to EkLine where the documentation lives.
- A source that contains the moment you want to capture, either an uploaded video or a session in which the agent browsed.
- For a browsing recording, the Sandbox tab under Settings > Docs Agent. If you don’t see it, contact support@ekline.io.
An uploaded video must meet these limits:
| Requirement | Value |
|---|---|
| Formats | MP4, WebM, MOV, AVI, MPEG |
| Maximum size | 500 MB |
Step 1: Give the agent a source
Section titled “Step 1: Give the agent a source”Choose the source that matches where your moment lives.
-
Sign in to the EkLine app and click New session in the sidebar. If the composer shows Docs and Marketing, select Docs.
-
Click the attachment icon in the chat panel and select your video file.
-
Wait for the upload to finish. When you send your message, the agent transcribes the video and reads what happens on screen, which takes a few minutes for a longer recording.
The video appears as an attachment in the chat panel once the upload completes.
Some tasks lead the agent to open a browser, for example when you ask it to document a page in your product. The agent records what it visits and keeps the recording with the session, so you can pull a frame from it afterward.
-
Ask the agent to visit the pages you want to illustrate. For example:
Open our pricing page and document the plan tiers. -
Watch the Live browser panel in the bottom-right corner of the editor to see the pages it visits.
-
Wait for the agent to finish browsing. The panel header changes to Recording, and the recording is available for the rest of the session.
To reach pages behind a sign-in, set up a sandbox first.
Step 2: Find the moment you want
Section titled “Step 2: Find the moment you want”Ask the agent where something appears in the video instead of scrubbing through the recording yourself.
Which second of this video shows the billing settingspage with the plan selector open?The agent answers with a timestamp. Ask follow-up questions if several moments look similar:
Is the success message visible at that point, or does itappear later?Step 3: Ask for the frame
Section titled “Step 3: Ask for the frame”Name the second you want and where the image belongs. Telling the agent what the screen shows helps it write useful alt text.
Extract the frame at 47 seconds and insert it intodocs/billing/change-plan.md after the "Open billingsettings" step. Write alt text describing the planselector.Extract frames at 12, 47, and 90 seconds and place eachone next to the step it illustrates indocs/billing/change-plan.md.Extract the frame from the browsing recording where thepricing table is fully visible, and add it to theoverview page with a caption.The agent extracts the frame, saves it as a PNG in your repository, and adds the markdown reference in the page you named.
Step 4: Check the image in the editor
Section titled “Step 4: Check the image in the editor”Select the image’s tab in the editor panel. The image renders inline, with the filename and a status badge below it. Click the preview to open the image larger.
Check that:
- The frame shows the screen or action you meant to capture.
- The image sits next to the step it illustrates.
- The alt text describes what the screen shows.
If the frame is wrong, reply in the chat with a corrected timestamp:
That frame is too early. The dialog is still opening.Extract the frame at 50 seconds instead.Step 5: Publish as a pull request
Section titled “Step 5: Publish as a pull request”-
Enable View All Changes in the toolbar to see a diff of what the agent created.
-
Click Raise PR. The chat box fills with
Open a pull request forand your repository’s name. Press Enter to send it, or edit it first to add instructions.
The agent opens the pull request and replies in the chat with a link. Extracted images commit alongside your documentation changes, so the page and its screenshots land in the same pull request.
Verify
Section titled “Verify”Confirm the capture worked:
- The image file appears in the editor panel and previews inline.
- The page you named has a markdown reference to the new image.
- The pull request includes both the page and the PNG file.
Troubleshooting
Section titled “Troubleshooting”| Issue | Solution |
|---|---|
| The agent says it cannot read the video | Check that the file finished processing and is under 500 MB in a supported format. Re-upload it if processing failed. |
| The captured frame is a moment too early | The screen was still changing at that second. Ask for a timestamp one or two seconds later. |
| The frame from a browsing recording looks low resolution | A recording captures the browser viewport at the recording’s resolution. For a crisp image, ask the agent to capture the page directly with a sandbox instead. |
| The agent cannot find a recording for the session | Recordings exist only for sessions in which the agent browsed. Ask it to visit the page first, then request the frame. |
| The image reference points at the wrong place in the page | Name the heading or step you want it after, then ask the agent to move it. |
Next steps
Section titled “Next steps”- Create documentation from a demo video: turn a whole walkthrough into a written guide.
- Browse authenticated pages with a sandbox: let the agent sign in to your product and capture pages directly.
- Create documentation: generate guides, READMEs, and references from your codebase and other sources.
Built on Potluck Docs, our open source template.