
You don't need another dashboard for WebRTC observability
You pull the webrtc-internals dump and scroll thousands of getStats() lines. rtcStats reads it for you, keeps its analysis engine portable, and lets your data stay yours.
Authors
Maker of rtcStats
Helping companies solve their WebRTC technical and roadmap challenges | 25+ years VoIP/WebRTC expert

You pull the webrtc-internals dump and scroll thousands of getStats() lines. rtcStats reads it for you, keeps its analysis engine portable, and lets your data stay yours.

Stop scrolling through thousands of getStats lines. Upload a webrtc-internals dump to rtcStats and AI tells you what went wrong on the call in under 30 seconds. Or query it from Claude Code and Cursor over MCP.

webrtc-internals is Chrome's built-in tool for a live session on your machine. rtcStats monitors production. Here's when each one is the right call.

Compute Pressure is the browser's privacy-preserving CPU load signal. Here's what it means, how to use it, and how rtcstats-js already collects it side-by-side with your other WebRTC metrics.

Stop asking users to capture webrtc-internals manually. Use rtcstats-js with IndexedDB to store WebRTC stats locally and get dumps only when you need them.

Meet Observations: a set of best practices that see WebRTC issues before you do, saving you time so you can focus on what matters most.

Discover the 'less is more' approach to WebRTC monitoring: collect everything but focus on what matters most for faster troubleshooting.

Learn how to build your own WebRTC monitoring solution with rtcstats. Control costs, own your data, and customize your metrics collection.

Yes, webrtc-internals can be improved upon. Discover its limitations and how rtcStats provides a better solution for WebRTC monitoring.

Discover why server-side monitoring isn't enough for WebRTC and how device-side statistics collection can transform your user experience.