Package and publish content

Package and publish DRM-X 6.0 protected VOD using DASH/CENC, HLS/CBCS, single-key or multi-key quality tiers, and managed or registered cloud storage.

View Markdown Live examples ↗Updated 2026-09-05

Source → encrypted package → validated publication → stable Content ID.

Choose the workflow#

Managed packaging

Use Console for the shortest path from source upload to a Published protected file and managed 1AICLOUD delivery.

DRM-X CLI Packager

Run Windows x64 packaging with a one-use Packaging Access Token. Upload to managed hosting or a registered Amazon S3 or Cloudflare R2 destination.

CPIX integration

Integrate a controlled media pipeline while keeping content keys and provider credentials out of build logs and operator workstations.

Prepare the source correctly#

Encode the final bitrate ladder, frame rates, audio languages, and subtitle tracks before encryption.
Use Single Key for broad compatibility or Multi-key Quality Tiered for AUDIO, SD, HD, UHD1, and UHD2 controls.
Produce DASH/CENC for Widevine and PlayReady and HLS/CBCS for FairPlay when those platforms are enabled.
Upload only encrypted segments, protected manifests, and intended public delivery assets.

Publication is the security boundary#

A successful packaging job is not automatically a playable catalog item. Published status means the immutable output, registered manifest variants, storage destination, key model, Content ID, and validation evidence are ready for the Playback Session API.

Do not paste a public manifest URL into application codeSelect the Published protected file by trusted Content ID. DRM-X returns the authoritative manifest that belongs to that file and requested DRM.

Validate before customers receive it#

Open Universal Playback Lab and sign in.
Select the exact Published protected file.
Confirm that Single Key or Multi-key Quality Tiered was detected correctly.
Test every platform, promised resolution, audio language, subtitle, stop/release path, and entitlement denial.