On this page
- What does session recording mean?
- How does session replay work?
- What a replay looks like in Session Recordings
- Session recording, heatmaps and analytics: what each shows
- What can you learn from session replays?
- What a recording cannot tell you
- Can a website record your screen or what you type?
- How do you record user sessions on a website?
- When should you use session recording?
- Frequently asked questions
- Try it on your site
- Sources
Session recording, also called session replay, is a way to save what a visitor does on a website, the pages they open, where they click or tap, how far they scroll and when they type, and play the visit back later. The replay is rebuilt from the page itself, not filmed, so there's no video, audio or camera, and a privacy-minded tool masks what visitors type before it leaves their browser. You see what someone did, never why.
Key takeaways
- Session recording, also called session replay, saves what a visitor does on a website and rebuilds the visit as a replay. It's not a video of their screen.
- Watch replays to spot hesitation, unexpected paths, broken steps and features nobody uses.
- Read a replay's Activity list first: the page the visit started on, quick-click runs and masked typing tell you where to press play.
- Treat your reading of a single replay as a guess until other visits show the same behavior, and use analytics to count how often it happens.
- Start watching right after a site change, when a number looks strange, or when a customer reports a problem.
- A website can't capture your screen, camera or microphone unless you allow it when the browser asks; a replay tool records what you do on that site's pages, typing included unless the tool masks it.
What does session recording mean?
It means capturing one visit to your website so you can play it back later. A session is one visit, from the moment someone arrives on your site to the moment they leave. Session recording and session replay are two names for the same thing; some people use "replay" for the watching and "recording" for the capturing.
Each recording follows one person through one visit. A traffic report does the opposite, adding every visit together into totals and charts.
How does session replay work?
A recording is a reconstruction, not a video. While someone browses, the recording notes the structure of each page and every event that happens on it. Page views, clicks, scrolling and taps each become an entry in a list. Later, a player uses that list to rebuild the page and act out each event in order.
Sheet music is a useful comparison. The recording stores the notes, meaning what was on the page and what the visitor did. The player performs them back for you.
Nothing films the screen. There is no audio and no camera. Because the replay is rebuilt from your own page, it looks like your site, and a phone visit plays back in the shape of the phone, so you see the same narrow view the visitor had.
How a recording is made, step by step
- A small script loads with the page. Some tools ask you to paste it into your site's code; on Shopify and Wix, some come as apps that add it for you.
- When the visit starts, the script takes a snapshot of the page's structure, its DOM, and turns it into text it can send, a step rrweb's docs call serialization.
- As the visitor moves around, it notes each change to the page and each click, tap, scroll and keystroke, with the time it happened. Browsers report page changes through their MutationObserver interface, which rrweb uses to record them.
- A privacy-minded tool masks typing in the visitor's browser, so what they typed is replaced before anything is sent.
- The notes go to the tool's servers in small batches while the visit goes on.
- To play the visit, a player rebuilds the page from the snapshot and acts out each event in order, at the size of the visitor's window. rrweb rebuilds it inside a sandboxed frame and runs none of the page's own scripts, which is why a replay shows what changed rather than re-running your site.
What a recording captures
- The pages a visitor views, in order
- Clicks on a computer and taps on a phone
- Scrolling, including how far down each page they went
- That someone typed into a field, and where they paused
What stays out
- Typed text. A privacy-minded tool masks what visitors type before it leaves their browser. In Session Recordings, text typed into a form field shows up as asterisks, so you can see that someone filled in a field without seeing what they wrote. Here's how typing in form fields is masked in the browser.
- People who said no. A tool that respects consent leaves out visitors who decline analytics cookies in your banner.
- Everything outside the tab. Other tabs, other apps and the room the visitor is sitting in never appear.
What a replay looks like in Session Recordings
In Session Recordings, a replay opens as your page, rebuilt, with an Activity list beside it: every moment of the visit in order, each with the time it happened. Click a row and the replay jumps there. These are the rows you'll see most.
| Row | What it means |
|---|---|
| Page view, with the page's address | The page the visit started on, such as /product-page/linen-apron |
| Click | A click or tap. Quick clicks in a row merge into one row with a count, such as ×4 |
| Typing (masked) | The visitor typed into a field. The replay shows asterisks, never the words |
On a Shopify store, the list also has a Page view row for every page, a Searched row with the words the shopper used, and Add to cart and Checkout rows. Some themes' buttons show up as plain clicks instead.
Read top to bottom, the list tells a short story before you press play. Take a made-up visit to a shop that sells aprons:
- 0:00, Page view, /product-page/linen-apron
- 0:41, Click ×3
- 1:05, Click
Three quick clicks on the product page, one more click, then nothing. Press play at 0:41 and the replay shows the rest: in this visit, the shopper tapped something that didn't respond, then clicked through to the shipping policy and left, probably still looking for delivery costs. That gives you two things to check on one page, and the moment to start watching: 0:41.
The player skips quiet stretches by default, and visits still in progress are marked LIVE in the list so you can follow one a few seconds behind. Each visit is listed with its time and how many pages it covered. Guests aren't identified (the list names them Visitor plus a short code); on a Wix site, visitors signed in as members show by name, and on a Shopify store nobody is named.

