ICE Candidate Parser
Parse an ICE candidate online and decode foundation, protocol, priority, address, port, candidate type, related address, related port and TCP type locally.
Paste ICE candidate
Candidate parsed| Foundation | 842163049 |
|---|---|
| Component | 1 (RTP / muxed media) |
| Priority | 1677734911 |
| Related address | 192.168.1.10 |
| Related port | 54321 |
| TCP type | — |
| Extensions | generation=0 |
Decode a WebRTC ICE candidate
This ICE candidate parser turns a raw candidate line into readable WebRTC networking fields. Paste a candidate copied from SDP, browser logs or an ICE diagnostic and the parser separates foundation, component, transport protocol, priority, address, port and candidate type. It also extracts related address and port information, TCP type and additional extension pairs when they are present.
Understanding candidate types
A host candidate represents an interface available to the browser. A srflx candidate is a server-reflexive address typically discovered through STUN. A relay candidate comes from TURN, while prflx refers to a peer-reflexive candidate learned during connectivity checks. Candidate type helps explain how WebRTC may attempt to establish a path, but it does not guarantee that the candidate will become the selected pair.
Use the parser with live ICE diagnostics
If you need to generate candidates instead of decoding an existing line, use the WebRTC ICE test. Developers can also verify a custom STUN server, test TURN relay allocation, or inspect address exposure with the WebRTC leak test. Parsing occurs locally in the browser and pasted candidate text is not intentionally transmitted by this tool.
ICE candidate parser FAQ
What ICE candidate formats does this parser accept?
It accepts both candidate:... and a=candidate:... forms and decodes the standard fields commonly exposed in WebRTC SDP and RTCIceCandidate strings.
What do host, srflx, prflx and relay mean?
Host candidates come from local interfaces, srflx candidates are discovered through STUN, prflx candidates are peer-reflexive, and relay candidates are allocated through TURN.
Does an ICE candidate address automatically mean a privacy leak?
No. Candidate interpretation depends on browser masking, mDNS, network topology, VPN configuration and which candidate type is being examined.