SagaSteps
Create a step-by-step guide from a website you are authorised to record. This illustrated guide uses fictional local content and shows the SagaSteps 1.0.1 workflow in ordinary Google Chrome 152.0.7977.82 on Linux. The program is supplied in the separate purchased bundle; this free pack contains no program.
1. Install the extension
After purchase, extract the buyer bundle and then extract program/sagasteps-extension-1.0.1.zip into a stable folder. Open chrome://extensions, enable Developer mode, choose Load unpacked, and select the extracted folder containing manifest.json in Chrome’s folder picker. Pin SagaSteps from the Extensions toolbar menu. The outer ZIP is not the installer.
Actual Chrome 152/Linux folder picker opened before selecting the extracted extension folder.
2. Create a guide and allow one site
Create a guide with a title and client in the editor or popup. Open an authorised http:// or https:// site, choose Allow recording on this site, then choose Allow in Chrome’s own permission prompt. Reopen the popup if it closes; check for Access granted. The fictional test used a localhost page. Remove access in the popup when finished.
Actual Chrome 152 optional site permission prompt for the fictional localhost page.
3. Record one step
Choose the guide under Record into, select Start recording, and work through the site. Clicks, submits, field changes, or Capture now can add visible-tab screenshots. Select Stop and inspect captured and skipped counts. The test captured one click with one step captured and zero skipped.
Actual Chrome 152 popup after one fictional click: one captured step, zero skipped.
4. Edit and mask
Open the editor. Rewrite headings and instructions, reorder or delete steps, then drag a mask rectangle on a screenshot or enter its coordinates and select Add mask. The recorder does not read typed form values directly as event text. Original local screenshots and captured page URLs can still contain them. URL queries are excluded from exports by default; enabling query export can include them. Review links as well as images. Adding a mask does not erase those original pixels. Export burns masks into new image pixels; use Burn masks into stored image to replace the local original when appropriate. Review every image before sharing. Burn masks into stored image is irreversible for that stored screenshot.
Actual Chrome 152 editor showing the fictional captured step and a 220 × 90 mask.
5. Preview, then export
Select Preview package to inspect the assembled guide and masked screenshots. Close preview to return to the editor; preview does not download or increment the version. Select Export ZIP package or Download HTML only. The tested ZIP contains index.html, guide.json, README.txt, and images/step-01.png. The 220 × 90 mask covered all 19,800 pixels in the exported PNG. Export requires a step; changes after an export receive the next version.
Actual Chrome 152 assembled preview before ZIP export.
Scope and rights
Tests exercised an ordinary Chrome 152/Linux Developer-mode install, Chrome’s actual site permission prompt, one click capture, one mask, preview, and ZIP export on a synthetic localhost page under Xvfb automation. Chrome for Testing 151/Linux passed a separate earlier check. Multi-step client workflows, Windows/macOS, repeated use, clean reinstall, interruption, full-v1 product acceptance, commercial keys, and live checkout remain unverified. No Web Store listing, cloud sync, operating-system capture, or video. Guides remain in this Chrome profile; export backups before removing the extension.
The free practice pack contains no program. Review every screenshot and mask before sharing a guide.