Session recording, heatmaps and analytics: what each shows
They answer different questions about the same visits: analytics counts visits, a heatmap adds up one page's clicks and scrolling, and a session recording shows a single visit as it happened.
| Tool | What it shows | The question it answers |
|---|---|---|
| Analytics | Totals: visits, sources, pages and sales | How many people came, and where they dropped off |
| Heatmap | One page's clicks and scrolling, added up over many visits | Where people click, and how far down they scroll |
| Session recording | One visit, replayed in order | What one visitor did, step by step |
Most questions need two of them in turn: analytics to find the page that loses people, then replays of that page to see what happens there. Session replay vs heatmaps vs analytics matches common questions to the right tool. Session Recordings makes replays and heatmaps from the same visits.
What can you learn from session replays?
Replays are best at showing how people use your site.
- Hesitation. A visitor scrolls down, back up and down again over the same section. Something there is unclear or missing.
- The real path. You may picture visitors going from the home page to a product to the cart. A replay might show someone reading your About page and your returns policy first, which tells you what they need before they trust you.
- Broken steps. A button does nothing, an error appears, or part of a page never shows up.
- Unused features. You added a size filter last month. Replays show whether anyone touches it.
- What people came for. A visitor who skips your banner and heads straight for the menu arrived with something specific in mind. Where they go next tells you what it was.
A hypothetical example: you sell handmade soap, and visitors reach your gift sets page and leave without buying. You watch a handful of those visits. Each person scrolls past the photos to the bottom of the page, scrolls back up and leaves. Maybe they want ingredients or delivery times the page never mentions. Now you have something specific to test.
Session recordings, private by default
What visitors type into form fields is masked in their browser before it's sent, and recording follows your cookie consent. Free forever.

