February 27, 2026

DRM explained: How digital rights management protects your videos

Masroor Ahmed
Masroor Ahmed
AI/ML Engineer

When a studio, a sports league or a course creator asks whether your app supports DRM, the usual answer is to encrypt the video and point the player at a license server. That approach is well documented and it works: the player asks for a key, the license server checks the request, and the device decrypts the stream without ever handing a usable file to the viewer.

Where it falls short is coverage. Safari and iPhones only accept FairPlay, Chrome and Android expect Widevine, and Windows and Xbox expect PlayReady, so protecting your library with one DRM system leaves part of your audience staring at a black screen.

Even with all three in place, devices differ. A phone whose DRM runs only in software is usually held to standard definition by the content owner, and a desktop browser using software DRM can still be screen-recorded. Below, we walk through how DRM works step by step, which DRM each device needs, how one set of files serves all three, and which piracy methods DRM actually blocks.

What is DRM? How DRM works in OTT, step by step

DRM (digital rights management) is the encryption and licensing technology that keeps your video encrypted all the way to the screen. The file sitting on the CDN is useless by itself. The key that decrypts it lives on a license server, and it only reaches a device inside a license that the device's Content Decryption Module (CDM) can open.

That is the whole DRM process in seven steps. Two checks inside it answer different questions: the playback token in step 2 decides whether this viewer may fetch this video at all, and the license request in step 5 decides whether this device may decrypt it. The CDM then enforces whatever the license allows, such as a resolution cap on a device without hardware protection.

On FastPix, the license request goes to an endpoint like api.fastpix.com/v1/on-demand/drm/license/widevine/{playbackId} with a DRM token your server signed. A copied stream URL without a fresh token never gets a key (DRM set-up docs).

Widevine vs FairPlay vs PlayReady

Each DRM system only works where its owner's CDM is installed, so the device chooses for you.

