webrtc/samples

WebRTC Web demos and samples

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 2 minutes ago
Added to GitGenius on September 4th, 2026
Created on September 20th, 2013
Open Issues & Pull Requests: 44 (+0)
GitHub issues: Enabled
Number of forks: 5,672
Total Stargazers: 14,641 (+0)
Total Subscribers: 611 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 14.8 hours
Mean response time: 85.7 days
90th percentile: 177.5 days
Tracked items: 28

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 7% of issues opened in the past year have been closed. Three people close 88% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 4
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 678 days
Stale 30+ days: 4
Stale 90+ days: 4

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • ApiDeprecation (1)
  • bug (1)
  • bug-in-firefox (1)
  • interop (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

WebRTC samples is a collection of JavaScript code samples demonstrating WebRTC capabilities.

The repository addresses the need for practical, working examples of WebRTC functionality. It provides runnable demonstrations of WebRTC APIs and patterns that developers can study, test, and adapt for their own applications. Each sample is designed to illustrate specific WebRTC features and use cases in isolation, making it easier to understand how particular APIs work in practice.

Developers should use this repository as a learning resource and reference when building WebRTC applications. It suits anyone new to WebRTC who wants to see concrete implementations before writing their own code, as well as experienced developers looking for patterns or solutions to specific problems. The samples are tested and maintained to work across browsers, so they serve as a reliable baseline for understanding what WebRTC implementations should achieve. The repository explicitly directs general WebRTC questions and API bugs to appropriate channels rather than treating this as a support forum, keeping the issue tracker focused on sample-specific problems.

The project maintains an active contribution process with clear guidelines for submitting bugfixes and new samples. Issues are actively tracked and addressed when samples encounter problems or break due to browser changes.