Chrome 160 Release Notes

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 standard. Removing it ensures better compatibility and security across different web browsers.

IT Admins should ensure that any internal or third-party web communication applications that rely on WebRTC are tested before Chrome 160 is deployed.

Chrome 151 began deprecating support for unspecified presentation and issuance protocols in the Digital Credentials API; final removal is scheduled for Chrome 160.

The Digital Credentials API was originally designed to be an opaque pipeline for arbitrary exchange protocols. In November 2025, the FedID WG resolved to change this so that the spec normatively referenced only a specific set of exchange protocols.

The removal of support for arbitrary, opaque pipelines ensures that only verified protocols are used, enabling a more robust privacy and security threat model for identity verification. This change aligns Chromium with updated industry specifications that normatively reference only a specific set of exchange protocols.