Record your screen with the Chrome extension
Capture a browser workflow as ordered steps, then review the resulting tour in the editor.
Use Record your screen when the browser workflow itself is the source. Layerpath turns accepted clicks into ordered steps inside one editable tour. Use Create with Agent instead when you already have images, video, a supported link, or library media.
What the extension captures
Each accepted click is the main step boundary. The extension captures the visible page state for that click, the click location, and useful page context such as the page title, URL, and visible control labels.
Typing, focus changes, and scrolling can provide supporting interaction signals. They do not create steps by themselves. The typing signal does not include the characters you type, but the visible page screenshot can still contain text, form values, names, or other sensitive information.
Optional microphone narration can provide additional context while Layerpath prepares the tour. It requires microphone permission. When narration is on, audio playing in the recorded tab may also be captured. Narration can help communicate intent, terminology, sequence, and important moments, but you must review all generated content.
What is not captured reliably
- Hover-only actions do not create a step.
- Typing or scrolling without a click does not create a step.
- Drag interactions, canvas controls, and short-lived visual states may not produce a useful step.
- Dropdowns and modals are useful only when the intended state is visible at the captured click.
- Content inside embedded frames may be incomplete, especially when the embedded content comes from another site.
- Chrome settings, the Chrome Web Store, extension pages, and other restricted browser pages are not recordable.
- Other browsers are outside the current supported boundary for this page.
You can switch between normal Chrome tabs during a recording. Page access and visible state can vary between tabs, so verify every step before sharing.
Before you start
- Choose Record your screen as the starting path.
- Install the official Layerpath Chrome extension.
- Sign in to Layerpath in Chrome and confirm the workspace where the project should appear.
- Open a normal website. Chrome internal pages cannot be recorded.
- Use test data where possible. Remove passwords, personal information, API keys, private messages, and unrelated tabs from the workflow.
- Rehearse one clear path from start to finish. Deliberate actions produce a tour that is easier to review.
- Keep Chrome open until the Layerpath processing view appears after you finish.
Record the workflow
Open Record your screen
On Layerpath Home, choose Record your screen. Go to the normal web page where the workflow starts, then open the Layerpath extension from the Chrome toolbar.
If the extension asks you to sign in, complete sign-in in the opened tab. Return to the starting page and reopen the extension.
Start the recording
Turn on narration only if you want to speak during the workflow. If Chrome asks for microphone permission, allow it or turn narration off before continuing.
Choose Start recording. On a first recording, Layerpath may show How recording works. Review it and choose Start recording again.
Wait for the countdown to finish before interacting with the page.
Open the extension during recording to check the step count, pause, finish, or discard the capture. Perform the workflow in order
Select only the controls a viewer needs to follow. Each accepted click increases the step count. Use the count as an orientation aid, then verify every step in the editor after finishing.
If you need a break, open the extension and choose Pause. Pause stops step capture and pauses the screen and narration recording. Choose Resume when you are ready to continue the same recording.
While paused, choose Resume recording to continue the same capture or Finish recording to send the current steps to Layerpath. Finish the recording
Choose Finish when the workflow is complete. The control changes to Finishing... while the extension submits the recording and opens Layerpath.
The Layerpath processing view is the handoff acknowledgment. The Finishing... label alone does not prove that the recording reached Layerpath.
After the processing view opens, the source page is no longer needed for the active recording. Keep the Layerpath tab open to monitor processing.
Choose Discard only when you want to abandon the capture. At Discard recording?, choose Discard to delete the active recording or Cancel to return to it.
Wait for the project
Layerpath creates a project with one editable tour. The recorded clicks become ordered steps. A preview can appear before callouts, content, and optional voiceover are complete.
Follow the visible processing stages. Treat the handoff as complete only when processing reaches Done and Edit is available.
When processing is complete, the processing stages clear and Edit becomes available. 
Choose Edit to open the tour. Use the step counter to confirm that the ordered steps arrived. Compare the step count and sequence with the workflow you performed. Open several steps and confirm that each one shows the expected page state and target. Then continue with Editor basics.
Review the result before sharing
The expected result is a new project whose tour contains the browser actions in order. Verify all of the following before sharing:
- The project appears in the intended workspace.
- The tour opens in the editor.
- The number and order of steps match the recorded path.
- Each captured step shows the expected page state.
- Hotspots and callouts point to the intended action.
- Intro, Outro, callouts, and optional voiceover are accurate and supported by the recorded workflow or your narration.
- No password, token, personal information, or unrelated browser content is visible.
- The complete tour works in Preview.
If Layerpath is still preparing the project, use Understand processing to identify the visible state. Do not assume that a completed extension animation means processing has finished.
Known limitations and common mistakes
| Situation | What to do |
|---|---|
| The capture is shorter than three seconds or contains no accepted click | Start again and record one complete, deliberate path with at least one click. A very short or empty capture may not create a project. |
| You clicked the wrong control | If the rest of the recording is useful, finish and remove the unwanted step in Manage steps. Otherwise, discard and start again. |
| A dropdown, modal, or loading state disappeared too quickly | Pause before the action, prepare the state, resume, and click only after the intended state is visible. Confirm the result in the editor. |
| You need a hover, drag, canvas action, or embedded control | Record the closest reliable click state, then inspect the result. Do not assume the interaction itself was captured. |
| The page reloads during recording | Reopen the extension and check whether the recording and step count are still active. Continue only after the active state is visible, then verify the surrounding steps in the editor. |
| You close the original tab before finishing | Reopen the extension immediately. Continue only if the active recording and step count are visible. Screen and narration continuity may stop when the original tab closes. |
| You see a microphone permission error | Allow microphone access in Chrome, or turn narration off and start without it. |
Sensitive data and privacy
The extension can capture website content and user activity that is visible during the workflow. Treat every captured page as publishable source material.
- Use a test account and synthetic records whenever possible.
- Close private messages, unrelated tabs, notifications, and password managers before starting.
- Mute unrelated tab audio, calls, and videos before turning narration on.
- Do not enter passwords, access tokens, payment details, health information, or customer data during the recording.
- Remember that typed characters are not required for the page screenshot to reveal the final visible value.
- Review every step at full size before sharing the tour.
- If sensitive information appears, remove the affected step or record the workflow again with safe data.
When the result is not what you expect
The extension shows Restricted Page
Open a normal website in Chrome, then reopen the extension. Chrome internal pages and extension pages are not recordable.
The extension asks you to sign in
Complete sign-in, return to the website, and reopen the extension. Confirm the intended workspace before starting.
Start recording does not begin a countdown
Keep the source tab open and note the visible error. Reopen the extension once. If the countdown still does not begin, open Help in Layerpath and include the time, Chrome version, website domain, and exact message.
The processing view does not appear after Finish
Keep Chrome open and connected. Check Projects once for the new project. If it is not there, preserve the exact visible message and open Help in Layerpath. The extension attempts background retries, but a user-controlled retry is not currently available in the visible flow.
Processing does not reach Done
Keep the project and note the visible stage. Read Understand project processing. If the stage remains unchanged, open Help and include the project name, time, and visible message.
The project appears with missing or incorrect steps
Do not share it. Remove an unwanted step when the source is otherwise correct. If steps are missing or the captured page state is wrong, preserve the project and open Help with the affected step numbers.