Replays - FAQs

Replay works like a car dash cam - it records the data continuously and erases older data on the fly. This way you can report even the bugs that are very hard to catch. With Replay enabled, Bug Capture records the DOM / HTML elements on the page and then creates a reconstruction of your actions.

No. Replays have minimal effect on CPU and memory as they are not videos, so they don’t require compression on the fly.

Replays are not technically videos, so they are not always pixel-perfect, and certain things might look off. The most common limitations are:

• Replay don’t capture the contents of an iFrame
• Replays don’t support all fonts

For more information, see documentation.

Replays contain no more than 2 minutes of your recent activity. This is done partly for performance reasons and partly because searching for a bug in a long recording is difficult, which we found out in user research.

No, by default Replays are disabled on all pages. You can choose which pages to enable Replays on. We recommend enabling them on the domains you test the most, e.g. your production and staging environments. Even when the Replays are enabled on the page, no data leaves your computer before you explicitly decide to upload the recording.