DRMOwnerWhere it playsSecurity levelsStreaming formats
WidevineGoogleChrome, Firefox, Edge, Android, Android TV, most smart TVs and streaming sticksL1 (hardware), L2 (rare), L3 (software only)DASH, and HLS with CMAF
FairPlayAppleSafari on macOS, iPhone, iPad, Apple TVNo numbered levels; Apple signals tiers in HLS with ALLOWED-CPC. Hardware-backed on current iPhone, iPad, Apple TV and Apple-silicon MacsHLS, including CMAF segments
PlayReadyMicrosoftEdge and apps on Windows, Xbox, many smart TVsSL3000 (hardware), SL2000 (software or hardware), SL150 (testing only)DASH, Smooth Streaming (Microsoft's older format), HLS with CMAF

The security level matters as much as the brand. Widevine L1 and PlayReady SL3000 decrypt inside a Trusted Execution Environment, a protected area of the processor that the operating system can't read (PlayReady security levels). Widevine L3 and PlayReady SL2000 can run entirely in software, which is easier to attack, so content owners cap them. That cap is why the same streaming subscription can play in HD on one Android phone and in 480p on another: the cheaper phone only reports Widevine L3. FairPlay has no numbered levels; on Apple devices it is hardware-backed.

Why OTT apps need multi-DRM

Multi-DRM means one encrypted library that all three systems can unlock, with the player picking the right one on each device. It exists because no single DRM covers the devices an OTT provider's audience uses. A Widevine-only service fails on every iPhone, and a FairPlay-only service fails on Android.

Licensing makes it hard to avoid. Studios, sports leagues and broadcasters write DRM into distribution agreements, often down to which security level is allowed for HD and 4K. "We encrypt with AES" does not get through that kind of content review. A multi-DRM solution is how one app satisfies that agreement on every platform it ships to, with one key management setup instead of a separate pipeline per platform.

Multi-DRM encryption and packaging with CMAF

The older way to run multi-DRM was to package every title twice: once for FairPlay on HLS, once for Widevine and PlayReady on DASH. That doubled storage and split the CDN cache across two copies of every title. CMAF (Common Media Application Format) removes the duplicate with one segment format, MP4 cut into small pieces, that both HLS and DASH manifests can point at.

Encryption has a trap. Common Encryption (CENC, ISO/IEC 23001-7) lets several DRM systems share one encrypted file, but it defines more than one scheme, and Apple only plays one of them:

SchemeCipherWhat gets encryptedPlays on
cencAES-CTREvery protected sample in fullWidevine and PlayReady, including older devices; not Apple
cbcsAES-CBC with a patternOne block in ten, in a 1:9 patternFairPlay, plus Widevine and PlayReady 4.0 and later

Apple's HLS authoring specification rules out CTR-mode encryption on Apple devices, so as soon as FairPlay is in the mix your files need cbcs. That is why we encrypt DRM segments in cbcs mode at FastPix, so one DRM playback ID serves Widevine, FairPlay and PlayReady players from the same files (DRM set-up docs). Smart TVs older than PlayReady 4.0 only understand cenc, the one case where packaging twice still makes sense.

Multi-DRM solutions: build it yourself or use a platform

Multi-DRM has more moving parts than the encryption, and the decision comes down to who runs them.

PieceRun it yourselfOn FastPix
Packaging in cbcsA packager run for every title and renditionDone when the DRM playback ID is created
License serversThree, each with its own protocolOne endpoint per system for every DRM playback ID
KeysYour own key server and access controlsNew keys reach the edge within seconds (changelog)
PlayersBrowser DRM wiring for each platformFastPix Player, or license URLs for HLS.js, Shaka, Video.js, AVPlayer and ExoPlayer
Apple FairPlay credentialsRequiredRequired: you still enroll with Apple

Either way, the player has to fetch a license before the first frame, so a slow license server shows up as startup delay. Log license response times next to your other startup metrics.

DRM vs HLS AES-128 encryption

HLS has its own encryption, AES-128, and it is often mistaken for DRM. With AES-128 the manifest names a key URL (the EXT-X-KEY tag), the player downloads the key, and decryption happens in ordinary app or browser memory. Unless that key URL is locked down separately, anyone who can load the manifest can fetch the key. A single ffmpeg command will then save the stream as a plain MP4.

DRM changes where the key lives. The key arrives inside a license that only the device's CDM can open, so it never sits in memory your app or a browser extension can read. On hardware-backed levels, the decoded frames also travel a protected path to the screen. That is the distinction content owners care about: AES-128 keeps the files on the CDN scrambled, while DRM keeps the key out of reach on the device.

AES-128 behind a signed URL still suits internal video. For anything sold or licensed, we would not rely on it alone.

Which piracy methods DRM actually stops

DRM is strongest against methods that copy the file. This table maps how paid video ends up re-uploaded against what DRM does about each. The right-hand column uses our own controls from the video security docs as the worked example.

How the video leaksDoes DRM stop it?What covers the gap
Download tools and stream rippers save the segmentsYes. The saved file stays encrypted and won't play outside a licensed playerUser agent restrictions can also deny download managers, command-line HTTP clients and headless browsers
A paying viewer shares the stream linkPartly. Each playback still needs a licenseA signed JWT scoped to one video with a short expiry
Another site embeds or hotlinks your playerNoDomain allow and deny lists, up to 25 domains each, with wildcards
Screen recording on a phone or TV with hardware DRMUsually yes. The recording comes out blackNothing extra needed on these devices
Screen recording in a desktop browser with software DRMOften noA visible watermark burned into the video discourages re-uploads
A camera pointed at the screenNoNo technical control stops this; takedown notices handle it
Shared account loginsNoSession and device limits in your own app

Most of the "No" rows are access problems, not file problems. DRM protects the file and the path that decrypts it, which is why it works best layered with short-lived tokens and domain locks rather than as a replacement for them. Hotlinking in particular is covered in more depth in CDN leeching and stream protection.

What to do when your video leaks on Telegram

Telegram has become a common home for leaked courses and OTT episodes, because public channels and bots repost large files faster than one takedown removes them. Three steps shorten a leak's life:

  1. Cut off the leaked link. If a stream URL or playback ID is circulating, delete that playback ID and issue a new one. Making an asset private does not revoke URLs that were already handed out.
  2. Report public channels and bots. Telegram accepts copyright complaints at [email protected] from the rights holder or an authorised agent, with t.me/... links to the content (Telegram FAQ). It does not act on private groups and chats.
  3. Find out how the copy was made. A clean, full-quality file means someone downloaded the segments, so turn on DRM for that title. A screen recording points to a software-DRM browser, where a visible watermark helps more.

Why DRM playback fails in production

Most DRM playback failures show up as a black screen or a spinner with no useful error. A quick check is a screenshot during playback: with DRM enforced on a supported device, it comes out black. The usual causes:

  • Widevine L3-only devices. If your license policy requires hardware security for HD, budget Android phones and some older browsers that only report Widevine L3 will be refused or downgraded. Test on the cheapest device your audience owns.
  • Incomplete FairPlay credentials. FairPlay needs Apple-issued credentials on the license side, and without them Safari won't play. Apple only issues them to organization developer accounts, which need a D-U-N-S number (up to 14 business days) and a 2 to 5 day review, so start early (FairPlay integration).
  • Token errors at the license step. A missing or expired DRM token fails after the manifest has loaded, so it looks like a decoder bug.
  • An unprotected MP4 rendition. A downloadable MP4 bypasses DRM entirely. FastPix turns off MP4 support automatically on DRM playback IDs (FairPlay changelog).

Add multi-DRM to your on-demand videos with FastPix

If your library is on-demand (VOD) and you need Widevine, FairPlay and PlayReady without running three license servers, we serve all three from one DRM playback ID. Start with a free account, which comes with $25 in credits, then ask our support team to enable DRM and you get a DRM configuration ID back.

If you ship to Safari or iOS, start Apple's FairPlay enrollment the same day, because it runs on Apple's timeline. Then create a playback ID with accessPolicy: drm and follow the DRM set-up guide for license URLs and player examples.

FAQs

What is DRM for video content?

DRM (digital rights management) for video encrypts each video and releases the decryption key only inside a license that the viewer's device can open, so a copied file will not play. Streaming apps use three DRM systems: Widevine, FairPlay and PlayReady. FastPix applies all three to an on-demand video when you create a playback ID with accessPolicy: drm.

How do I add DRM to my video streaming app?

The usual route is a video API that packages the encryption and runs the license servers, so your app only signs tokens. With FastPix you enable DRM on your account, create a playback ID with accessPolicy: drm, and pass a playback token and a DRM token to the player. The same playback ID then plays with Widevine, FairPlay or PlayReady, depending on the device.

Which video API supports Widevine, FairPlay and PlayReady in one integration?

FastPix supports all three DRM systems from a single DRM playback ID, using one set of files encrypted with Common Encryption in cbcs mode. It provides a license endpoint for each system and works with the FastPix Player, HLS.js, Shaka Player, Video.js, AVPlayer and ExoPlayer. DRM covers on-demand video and is enabled per account through FastPix support.

Do I need to run my own DRM license server?

You don't need your own DRM license server if your video platform runs one for you. FastPix creates Widevine, FairPlay and PlayReady license endpoints for every DRM playback ID and checks each request against a DRM token your server signs. For FairPlay you still enroll with Apple as an organization and give FastPix your FairPlay certificate, private key, key password and ASK.

What is the difference between signed URL tokens and DRM for protecting videos?

Signed URL tokens control who can open a video: each token is tied to one video and expires, but the video itself is not encrypted. DRM encrypts the video so even a copied file cannot play without a license. On FastPix a private playback ID uses signed JWTs alone, for internal video, and a DRM playback ID uses both, for paid libraries.

Can DRM be used for live streaming?

Widevine, FairPlay and PlayReady all support live as well as on-demand video, with the same license flow. Live adds timing pressure, because thousands of viewers request licenses the moment an event starts. On FastPix, live streams are protected with signed playback tokens, and multi-DRM covers on-demand libraries.

Can I add DRM to videos I have already uploaded?

You can add DRM to videos you have already uploaded without encoding them again. On FastPix you create a DRM playback ID for the existing media, and the stored segments are repackaged with encryption. Public or signed playback IDs on the same video keep working alongside it, and deleting the DRM playback ID revokes that access.

Share

Stay Ahead of Video
Streaming Trends

Start shipping video today.