> ## Documentation Index
> Fetch the complete documentation index at: https://docs.usetool.bar/llms.txt
> Use this file to discover all available pages before exploring further.

# Replay Feature

> Replay captures an event timeline behind each screenshot so teams can reproduce flows and give developers richer context. It records a privacy‑aware HTML snapshot of the DOM in the background, stored locally with strict security, and only leaves your machine when you choose to share a replay link.

<img src="https://mintcdn.com/toolbar/ElQ93TL-Mz0OD55x/images/Replay.png?fit=max&auto=format&n=ElQ93TL-Mz0OD55x&q=85&s=a804377853b993d0e96245ffbb78b57d" alt="Replay Pn" width="1920" height="1440" data-path="images/Replay.png" />

### How Replay Works (User Flow)

<Steps>
  <Step title="Bug appears">
    You notice an issue during normal use.
  </Step>

  <Step title="Click Replay">
    Press the Replay button to open the Replay window.
  </Step>

  <Step title="Trim & curate">
    Use start/end handles to select the exact segment, remove noisy steps, and choose overlays (console/network).
  </Step>

  <Step title="Review & finalize">
    Preview the playback, confirm targeted elements, and add optional annotations.
  </Step>

  <Step title="Share">
    Generate a one‑link replay and push to your task manager.
  </Step>
</Steps>

### What Replay Does

* **Event Timeline**\
  See the exact sequence of user actions (clicks, navigations, inputs) and UI state changes around the incident.
* **DOM HTML Recording (Background)**\
  Lightweight, privacy‑aware HTML snapshots of the DOM captured in the background to reconstruct the page state without live access.
* **One‑Link Playback**\
  Share a single link that plays back the timeline with technical signals (console, network, environment) aligned to each moment.
* **Developer Context**\
  Pair the playback with device/OS, browser/version, viewport, console logs, and network summaries so the fix is clear.

### Privacy & Security

* **Local‑First Storage**\
  The HTML recording, timeline, and technical context are stored on the user’s computer by default and do not leave the device until a replay link is explicitly shared.
* **Data Minimization**\
  The recording prioritizes structure and state (DOM) over sensitive payloads. Credentials, cookies, and request/response bodies are not captured by default.
* **Secure Transport & Access**\
  When shared, replay data is transmitted over encrypted channels and scoped to the recipient workspace with role‑based access.

### FAQs

<Accordion title="Why Replay?">
  * **Reproduce flows**\
    Developers can play back the exact steps and UI transitions without guesswork.
  * **Faster triage**\
    Align console errors and network events to the precise moment they happened.
  * **Single source of truth**\
    A one‑link replay replaces scattered screenshots and threads.
</Accordion>

<Accordion title="Is Replay always recording?">
  Replay maintains privacy‑aware DOM snapshots locally and only leaves your device when you share a replay link.
</Accordion>

<Accordion title=" Do you capture sensitive data?">
  By default, credentials, cookies, and request/response bodies are excluded. Only what is needed for development is included.
</Accordion>