Report a problem or suggest an improvement
WebRTCTest welcomes focused reports about incorrect results, browser compatibility, accessibility, unclear explanations and ideas for useful WebRTC diagnostics. The project currently handles public support and product feedback through its GitHub issue tracker. You can open a WebRTCTest issue to start a report.
Do not include passwords, TURN credentials, complete SDP, private or public IP addresses, device labels, personal information or anything else that should not be published.
What to include in a bug report
A good report identifies the page, the action you took, the result you expected and what happened instead. Include the browser name and version, operating system, whether the page was opened over HTTPS, and the exact error text if it contains no sensitive information. Screenshots can help, but review them carefully for camera previews, tab names, network addresses or device details before uploading.
For camera, microphone or screen-share problems, say whether permission was allowed, blocked or never requested. For ICE, STUN or TURN problems, describe the candidate type or failure category without posting addresses or credentials. The ICE test and related pages are diagnostics, so the same environment may behave differently inside a specific conferencing service.
Security and privacy reports
If a report describes a security weakness or requires sharing non-public information, do not publish the details in a public issue. Open a minimal issue that asks the maintainers to establish a private coordination channel, without including exploit steps, secrets or affected user data. Privacy questions should first be checked against the Privacy Policy, which explains local media processing, network endpoints and analytics status.
Scope of support
WebRTCTest can help explain what its own tests measure and correct defects in the site. It cannot access your device remotely, change browser or operating-system permissions, recover third-party accounts, configure a private TURN service, or guarantee that another calling platform will work. For a third-party product problem, share the WebRTCTest result with that product's support team only after removing sensitive values.
Before opening a request, the About page explains the project's measurement limits and the Changelog lists recent updates. Clear, privacy-safe reports are the fastest way to help improve the site for everyone.