Session recording
Session recording captures page state and browser activity as timestamped events. The stored events form a recording that a player can reconstruct as a session replay. Capture settings determine which page content and interactions are included, so masking rules need to be in place before recording starts.
How it works
A script captures the page's initial state, then records changes and interactions. In rrweb, record() sends these events to an emit callback. Your application uses that callback to store or send the events.
The recording guide covers capture options. Apply data masking in the browser before sending events to storage.
Recording and replay
Recording captures the events. Session replay reconstructs them so you can watch the session. People sometimes use either term for the whole process.