RTCIceCandidatePairStats: priority property

Deprecated: This feature is no longer recommended. Though some browsers might still support it, it may have already been removed from the relevant web standards, may be in the process of being dropped, or may only be kept for compatibility purposes. Avoid using it, and update existing code if possible; see the compatibility table at the bottom of this page to guide your decision. Be aware that this feature may cease to work at any time.

Non-standard: This feature is non-standard and is not on a standards track. Do not use it on production sites facing the Web: it will not work for every user. There may also be large incompatibilities between implementations and the behavior may change in the future.

The obsolete RTCIceCandidatePairStats property priority reports the priority of the candidate pair as an integer value. The higher the value, the more likely the WebRTC layer is to select the candidate pair when the time comes to establish (or re-establish) a connection between the two peers.


An integer value indicating the priority of this pair of candidates as compared to other pairs on the same peer connection. The higher this value, the better the WebRTC layer thinks this pair of candidates is compared to the others, and the more likely a pair is to be selected for use.

Note: This property was removed from the specification as its value cannot be guaranteed to be accurately represented in a JavaScript number. You can calculate its value using the algorithm described in RFC 5245, section 5.7.2 if you need this information and can accept the risk that the result may not be entirely accurate.


No specification found

No specification data found for api.RTCStatsReport.type_candidate-pair.priority.
Check for problems with this page or contribute a missing spec_url to mdn/browser-compat-data. Also make sure the specification is included in w3c/browser-specs.

Browser compatibility

BCD tables only load in the browser