Upcoming Breaking Changes in Twilio Video JavaScript SDK & Google Chrome

Twilio Video JavaScript versions prior to versions 1.20.0 and 2.0.0-beta15 rely on the Plan B SDP (Session Description Protocol) API. Google will be removing this SDP format from Chrome in Q1 of 2020. Due to this change, older versions of the Twilio Video JS SDK will be incompatible with future versions of Chrome. We recommend upgrading to the latest 1.x and 2.x versions of Twilio Video JS SDK. For more information refer to the Detailed Explanation section below.

Impact Timeline

Google communicated that the removal of Plan B SDP support is targeted for Q1 of 2020. Google has not indicated the exact version of Chrome or a more precise date. We recommend that you upgrade to the latest Video JS SDK release as soon as possible.

Is my application affected?

Your application is affected if you are using versions prior to 1.20.0 and 2.0.0-beta15

How do I upgrade my application?

Upgrade your application to one of the JavaScript SDKs listed below


NPM command



npm install twilio-video@1.20.1



npm install twilio-video@2.1.0



If you are upgrading twilio-video.js from 1.x to 2.x, you can refer to the migration guide.

In general, we recommend that all customers currently using our CDN to switch to a build process using the official twilio-video NPM package. Using NPM provides developers with more precise versioning rules. Additionally, and adding dependencies as a build step provides more control over what makes it into your production application. That said, you don't need to switch to NPM to address this upcoming compatibility issue with Chrome.

Detailed Explanation

In December 2018, Google began the phased migration of Chrome from using the Plan B SDP (Session Description Protocol) format to the Unified Plan SDP format. As they have now entered the final phase, Google will completely remove Plan B support from Chrome. Google has indicated this will be completed in Q1 of 2020.

With this phase out, Video JS SDK versions prior to versions 1.20.0 and 2.0.0-beta15 will exhibit incompatibilities with the new Unified Plan format that cause inability to play tracks from remote participants.

Additional Resources

Have more questions? Submit a request
Powered by Zendesk