DRM tester.
What can this browser actually play?
Protected playback depends on three things a page can't see: which Content Decryption Modules the browser ships, which robustness level each one will grant, and whether the display meets the HDCP policy the studio asked for. This page asks the browser all three and prints the answers.
It runs navigator.requestMediaKeySystemAccess() against the key systems, robustness levels and codecs below. There's no stream and no licence request involved, so the result describes the browser and the device, not a particular title. Everything happens in your own browser.
DRM capability report
The test starts as soon as the page loads and takes a few seconds, because each key system is asked about every robustness level in turn.
Key systems
| Key system | Identifier | Available | Robustness levels granted | Offline licences |
|---|---|---|---|---|
| Testing... | ||||
Video codecs, per key system
A key system can be present and still refuse a codec, which is how HEVC and AV1 playback fails on an otherwise DRM-capable browser.
| Codec profile | Widevine | PlayReady | FairPlay | ClearKey |
|---|---|---|---|---|
| Testing... | ||||
HDCP policy
In plain English
Copy the result into a support ticket
Most DRM failures are reported as "it does not play", which isn't enough to work with. The block below is the report in text form, including the browser and the platform it reported. Paste it into a ticket and the next person knows exactly which capability is missing.
How to read the result
Browsers don't answer "yes" or "no" to DRM. They answer a narrower question: can you play this codec, at this robustness level, with this DRM system? That's why the tables above are a matrix, not a list of check marks.
| What you see | What it means |
|---|---|
Widevine with HW_SECURE_DECODE or HW_SECURE_ALL |
Widevine L1. The decoder and the keys live in a trusted execution environment, which is what studios require for HD and UHD. |
Widevine with only SW_SECURE_CRYPTO or SW_SECURE_DECODE |
Widevine L3. Decryption happens in software. Fine for SD and for development, refused by many studios for HD and above. |
PlayReady with HW_SECURE_ALL |
PlayReady hardware DRM, the normal outcome on Windows and Xbox. HD content is available where the licence policy allows it. |
| FairPlay present, no robustness levels | Normal. FairPlay doesn't expose robustness levels through EME the way Widevine does; on Apple platforms the security level is decided by the licence and the hardware, not by a string in the request. |
HDCP status usable |
The display and the whole output path meet that HDCP version. output-restricted means the browser understood the policy and the current display does not satisfy it, which is what a recorder or an old HDMI splitter produces. |
| Offline licences: yes | The CDM accepts persistentState: "required", so persistent licences for download-and-play offline are possible. It doesn't prove your licence server issues them. |
Limits of what a page can measure
- HDCP needs a real key session. The check above uses
MediaKeys.getStatusForPolicy(), which some browsers don't implement. Where it's missing, the page says so rather than guessing. - No licence is requested. A browser can downgrade or refuse playback later, when a real licence arrives with a policy such as HDCP 2.2 or a maximum resolution.
- FairPlay identifiers differ by Safari version. Safari reports
com.apple.fpsin current releases andcom.apple.fps.1_0in older ones, so the page tests all three and shows which one answered. - Encrypted Media Extensions need a secure context. Over plain HTTP the API is absent even in a browser that supports it, and the page reports "absent" because that is what the browser exposes.
- No streams, no files, no URLs. There is nothing to upload and nothing to store. This page only queries capability APIs.
If a key system is missing
Which system a viewer gets is decided by the browser and the platform, so the fix is usually in the packaging, not in the player:
- No Widevine in Safari or on iOS. Expected. Apple platforms use FairPlay, and Safari doesn't implement Widevine at all.
- No FairPlay in Chrome, Firefox or on Windows. Also expected. FairPlay is an Apple-only path, which is why most operators package the same title for Widevine, PlayReady and FairPlay and let the player choose.
- Widevine present but no hardware robustness. A software-only path on a desktop is normal. If a studio requires hardware DRM, the device, the operating system and sometimes the GPU driver decide the answer, not the browser version.
- No key system at all. The browser can't play protected content. Common causes are a non-secure context, a Linux build without the CDM, or a browser that ships without EME.
Serving all three systems from one package is the normal production setup. Multi-DRM playback describes what the Bradmax player does with this matrix at runtime, and the DRM playback demo plays Widevine, PlayReady and FairPlay streams in a full player.
Related tools
- Browser capabilities - MSE, EME and the full codec and audio matrix, without the DRM robustness detail.
- Online M3U8 player - play an unprotected HLS stream and see the real error when it fails.
- HLS playlist inspector - parse the manifest, including the
#EXT-X-KEYlines that mark a stream as encrypted. - Multi-DRM playback - how Widevine, PlayReady and FairPlay are configured in one player.
- What is an M3U8 file - the playlist format explained.