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


This feature is obsolete. Although it may still work in some browsers, its use is discouraged since it could be removed at any time. Try to avoid using it.

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 deprecated (and never part of the official specification) read-only RTCDataChannel property stream returns an ID number (between 0 and 65,535) which uniquely identifies the RTCDataChannel. This ID is set at the time the data channel is created, either by the user agent (if RTCDataChannel.negotiated is false) or by the site or app script (if negotiated is true).

This property has been replaced with the RTCDataChannel.id property. If you have code that uses stream, you will need to update, since browsers have begun to remove support for stream.


var stream = aDataChannel.stream;


An unsigned short value (that is, an integer between 0 and 65,535) which uniquely identifies the data channel.


var dataChannel = pc.createDataChannel("SampleChannel");

console.log("Data channel stream ID: " + dataChannel.stream);


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

Browser compatibility

FeatureChromeEdgeFirefoxInternet ExplorerOperaSafari
Basic support56 ? No No43 No
FeatureAndroid webviewChrome for AndroidEdge mobileFirefox for AndroidOpera AndroidiOS SafariSamsung Internet
Basic support5656 ? No43 ? ?

See also

Document Tags and Contributors

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