> [!NOTE]
> **Note:** Visit ChromeStatus.com for lists of [current deprecations](https://www.chromestatus.com/features#browsers.chrome.status%3A%22Deprecated%22) and [previous removals](https://www.chromestatus.com/features#browsers.chrome.status:%22Removed%22).

Chrome 97 beta was released on November 18, 2021 and is expected to become the
stable version in late December, 2021.

## Remove SDES key exchange for WebRTC

The SDES key exchange mechanism for WebRTC has been declared a MUST NOT in the
relevant IETF standards since 2013. The SDES specification has been declared
historic by the IETF. Its usage in Chrome has declined significantly over the
recent year. Consequently [it is removed](https://www.chromestatus.com/feature/5695324321480704) as of Chrome
97.

## Remove WebSQL in third-party contexts

[WebSQL in third-party contexts is now removed](https://www.chromestatus.com/feature/5684870116278272).
The Web SQL Database standard was first proposed in April 2009 and abandoned in
November 2010. Gecko never implemented this feature and WebKit deprecated it in
2019. The W3C encourages
[Web Storage](https://developer.mozilla.org/docs/Web/API/Web_Storage_API)
and
[Indexed Database](https://developer.mozilla.org/docs/Web/API/IndexedDB_API)
for those needing alternatives.

## Remove SDP Plan B

The Session Description Protocol (SDP) used to establish a session in WebRTC has
been implemented with two different dialects in Chromium: Unified Plan and Plan
B. Plan B is not cross-browser compatible and [is hereby removed](https://www.chromestatus.com/features/5823036655665152).

## Deprecation policy

To keep the platform healthy, we sometimes remove APIs from the Web Platform
which have run their course. There can be many reasons why we would remove an
API, such as:

- They are superseded by newer APIs.
- They are updated to reflect changes to specifications to bring alignment and consistency with other browsers.
- They are early experiments that never came to fruition in other browsers and thus can increase the burden of support for web developers.

Some of these changes will have an effect on a very small number of sites. To
mitigate issues ahead of time, we try to give developers advanced notice so they
can make the required changes to keep their sites running.

Chrome currently has a [process for deprecations and removals of
API's](http://www.chromium.org/blink#TOC-Launch-Process:-Deprecation),
essentially:

- Announce on the [blink-dev](https://groups.google.com/a/chromium.org/forum/#!forum/blink-dev) mailing list.
- Set warnings and give time scales in the Chrome DevTools Console when usage is detected on the page.
- Wait, monitor, and then remove the feature as usage drops.

You can find a list of all deprecated features on chromestatus.com using the
[deprecated filter](https://www.chromestatus.com/features#deprecated) and
removed features by applying the [removed
filter](https://www.chromestatus.com/features#removed). We will also try to
summarize some of the changes, reasoning, and migration paths in these posts.