Based on user research, Bug Capture typically saves over 50% of the time on reporting issues and about 30% of the time on debugging.

The Web SDK (currently available on an Enterprise plan) supports all modern browsers. The extension works on all Chromium browsers including Chrome, Edge, Opera, etc. Regardless of the browser, the extension needs to be installed from the Chrome Web Store. Bug Capture extension is not available for Safari and Firefox. You should be able to view the recordings on all modern browsers (including Safari).

On smartphones, Bug Capture is only available for web apps that can be accessed via mobile browsers. Native apps are currently not supported.

Yes. Absolutely. For steps, see documentation.

Absolutely. To capture the technical logs within an emulated browser, configure the Web SDK (currently available on an Enterprise plan). The extension will only be able to record a video, but will not capture the logs from the emulated browser.

Of course. The best way to do that would be to integrate Bug Capture Web SDK (currently available on an Enterprise plan) on your page. Alternatively, you can even integrate it with Zendesk or Intercom.

The Web SDK Widged (currently available on Enterprise plan) and browser extension are complementary solutions. You can either use one or both, depending on your requirements.

The Web SDK and browser extension serve different needs:

• The web SDK widget is better suited for end customers to report bugs because it has a simpler interface and workflow.
• The browser extension is better suited for frequent QA and testing, as you can easily access all functionalities.

SDK support is currently provided only on Enterprise plans. For more details, contact BrowserStack Support.

To know more about SDK and its setup, see documentation.

Absolutely. You can turn this option on in the Extension by clicking the carat icon on the right of the “Record current tab” button.

Absolutely. You can turn this option on in the Extension by clicking the carat icon on the right of the “Record current tab” button.

There is no limit for the video length, so that you can comfortably record not just bugs, but also the execution of manual tests for later reference. However, longer recordings typically take longer to upload and might affect performance due to browser limtiations.

Yes. You can download in webm format (before or after the recording is uploaded) or in mp4 (after the recording is uploaded). Please, note that you would still need to share a Bug Capture URL of the recording if you want the person to be able to view the technical logs.

At the moment it’s only possible to trim a Replay. When you are recording however, you can pause and resume the recording in case you need to perform some actions in-between.

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.

At this moment this is not possible. If multiple screenshots are required, consider recording a video instead, because engineers might appreciate additional context.

This could happen due to the following reasons:

• You don’t have replays enabled on the page. For steps to enable Replays, see documentation.
• There were no technical logs generated by the browser before the screenshot was taken.

That is currently not possible. You can however use annotations to draw the attention to a particular part of the screenshot.

At the moment only the viewport get into the screenshot.

There are a number of integrations with various tools, i.e. Issue Management (Jira Cloud, GitHub, Azure DevOps, Linear, Trello, Zapier), Automated testing (Selenium, Cypress, Playwright, Puppeteer), Communication (Slack Email), Error monitoring (Rollbar, Sentry, Bugsnag), Customer Support (Zendesk, Intercom).

Yes, the integration supports most custom fields. Unfortunately, support for all custom fields is virtually impossible, but with our constant improvements to Jira Cloud integration, it’s very rare that users run into unsupported custom fields.

At the moment we only have Jira Cloud integration.

With the automated Jira Cloud integration, the Jira API sets the reporter name as the name of the person who configured the integration. As a workaround, your name will be included in the description of the given bug report, so that your colleagues can reach out to you for further questions. As an alternative, you can use manual Jira cloud integration, which will set the Reporter field correctly.

We have an integration with Zapier, so please consider connecting the tool you need via Zapier.

To resolve this issue, see documentation.

• Try uploading a shorter recording. Longer recordings typically take longer to upload, so check if the recordings of all sizes are affected.
• Check your internet connection or try another Wi-Fi network.
• Network logs sometimes are very large. Try limiting the maximum size of network logs or disabling them completely. See documentation.

You can report the bug to us. To report a bug, log in to your Bug Capture workspace. In your workspace, in the bottom right corner, click the (?) button to open the help menu. On the help menu, click Report a bug to submit a bug to us. You can also include a recording or a screenshot. Your input will allow us to debug a lot quicker. Thank you in advance!

Contact your admin for adding and removing email addresses through the Browserstack user management page. If you are an admin, you can use Bug Capture’s Members page to invite the new email address to your workspace and subsequently remove the user with the old email address.

It’s likely that you are a part of more than 1 workspace. You can jump to a correct workspace by using a workspace switcher in the top left corner of your Bug Capture dashboard.