The   Web Real-Time Communications Working Group   has published   WebRTC: Real-Time Communication in Browsers   as an updated W3C Recommendation. This document defines a set of ECMAScript APIs in WebIDL to allow media and generic application data to be sent to and received from another browser or device implementing the appropriate set of real-time protocols. This specification is being developed in conjunction with a protocol specification developed by the IETF RTCWEB group and an API specification to get access to local media devices.

  The   Web Real-Time Communications Working Group   has proposed amendments, including both corrections and additions, to the W3C Recommendation of   WebRTC: Real-Time Communication in Browsers . This document defines a set of ECMAScript APIs in WebIDL to allow media and generic application data to be sent to and received from another browser or device implementing the appropriate set of real-time protocols. This specification is being developed in conjunction with a protocol specification developed by the IETF RTCWEB group and an API specification to get access to local media devices. Proposed corrections and additions since the  January 2021 Recommendation  are listed in an  appendix to the document . Comments, including implementation experience, are welcome via  GitHub  through  8 December 2024 .

The  Web Real-Time Communications Working Group  has published a First Public Working Draft of  Capture Handle – Bootstrapping Collaboration when Screensharing . This document proposes a mechanism by which an application  APP  can opt-in to exposing certain information with another application  CAPTR , if  CAPTR  is screen-capturing the tab in which  APP  is running. It describes a mechanism for  tab capture  only.  

  The   Web Real-Time Communications Working Group   published today   Media Capture Depth Stream Extensions   as a   Discontinued Draft , due to lack of implementation momentum. The specification expected to extend the   Media Capture and Streams specification   to allow a depth stream to be requested from the web platform using APIs familiar to web authors. Publication as a Discontinued Draft implies that this document is no longer intended to advance or to be maintained. It is inappropriate to cite this document as other than abandoned work. Introduction: Mastering Digital Growth in 2025—From SEO to Social Media and AI In 2025, digital success isn’t just about having an online presence—it’s about strategically connecting the dots between SEO, web design, content creation, and social media. For small businesses and marketers alike, staying ahead means embracing the latest tools and trends that shape how we rank, engage, and grow online. Whether ...

21 September 2021 The Web Real-Time Communications Working Group has published a First Public Working Draft of WebRTC Encoded Transform. The goal of this work is to define an API for processing encoded media in WebRTC, for example for voice processing, background removal, dynamic control of codec parameters, etc. This document specifies an API surface for manipulating the bits on MediaStreamTracks being sent via an RTCPeerConnection.api

14 January 2020 The  Web Real-Time Communications Working Group  invites implementation of its updated Candidate Recommendation of  Identifiers for WebRTC’s Statistics API . This document defines a set of WebIDL objects that allow access to the statistical information about a RTCPeerConnection. These objects are returned from the getStats API that is specified in [ WEBRTC ].

2 July 2019 The  Web Real-Time Communication Working Group  has published an updated Candidate Recommendation of  Media Capture and Streams . This document defines a set of JavaScript APIs that allow local media, including audio and video, to be requested from a platform.

21 June 2018 The  Web Real-Time Communications Working Group  invites implementations of an updated Candidate Recommendation of  WebRTC 1.0: Real-time Communication Between Browsers . The WebRTC 1.0 specification defines JavaScript APIs to enable real-time audio, video and data exchange on the Web. Since the previous publication as Candidate Recommendation, the specification was updated with a number of bug fixes and clarifications in its algorithms. The following new APIs were added as part of these improvements:  RTCRtpSender.setStreams() ,  RTCRtpTransceiver.currentDirection ,  RTCSctpTransport.maxChannels ,  RTCPeerConnection.onstatsended , and the  RTCStatsEvent interface.

19 February 2015 The Web Real-Time Communications Working Group and Device APIs Working Group have published a Working Draft of Media Capture from DOM Elements . This document defines how a stream of media can be captured from a DOM element, such as a video, audio, or canvas element, in the form of a MediaStream. Learn more about the Ubiquitous Web Applications Activity .

10 February 2015 The Web Real-Time Communications Working Group has published a Working Draft of WebRTC 1.0: Real-time Communication Between Browsers . This document defines a set of ECMAScript APIs in WebIDL to allow media to be sent to and received from another browser or device implementing the appropriate set of real-time protocols. This specification is being developed in conjunction with a protocol specification developed by the IETF RTCWEB group and an API specification to get access to local media devices developed by the Media Capture Task Force. Learn more about the Ubiquitous Web Applications Activity .

10 February 2015 The Web Real-Time Communications Working Group and Device APIs Working Group have published two First Public Working Drafts today: Audio Output Devices API . This document defines a set of JavaScript APIs that let a Web application manage how audio is rendered on the user audio output devices. Screen Capture . This document defines how a user’s display, or parts thereof, can be used as the source of a media stream using getOutputMedia, an extension to the Media Capture API. Learn more about the Ubiquitous Web Applications Activity .

27 January 2015 The Device APIs Working Group and Web Real-Time Communication Working Group have published two Working Drafts today. MediaStream Recording , which defines a recording API for use with MediaStreams as defined in Media Capture and Streams. Mediastream Image Capture , which specifies the takePhoto() and grabFrame() methods, and corresponding camera settings for use with MediaStreams as defined in Media Capture and Streams. Learn more about the Ubiquitous Web Applications Activity .

03 September 2013 The Web Real-Time Communication Working Group and the Device APIs Working Group have published an updated Working Draft of Media Capture and Streams . This document defines a set of JavaScript APIs that allow local media, including audio and video, to be requested from a platform. Learn more about the Ubiquitous Web Applications Activity .

28 June 2012 The Web Real-Time Communication and Device APIs Working Groups published a Public Working Draft of Media Capture and Streams . This document defines a set of JavaScript APIs that allow local media, including audio and video, to be requested from a platform. Lean more about Ubiquitous Web Applications Activity .

The Web Real-Time Communications Working Group has published he First Public Working Draft of WebRTC 1.0: Real-time Communication Between Browsers . This document defines a set of APIs that enable video conferencing from within an Open Web Platform application. These APIs allow local media, including audio and video, to be requested from a platform, media to be sent over the network to another browser or device implementing the appropriate set of real-time protocols, and media received from another browser or device to be processed and displayed locally. This specification is being developed in conjunction with a protocol specification developed by the IETF RTCWEB group. Learn more about the Ubiquitous Web Applications Activity .

W3C today launched a new Web Real-Time Communications Working Group to define client-side APIs to enable Real-Time Communications in Web browsers. These APIs should enable building applications that can be run inside a browser, requiring no extra downloads or plugins, that allow communication between parties using audio, video and supplementary real-time communication, without having to use intervening servers. Read the full charter and learn more about W3C's Ubiquitous Web Applications Activity .