We're looking for a person or people to help audit MDN to find places we could speed up. Is this you or someone you know? Check out the RFP: https://mzl.la/2IHcMiE


The read-only property RTCPeerConnection.pendingRemoteDescription returns an RTCSessionDescription object describing a pending configuration change for the remote end of the connection. This does not describe the connection as it currently stands, but as it may exist in the near future. Use RTCPeerConnection.currentRemoteDescription or RTCPeerConnection.remoteDescription to get the current session description for the remote endpoint. For details on the difference, see Pending and current descriptions in WebRTC connectivity.


sessionDescription = RTCPeerConnection.pendingRemoteDescription;

Return value

If a remote description change is in progress, this is an RTCSessionDescription describing the proposed configuration. Otherwise, this returns null.


This example looks at the pendingRemoteDescription to determine whether or not there's a description change being processed.

var pc = new RTCPeerConnection();
var sd = pc.pendingRemoteDescription;
if (sd) {
  // There's a description change underway!
else {
  // No description change pending


Specification Status Comment
WebRTC 1.0: Real-time Communication Between Browsers
The definition of 'RTCPeerConnection.pendingRemoteDescription' in that specification.
Candidate Recommendation Initial specification.

Browser compatibility

FeatureChromeEdgeFirefoxInternet ExplorerOperaSafari
Basic support56 Yes22 ?


37 — 43

FeatureAndroid webviewChrome for AndroidEdge mobileFirefox for AndroidOpera AndroidiOS SafariSamsung Internet
Basic support5656 Yes44


37 — 43

? ?

1. Promise based version.

The addition of pendingRemoteDescription and currentRemoteDescription to the WebRTC spec is relatively recent. In browsers which don't support them, only remoteDescription is available.

See also

Document Tags and Contributors

 Contributors to this page: fscholz, Sheppy, jpmedley
 Last updated by: fscholz,