HLS Encryption
Encrypts the video segments themselves. Each chunk is scrambled and only opens with a key delivered separately, through a signed URL with a short lifetime.
Endpoints in this section
| Method | Path | Page |
|---|---|---|
| GET | /library/{library_id}/hls-encryption | Get HLS encryption status |
| PUT | /library/{library_id}/hls-encryption | Update HLS encryption status |
What it protects
Encryption is a stronger layer than the referrer whitelist and the download blocker: those control where the player may load, while encryption protects the media itself in transit and at rest on the CDN.
Business rules
- The setting applies to new uploads only. Videos that already exist are unaffected until they are reprocessed.
- Reprocessing requires the library to have
keep_original_filesenabled, and consumes credits. - Changes are cached — allow up to ~6 minutes before playback reflects the new value.
Encrypting a catalogue that already existsTurning this switch on does not touch existing videos. To encrypt them, reprocess them — one at a time or in batches of up to 100 — under Video Reprocessing. Reprocessing consumes credits, so budget for it before running it over a full catalogue.
Not the same as HLS Segment DurationThis section is about encryption. The
hls_segment_durationsetting (how long each HLS chunk is) is a different feature — see Configure Hls Segments.
Related sections
- Block Download — the simpler anti-download layer.
- Referrer Management — control which domains may embed the player.
- Video Reprocessing — apply encryption to videos that already exist.