On 13 April 2027, Google will discontinue its Widevine Cloud License Service (CLS). If you currently rely on this service for Widevine DRM delivery, the clock is now ticking for a transition in your architecture.
Important clarification: Only the Google-hosted CLS endpoint is being retired. Widevine DRM itself isn’t going anywhere and will be maintained as usual.
If you’re using our DRMtoday service, then you’re already set up for success and there’s nothing you need to do!
What’s the Widevine CLS?
Widevine’s CLS is a free Google-hosted option available to Widevine licensees to generate DRM licenses. This service endpoint allows content distributors to use Google’s infrastructure rather than fully operating their own Widevine licensing server or working with a third-party DRM vendor. For some, this has been a convenient entry point – but it comes with trade-offs: as a free offering, support and valuable features aren’t available.
Alternatively, Google also offers licensees a “Widevine License Server SDK” to execute 100% of the end-to-end DRM license generation/delivery on their own infrastructure – avoiding any need for communicating with the Widevine CLS. Many third-party cloud multi-DRM providers already use this SDK – which also allows them to offer improved service-level and benefits.
For example, these are benefit differences between using the Widevine CLS vs. a managed DRM provider like DRMtoday that has the Widevine License Server SDK in place:
| Using Widevine CLS | DRMtoday | |
|---|---|---|
| End-to-end SLA & 24/7 support available |  |  |
| Uptime guarantees | | Up to 99.999% |
| Configuration flexibility & policy management | Limited | Expanded for fine tuning |
| License metrics visibility | Limited | Widely available |
| Number of server regions | Limited | Expanded for high availability and low latency |
| DRM systems | Widevine only | Widevine, FairPlay Streaming, PlayReady |
What does this mean?
If your service uses the Widevine CLS, either directly or indirectly, then when Google turns it off you wouldn’t be able to process DRM licenses for the many devices relying on Widevine for content security. Your service will need to transition to an alternative Widevine license delivery model – and you’ll need time to revise your DRM delivery architecture, transfer security policies, and test across device ecosystems.
It’s best to prepare now to avoid service interruption or migrating under time pressure.
Who this affects (and what to do)
If you use the Widevine License Proxy SDK or Widevine’s CLS directly
Perhaps you’re managing Widevine DRM licensing in-house with your own service architecture and you use the Widevine License Proxy SDK or the Widevine CLS. You’ll need to either:
- Replace usage of the Proxy SDK or Widevine CLS by migrating to the Widevine License Server SDK. Access to the SDK may require obtaining updated Certified Widevine Implementation Partner (CWIP) training and certification.
or
- Move to a dedicated DRM licensing vendor that doesn’t rely on the Widevine CLS – we suggest trying DRMtoday! 🙂
If you use a DRM vendor that still relies on Widevine’s CLS
It’s common for streaming platforms, broadcasters, and OTT operators to use a third-party multi-DRM licensing service. Most of these dedicated solutions would have already moved away from using Widevine’s CLS some time ago in order to provide improved service and end-to-end customer support.
If your existing DRM vendor solution still uses the Widevine CLS, then you’ll need to ensure they upgrade their service soon to manage those licensing components, or you can switch to a DRM provider that’s already prepared.
Our best-in-class DRMtoday service was upgraded years ago to provide end-to-end licensing without relying on Google services.
If devices require a CLS fallback
There are some devices (for example: certain older TV models) that currently require a fallback to the Widevine CLS. Widevine has stated they’ll implement a solution before the sunset period that’ll allow these fallback requests to be handled.
Upgrade to DRMtoday
Future-proof your content protection strategy with our leading DRMtoday licensing service. We’ll work with you to ensure a smooth migration path without needing to re-encrypt content.
Importing your existing media library’s content encryption keys (CEK) is simple. Based on how you use the CLS, this would either look like:
- Case 1: You brought your own keys, or Google created the CEKs and you’ve stored them in your own infrastructure. In this case you already have the keys ready for ingestion.
- Case 2: Google created your CEKs but you don’t store them in your own infrastructure. You’ll just need to use Widevine’s
getcontentkeyAPI to fetch the keys before ingestion. ⚠️ Please note: Google is planning to disable this API in February 2027.
Recent updates
For decades, conditional access systems (CAS) have been the backbone of PayTV security. They’ve protected...
In streaming, errors are inevitable. What isn’t inevitable is the confusion that comes with them....
At Castlabs, hiring is so much more than just filling vacancies, it’s about finding future...