Dubble

For a browser procedure, install the Chrome extension, start a recording, perform the task and stop capture. Dubble processes the result into a guide that can then be edited or shared. Start with a fictional workflow so the first capture contains no live customer details.

After recording, an editor can refine descriptions, add or remove text, replace screenshots and select another frame from a recording. This matters when a click sequence needs clearer context or a screenshot caught the wrong state.

The screenshot editor can annotate, crop and redact images. A redaction applied to a still screenshot does not hide the same content in an accompanying video; use the recording Blur control before capturing sensitive information and inspect both outputs before sharing.

Onscreen controls can pause capture while navigating through irrelevant or sensitive screens, resume it for the next step, or restart a recording. A sensible practice is to pause before opening a page that may expose data, blur it, and then resume.

A guide link can have adjustable visibility, with a workspace minimum privacy level. Before sending a guide outside the team, test its link with a separate viewer role and check the screenshots and any recording for information that should stay private.

Guides can be copied as rich HTML or Markdown, exported to PDF, or embedded where raw HTML is accepted. An embed reflects later edits automatically; a copied or exported file should be checked again after the guide changes.

Collections can organize several guides for readers. Publishing a collection does not make private or team-only guides inside it public, so test both the collection link and an individual guide link before relying on the result.

For work outside the browser, Dubble has a Mac desktop beta that can capture across native and web apps. Confirm whether that beta covers the team’s operating systems and applications before planning a desktop-wide rollout.