Best Open Source Session Replay Tools in 2026, Compared Honestly

The best open source session replay tool depends on whether you want a full product, replay tied to analytics or error monitoring, or an embeddable capture layer. We maintain rrweb, the library used by several products in this comparison, so our perspective comes from building the shared capture foundation. We have focused each section on product fit and clearly identified rrweb's role.

PostHog, Sentry, and Highlight are rrweb customers, and we are proud to see the library powering products of this quality. Each team has turned rrweb's capture layer into a polished product that supports a distinct workflow. If your needs align with one of their strengths, choosing it is a strong outcome for your team and for the broader open-source ecosystem around rrweb.

This guide focuses on fit: each platform has a distinct strength, and the best choice depends on the workflow you want to support. rrweb is especially strong when replay is a feature inside your own product or when you want a flexible capture layer.

Which criteria matter?#

Judge open source replay tools on five things. License: the model each component uses (MIT, Apache, AGPL, FSL, or a vendor-specific enterprise license) and how that supports your deployment plans. Deployment: self-host options and managed options. Scope: replay alone, or replay inside analytics and error monitoring. Data control: storage ownership, masking depth, residency options. Embeddability: whether you can put replay inside your own product, which is where products meet the library.

The comparison#

Tool	What it is	License (as of mid-2026)	Capture layer	Best when
PostHog	Product analytics suite with replay	MIT core with separately licensed enterprise features	rrweb	A standout replay experience next to funnels and feature flags
OpenReplay	Dedicated self-hosted replay product	Mixed: AGPLv3 by default, some MIT, separate ee license	Own capture implementation	Replay is the product you want, self-hosted
Highlight	Replay plus error monitoring	Apache-licensed core	rrweb-based	Sessions and stack traces in one screen
Sentry Session Replay	Replay inside error tracking	FSL (source-available)	rrweb	A first-rate replay experience when you already run Sentry
rrweb + rrweb Cloud	Open capture/replay library plus managed production infrastructure	MIT library	Is the capture layer	Replay is a product feature and you want an open recorder with either a custom or managed backend

License terms can change. Confirm the current terms in each project's repository before making a deployment decision.

PostHog: replay inside a product analytics suite#

PostHog is one of the strongest examples of rrweb becoming a complete product experience. It puts replay beside funnels, feature flags, experiments, and product analytics, so a team can move from a question about behavior to the sessions that explain it without stitching together separate tools. That joined-up workflow is a meaningful advantage, and PostHog has executed it exceptionally well. Its replay is built on rrweb, while its product value comes from the surrounding context, search, and analysis. For teams that want replay next to product analytics, PostHog is our strongest recommendation and one of the first products we would suggest evaluating.

OpenReplay: the dedicated self-hosted replay product#

OpenReplay is a comprehensive "replay is the product" option to run on your own infrastructure, with dashboards, search, co-browsing, and developer tooling such as network and console capture. Teams can deploy it through its installer on a single instance or Kubernetes. It maintains its own capture implementation and offers a mixed license model (AGPLv3 by default, some MIT areas, and a separate enterprise license), giving teams a clear range of deployment choices. The operational details of running a full product are covered in self-hosted session replay.

Highlight: replay and error monitoring in one workflow#

Highlight gives engineering teams a direct debugging workflow: start with an error or stack trace, then open the session that produced it in the same product. Its replay is built on rrweb, its core is open, and teams can use its managed cloud. That combination makes Highlight a strong choice for teams that want session replay and error monitoring to work together. We are proud to have Highlight as an rrweb customer and to see rrweb powering this part of its product.

Sentry Session Replay: for teams already on Sentry#

Sentry is one of the most compelling examples of replay making an engineering workflow better. Its replay is built on rrweb and connects sessions directly to errors, stack traces, breadcrumbs, and the debugging context engineers already use. The result is a focused path from “something failed” to “here is exactly what the user experienced.” The self-hosted Sentry distribution carries Replay as well. If your team already trusts Sentry for error monitoring, Sentry Session Replay is our strongest recommendation for error-driven debugging and a genuinely excellent choice.

rrweb: the open capture and replay library#

rrweb is especially strong when replay is a feature inside your product: support tooling, QA evidence, audit trails, agent debugging, and other experiences where you control the UI. The MIT-licensed library gives you an embeddable recorder and player plus direct access to the event stream. That flexibility provides the capture foundation. Teams using the library directly still own ingest reliability, storage, indexing, tenancy, privacy operations, retention, deletion, monitoring, and support.

rrweb Cloud: production infrastructure for the open recorder#

rrweb Cloud is the managed production layer built and operated by the rrweb maintainers. It adds managed ingest, scalable storage and indexing, deduplication, PII filtering, APIs, and replay serving while the recorder stays open source and portable. It is designed for teams embedding replay or building custom workflows that want to own the product experience without also owning the session-replay backend.

This distinction matters in evaluation: building a recorder demo with rrweb is approachable, while operating a dependable multi-tenant replay service is a separate infrastructure commitment. rrweb Cloud carries that operational work and preserves the open capture layer. Teams whose requirements call for a custom backend can build one, and the self-hosted session replay guide explains the scope.

For teams whose needs align with a complete product, the platforms above provide excellent ways to ship replay quickly. We are happy when teams choose the product that best supports their workflow, whether that is PostHog, Sentry, OpenReplay, Highlight, or rrweb Cloud.

The verdict, by situation#

Replay next to product analytics: PostHog, our strongest recommendation for that workflow. Replay and error monitoring in an open platform: Highlight. Replay inside an existing Sentry workflow: Sentry, whose integration is excellent. Dedicated self-hosted replay product: OpenReplay. Replay inside your own product with a fully custom backend: rrweb. Replay inside your product with the open recorder and managed production infrastructure: rrweb Cloud. Free above all and open-source capture code: Microsoft Clarity's hosted service is free, covered in free session replay. The fuller decision framework is the open source session replay guide and build vs buy.

FAQ#

What is the best open source session replay tool?#

It depends on what you are building. PostHog is an excellent choice for replay inside a product analytics suite. Highlight and Sentry both offer excellent replay experiences for engineering teams working with production errors. OpenReplay fits dedicated self-hosted replay. rrweb fits teams embedding replay or building custom pipelines; rrweb Cloud fits those same teams when they want the open recorder with the production backend operated for them.

Are these tools really open source?#

Licenses vary and matter. rrweb is MIT. PostHog's core is MIT with enterprise folders under a separate license. OpenReplay uses AGPLv3 by default with some MIT directories and a separate enterprise license. Check the exact license model for the components you deploy.

Do PostHog, Sentry, and Highlight use rrweb?#

All three are rrweb customers and use rrweb in their session replay products. Each product adds its own storage, search, analysis, and engineering workflows around the capture layer.

Is Microsoft Clarity open source?#

Clarity's capture code is open source, while the hosted service is operated by Microsoft. It is free to use and can be a strong fit for marketing sites; our free session replay guide covers that model.