Rewind the bug. Watch it happen.

What you can inspect

Seek through the timeline and change playback speed. Open the recorded clicks, console and request panels to see the context at that moment.

• Select a recorded click to jump to it.
• Inspect the captured element in the DOM inspector, as it was when it was recorded.
• See console and network entries for the capabilities that were enabled.
• Follow a request into your server with backend evidence, where it is set up.

Recorded where the review happens

Recording starts with a hosted review session, or in the browser extension when Record Session Replays is allowed for the device and project. Make a short test action first and check the replay before reproducing the bug.

A replay shows what was recorded. It does not re-run the original requests.

Export it, open it locally

Download a replay as a file, then open a supported .json or .json.gz recording in Claron's local player. The local player reads it in your browser without creating a new cloud recording.

Privacy first

Recordings can contain application text and data, so review with dedicated test accounts. Project diagnostic permissions control who can open cloud evidence; a downloaded file is a separate copy, so share it only with authorized people.