Replayowl vs Umami session replay
Umami is open source web analytics that now includes session replay and heatmaps. Replayowl only does session replay. Which one fits depends on whether replay is a side feature for you or the main thing.
Facts about other products on this page were last checked against their own websites on . Prices and limits change; follow the source links before you decide.
Umami is the better choice if
- You want web analytics, replay and heatmaps in one self-hosted tool.
- You prefer the MIT license.
- Sampled, short recordings are enough to understand how people use your pages.
Umami is a mature project with around 39,000 GitHub stars. Session replay arrived in v3.1.0 in April 2026, and click and scroll heatmaps in v3.2.0 in June 2026.
Replayowl is the better choice if
You use replays to understand individual visitors’ problems: a support ticket, a bug report, a failed checkout.
| Umami replay (from its docs) | Replayowl | |
|---|---|---|
| Which sessions are recorded | Sample rate, 15% by default | Every session the script runs on |
| Recording length | Stops at a maximum duration, 5 minutes by default | Whole session, across page loads |
| Retention | Replays stored for 30 days | Until you delete them |
| Masking | Two levels: inputs, or inputs and all text; plus a block selector | Inputs, emails and card numbers by default; per-element mask, block and unmask |
| Console errors | Not mentioned in the replay docs | Recorded with stack traces and marked on the timeline |
| Find sessions by your user ID | Distinct IDs exist in Umami tracking | Yes, with page, duration, device, error and rage-click filters |
| Heatmaps | Yes | No |
| Web analytics | Yes | No |
| License | MIT | AGPL-3.0 |
Source: Umami replay docs.
Can I use both?
Yes. Umami for traffic analytics and heatmaps, Replayowl for full-length replays with errors. They use separate scripts and separate storage.
See the replay quality for yourself in the live demo.