← Back to release summary

Deprecate and remove WebRTC peer connection method

Category
WebRTC
Type
Feature removal
Status
Proposed (Chrome Proposed)
Intent stage
None

WPT details: https://wpt.fyi/results/webrtc/historical.html%3Finterop-2026?label=master&label=experimental&aligned&view=interop&q=label%3Ainterop-2026-webrtc

Summary

Starting in Chrome 160, Chrome will remove support for the `RTCPeerConnection.createDTMFSender()` method on Windows, macOS, Linux, ChromeOS, and Android. This is a legacy, non-standard method that is obsolete and no longer conforms to the official _Real-time communication for the web_ ([WebRTC](https://webrtc.org/)) standard. Removing it ensures better compatibility and security across different web browsers. **Before Chrome 160** is deployed, admins should test any internal or third-party web communication applications that rely on WebRTC. For more details on rollout dates, see the [Chromium release schedule](https://chromiumdash.appspot.com/schedule).

Motivation

This is a legacy and obsolete method that does not exist in the WebRTC spec and the only major engine implementing it is Blink. Removing it is part of Interop 2026.

Standards & signals

Ecosystem

View on chromestatus.com