Your First Session
You just signed up. Here is how to get your first WebRTC session analyzed in under five minutes - no integration required.
You just signed up. Time to understand what superpowers rtcStats gives you. Start by uploading and analyzing your first webrtc-internals file.
Step 1: Get a dump file
The fastest path is a webrtc-internals export straight from Chrome.
- Open
chrome://webrtc-internals/inside Chrome - In another browser tab, start a WebRTC session in your application
- Reproduce the issue - or let a call run for at least a minute or two
- Go back to the webrtc-internals tab. Click on "Create a WebRTC-Internals dump"
- Click Download the "webrtc-internals dump" or Download the "rtcstats dump" (we support both and prefer rtcstats dump)
Already have an rtcstats format dump from your own collection server? That works too - upload it the same way in Step 2 below.
Step 2: Upload the file
- Sign into your account at rtcstats.com.
- Click Import Session in the top navigation.
- Drop your file or select it from disk.
rtcStats processes the session in under 5 seconds.
Step 3: Read the results
Once processing is done, you land on the session dashboard. Three things to look at first:
- Observations - specific moments the engine flagged: packet loss spikes, DTLS failures, ICE candidate pair switches, codec changes. Each Observation names the event, the timestamp, and why it matters
- Experience Score - a single number (0-100) representing how the call felt from the user's side. Gives you a quick severity read before you dig into individual metrics
- AI Summary - a plain-English paragraph that ties the Observations together and names the most likely root cause
Start with the AI Summary to orient yourself, then drill into the Observations for the specific moments.
Ready to stop doing this manually?
Uploading files by hand works for debugging one-off complaints. When you want sessions flowing in automatically - without asking users to export from their browser - you need two more pieces: rtcstats-js running in your client and rtcstats-server inside your infra. The Integration Guide walks you through both, four steps, under an hour.
Was this page helpful?