How to anonymize a webrtc-internals or rtcstats dump file

Use the free WebRTC Dump Anonymizer tool to strip IP addresses and other private data from dump files before sharing them.

When you receive a webrtc-internals or rtcstats dump file from a user, it often contains information you would rather not share publicly - IP addresses, host names, and other network details. rtcstats-server has a built-in anonymizer to keep your data safe. At times, you may need to take a file directly from a browser and present it publicly somewhere - for example when submitting a Chrome bug report. The WebRTC Dump Anonymizer is a free, browser-based tool that strips this data in a single click, so you can safely attach the file to a bug report, forum post, or support ticket.

What the tool does

The WebRTC Dump Anonymizer is a one-page web app hosted at:

https://rtcstats.github.io/rtcstats/dump-importer/anonymize

You drop a dump file onto the page, and it returns a sanitized copy for download. Everything happens locally in your browser - the file is never uploaded to a server.

When to use it

Use the anonymizer whenever a dump file is going to leave your organization or be shared in a place you don't fully control:

Filing a Chrome or browser bug - attach a sanitized dump instead of raw output from chrome://webrtc-internals
Asking for help in a public forum or Discord - strip IPs before posting on discuss-webrtc, Stack Overflow, or similar
Sharing a dump with a vendor or partner - keep your internal network topology private
Uploading a sample dump to a blog post, tutorial, or conference talk - anonymize before publishing

If the dump stays inside your own infrastructure and gets processed by rtcstats-server, you don't need this tool - see How to configure rtcstats-server for privacy for the server-side alternative.

How to use it

Open https://rtcstats.github.io/rtcstats/dump-importer/anonymize in any modern browser
Drag a dump file onto the drop zone, or click Choose file to pick one from your file system
The anonymized file downloads automatically once processing finishes
Open the downloaded file to verify the result, then share it wherever you need to

No account, upload, or install is required.

What gets anonymized

The tool rewrites three categories of data:

ICE candidates - host and server-reflexive candidates are anonymized. TURN server and relay addresses are left intact so the call flow remains understandable
Candidate lines inside SDP - the a=candidate: lines carried in setLocalDescription / setRemoteDescription events are rewritten to match
IP-related fields in statistics - IP addresses that appear inside getStats() records are anonymized as well

How IP addresses are rewritten

IPv4 - the last octet is replaced with x (for example 192.168.1.42 becomes 192.168.1.x)
IPv6 - the last six segments are replaced, preserving only the network prefix

This keeps the file useful for debugging - you can still see that two candidates were on the same subnet, or that traffic went through a specific TURN server - without exposing a specific user or device.

What does not get anonymized

The anonymizer is focused on network-layer identifiers. It does not touch:

userId, sessionId, or conferenceId values you passed into rtcstats-js
URLs captured in trace metadata
Device names from enumerateDevices()
Custom application metadata you added to the dump

If any of those fields may contain PII, sanitize them at collection time rather than after the fact. See How to configure rtcstats-server for privacy and the guidance on how to use sessionId, conferenceId and userId.