WebRTC Encoded Transform (V2)

Category: WebRTC
Type: Chromium catches up
Status: In developer trial (Behind a flag) (Chrome 141)
Intent stage: None

Summary

This API allows processing of encoded media flowing through an RTCPeerConnection. Chromium shipped an early version of this API in 2020. Since then, the spec has changed and other browsers have shipped the updated version of the spec (Safari in 2022 and Firefox in 2023). This launch refers to the latest spec version and is part of Interop 2025. This launch does not cover the generateKeyFrame method, which is still under discussion https://github.com/w3c/webrtc-encoded-transform/issues/143 https://github.com/w3c/webrtc-encoded-transform/issues/271 https://github.com/w3c/webrtc-encoded-transform/pull/269

Motivation

Latest version of API to allow processing of encoded media in RTCPeerConnections. Explainer: https://github.com/w3c/webrtc-encoded-transform/blob/main/explainer.md

Standards & signals

Specification: https://github.com/w3c/webrtc-encoded-transform
Firefox: Shipped/Shipping
Safari: Shipped/Shipping
Web developers: Positive
Tracking bug: https://issues.chromium.org/issues/354881878

Samples: https://webrtc.github.io/samples/src/content/insertable-streams/endtoend-encryption

View on chromestatus.com