What browsers and platforms are supported?

rtcStats works with any browser or platform that implements the standard WebRTC getStats() API.

Browser support for rtcstats.js (SDK)

rtcstats.js works by wrapping the standard RTCPeerConnection API. It supports all modern browsers, including Chrome, Edge, Firefox, Safari and any Chromium-based browser.

Uploading webrtc-internals dump files

For manual uploads to rtcstats.com, the primary supported format is the rtcstats file as well as Chrome's webrtc-internals dump. If you use Chrome, then both formats are available for manual download via chrome://webrtc-internals - our suggestion is to download and use the rtcstats file format (it is richer and slightly more comprehensive than webrtc-internals).

We do not support Firefox about:webrtc or Safari equivalents. In these browsers, the best approach is to use rtcstats-js - you will be needing to integrate with it if you want a rock solid WebRTC observability platform anyway.

Platform considerations

Below are some platform specific considerations when dealing with rtcstats integration.

Desktop & mobile browsers

On desktop and mobile browsers, the standard practice is to integrate rtcstats-js with your web application directly. There should be no OS specific issue or browser specific issue with the integration - this part should be straightforward.

Electron and embedded browsers

Electron and other embedded browsers use the same approach as you would with a regular web browser - make rtcstats-js a part of your application and the rest should be straightforward.

In such environments, it is theoretically possible to collect more metrics - either ones associated with your application or ones that access machine data that web browsers don't expose via Javascript. If you are looking to collect and visualize such information, please contact us.

Native mobile apps (iOS/Android)

For native mobile apps, see Can I use rtcStats for native mobile apps?

See also

• Can I use rtcStats for native mobile apps?