What a recording cannot tell you
A recording can't tell you why someone did something, what happened outside your site, how many people did the same, or anything about visitors who declined analytics. Knowing those limits keeps you from reading too much into a single visit.
Why someone did something
A replay shows actions. The reasons stay in the visitor's head. A long pause might mean careful reading, confusion or a knock at the door. Treat your explanation as a guess until other visits back it up, or hear the reasons first-hand in a small usability test, where a few people think aloud as they use your site.
What happened somewhere else
If a visitor opens another tab to compare prices, the replay shows them leaving your page and maybe coming back later. Phone calls, distractions and second devices stay invisible.
How many people did it
One replay is one person. Recordings show how something happens, and analytics show how often. For totals, conversion rates and traffic sources, you need an analytics tool, and session replay, heatmaps and analytics compared helps you pick the right one for each question.
Anyone who declined
When your tool respects consent, your replays come only from visitors who agreed to analytics. That's fine for finding problems, since a broken button is broken for everyone.
The session recording glossary defines the rest of the vocabulary, from DOM snapshots to drop-offs.
Can a website record your screen or what you type?
Not your screen, unless you agree to share it: browsers ask your permission before a page can capture your screen, camera or microphone. What a page can do is record what you do on that page, such as your clicks, taps and scrolling, and play it back later. Unless the tool masks it, that includes what you type. That's session recording.
- What a page can record. What happens in its own tab, on its own site: the pages you open, where you click or tap, how far you scroll and what you type into its fields. Most recording tools rebuild that as a replay rather than filming it.
- What it can't. Your screen, other tabs and other apps, your camera or your microphone, unless you allow it when the browser asks. MDN's documentation says the browser prompts you to grant that permission for each of them.
- Whether typing is hidden. That depends on the tool and its settings. rrweb, the open-source recorder Session Recordings is built on, masks only password fields by default, and a site has to switch on masking for the rest.
- How to tell. Look for session recording in the site's privacy notice and for an analytics choice in its cookie banner. In Chrome, the Network panel logs the requests a page makes while the developer tools are open, so a replay tool's requests show up there.
- What Session Recordings records. Only the pages of the store or site that added it. Whatever you type into a form field is replaced with asterisks in your browser before anything is sent, and you aren't identified: the list names you Visitor plus a short code (on a Wix site, members signed in to it show by name; on a Shopify store, nobody is named). With a cookie banner, nothing is recorded until you allow analytics; without one, recording doesn't wait for a choice. A visit is recorded from the moment the page opens, whether or not you click, and text the page itself shows, such as your name in a greeting, is recorded as part of the page. On a Shopify store, the words you submit in its search are shown, and its checkout and your account pages are never recorded.
That's the visitor's side. For the site owner's, what a session replay can see covers masking, consent and what to tell visitors.
How do you record user sessions on a website?
Pick a tool, add it to your site, check what it masks and when it starts, then watch a test visit.
- Pick a tool. Session recording tools include Microsoft Clarity, Contentsquare (now home to Hotjar) and PostHog, and, for Shopify stores and Wix sites, Session Recordings. Free session recording apps for Shopify and session recording tools for Wix set out their free plans, limits and setup side by side.
- Add it to your site. Most tools give you a script to paste into your site's code. On Shopify, apps can add theirs as an app embed, which you switch on in the theme editor; on Wix, some come as apps that add their own script, and for the rest, where a tracking code goes on Wix has the steps.
- Check masking and consent. Make sure typing is masked, and that recording waits for your cookie banner if your site has one. What a session replay can see covers both.
- Say so in your privacy policy. The free session recording privacy notice template gives you wording to adapt.
- Make a test visit and watch it. Open your published site, accept analytics cookies if your banner asks, click around, then find your visit in the tool. What to check in your first 20 replays tells you what to look for next.
When should you use session recording?
When your site has just changed, when something looks wrong, or when the site is new to you.
- Right after a change. You launched a new menu or product layout and want to see real people use it.
- When a number looks strange. A report shows a drop at one step, and you need to see what happens there.
- When a customer reports a problem. A replay can show what they ran into, even if they couldn't describe it.
- When a site is new to you. Watching a dozen visits is a quick way to learn how strangers move through it.
When you start watching your own, a routine for watching recordings quickly keeps each sitting short.
Frequently asked questions
Is session recording the same as screen recording?
No. Screen recording makes a video of everything on a screen, and a browser asks your permission before any website can capture yours. Session recording saves only what happens on one website's pages, as events that a player rebuilds into a replay, so other tabs, apps, your camera and your microphone stay out of it.
Is it legal to record visitors on your website?
It can be, when visitors are told and, where the law requires it, asked first. In the UK, for example, the ICO's guidance lists logs or recordings of individual visitors among the things that need consent, unless they're kept for security (ICO, statistical purposes exception). The EU's consent rules and US wiretap lawsuits are covered in plain language in our guide to session replay privacy and GDPR; it's general information, not legal advice.
Can visitors tell when their visit is being recorded?
Not from the page itself. A recording runs quietly in the background, so nothing on screen changes while someone browses. Visitors learn about it from your cookie banner and your privacy policy, which is why both should mention recordings in plain words. With a tool that follows cookie consent, visitors who decline analytics aren't recorded at all. A visitor who wants to check can watch the Network panel of the browser's developer tools for requests to a replay service; what a session replay can see covers what to tell them.
How many session recordings should you watch?
Enough to see a pattern, which is often fewer than you expect. Start with one clear question and about ten visits that can answer it. If the same behavior shows up several times, you have a lead worth acting on. If every visit looks different, narrow the question or watch more, then check your analytics to see how often it happens.
Do you need to add code to start session recording?
Not with every tool. Some ask you to paste a script into your site, as Hotjar's custom-code setup on Wix does. Session Recordings needs no code. On Shopify, you switch on its Session recorder in your theme editor: the app's Turn on in theme editor button opens it, and you click Save. On Wix, recording is on as soon as you add the app, and it runs on your published site; if its Replays page says your site's recorder isn't set up yet, press Add it now and publish your site again.
Try it on your site
Session Recordings records real visits to Shopify stores and Wix sites and replays them as rebuilt pages, with what visitors type into form fields masked. See session replay for Shopify and Wix, from the Activity list to live view.
Sources
For the section on what a website can record, checked October 6, 2026.
- MDN: MediaDevices.getDisplayMedia()
- MDN: MediaDevices.getUserMedia()
- rrweb: recording options (maskAllInputs, maskInputOptions)
- Chrome DevTools: Inspect network activity
For the Shopify setup lines, checked October 29, 2026.
For how a recording is made, and the UK consent line, checked October 28, 2026.



