Widevine Solutions & Features
Cloud License Service vs SDK, supported features at a glance.
What "Widevine" actually means as a product
Three things wear the Widevine name and it pays to keep them straight:
For CWIP candidates the relevant product is the License Server SDK. The labs configure and exercise that SDK; the in-person training drills its API.
Deployment shapes you'll meet
| Pattern | Where the SDK runs | Who runs it |
|---|---|---|
| Self-hosted | Inside the integrator's own infrastructure | Streaming service ops team |
| Multi-DRM SaaS | Inside a third-party provider that has CWIP partners on staff | The SaaS vendor |
| Cloud License Service (legacy) | Google-hosted | Google — sunsetting 2027-04-13 |
The 2027-04-13 sunset for the Widevine Cloud License Service is the kind of date that's easy to test. Memorise it.
What Widevine ships out of the box
The features below are the public-facing capability set. Each gets its own deeper module later:
- Streaming licences (in-memory, single-session).
- Persistent licences (offline / download-to-go).
- Key rotation (live streams rotate content keys on a schedule).
- License renewal (the CDM emits a renewal message; the app refreshes the licence mid-playback).
- Per-track keys (different KIDs per video resolution or per audio track, used to enforce HD-vs-SD policies).
- Output protection enforcement (HDCP version, analogue blocking).
- Provisioning isolation (the per-origin / per-application device certificates introduced with Provisioning 3.0).
Devices and reach
A correct mental model of "which devices does Widevine cover?" matters because content owners ask it directly:
- Chrome (desktop, Android, ChromeOS — but not Chrome on iOS, where the system stack is FairPlay-only).
- Android every phone, tablet, TV box, ChromeCast Ultra, certified Android TVs.
- Smart TVs and STBs that ship Widevine via the SoC vendor's integration (LG WebOS, Samsung Tizen, Sony Bravia, many cable / IPTV STBs).
- Edge on Windows also ships Widevine (alongside PlayReady).
- Firefox uses the Widevine CDM via Adobe / Google distribution (varies by OS).
iOS and tvOS native players use FairPlay. If your target is "every screen", you ship CENC content and run a licence server that can issue all three (Widevine, PlayReady, FairPlay).
"Widevine works on iOS Safari" is a trap question. Browsers on iOS use the WebKit-bundled stack. For DRM that means FairPlay-only. A single integrator codebase shipping to iOS still needs FairPlay support.
What CWIP doesn't cover
Some adjacent topics show up in real integrations but are out of scope for the CWIP exam itself:
- Forensic watermarking (NAGRA, Verimatrix, etc.) — separate vendor stack.
- Per-user session DRM tokens for CDN auth — implementation detail of the integrator.
- Subscriber/billing systems — entirely the integrator's problem.
The exam stays focused on the Widevine system: packaging, server SDK, CDM, devices, EME / MediaDrm.