# Mediasoup doesn't support in chrome version 140

**URL:** <https://mediasoup.discourse.group/t/mediasoup-doesnt-support-in-chrome-version-140/6857>\
**Category:** mediasoup libraries\
**Created:** [September 8, 2025, 11:09am UTC](https://mediasoup.discourse.group/t/mediasoup-doesnt-support-in-chrome-version-140/6857 "2025-09-08T11:09:54Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![ibc](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/ibc/32/1540_2.png) [@ibc](https://mediasoup.discourse.group/u/ibc)\
**Post date:** [September 8, 2025, 11:40am UTC](https://mediasoup.discourse.group/t/mediasoup-doesnt-support-in-chrome-version-140/6857/2 "2025-09-08T11:40:06Z")

</div>

Did you search in the Announcements topic or did you check the latest PRs in mediasoup-client? I write things for something but if people don’t read them there is nothing I can do.

> [@URGENT: Upgrade to mediasoup-client 3.15.0 ASAP](https://mediasoup.discourse.group/t/urgent-upgrade-to-mediasoup-client-3-15-0-asap/6821):
>
> mediasoup-client 3.15.0 has been released and everyone should upgrade to it ASAP. In Chrome M140, the way codec payload types and RTP extension IDs are assigned in the local SDP will dramatically change and will break assumptions made by mediasoup-client internals. In current Chrome Canary (version 141) this is already true, so literally mediasoup-client doesn’t work on it. The new version 3.15.0 of mediasoup-client fixes this problem. Related issue: [Produce Video only stream fails. · Issue …](https://github.com/versatica/mediasoup-client/issues/330)

---

_[View the full topic](https://mediasoup.discourse.group/t/mediasoup-doesnt-support-in-chrome-version-140/6857)._