CDN assets

rrweb browser assets are served from https://cdn.rrweb.com.

Use the CDN for browser-loaded scripts and styles.

CDN asset URL shape

CDN asset URLs follow the shape https://cdn.rrweb.com/<package>/<version-or-channel>/<file>, for example loading the Browser Client, the rrweb-player script, or the rrweb-player stylesheet.

https://cdn.rrweb.com/<package>/<version-or-channel>/<file>

Examples:

<script type="module">
  import { start } from 'https://cdn.rrweb.com/browser-client/next/browser-client.js';

  start({
    publicApiKey: 'your-public-api-key-here',
  });
</script>
<script
  type="module"
  src="https://cdn.rrweb.com/rrweb-player/next/rrweb-player.js"
></script>
<link
  rel="stylesheet"
  href="https://cdn.rrweb.com/rrweb-player/next/style.css"
/>

Versions and channels

Exact version URLs are immutable once published. current and next are channel aliases that redirect to an exact version recorded in the catalog. The catalog tooling sets current to the latest stable release, and falls back to the latest alpha while no stable release exists yet. It sets next to the latest prerelease whose version string contains next. The catalog is reviewed in pull requests and can also carry an emergency entry that pins a channel to a specific build, for example to hold a version or remap the bytes a version serves.

Once https://cdn.rrweb.com/rrweb-player/2.0.0-alpha.20/rrweb-player.js is published, republishing different bytes to that object is rejected by the publish tooling.

Browse the catalog

The public catalog at https://cdn.rrweb.com/catalog.json lists available versions, packages, aliases, and canonical files for each package.

https://cdn.rrweb.com/catalog.json

The CDN can also serve other published files for a package and version, which keeps older releases working when file names or layouts changed over time.

Publishing

Generated assets are not committed to Git; published exact version URLs are immutable, while current and next move forward through redirects.