DRM-X 6.0 dove and olive branch logoDRM-X 6.0Docs
/
◎ English

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 MarkdownLive examplesUpdated 2026-09-09

Encrypt and publish your video

Prepare the source video, encrypt it, publish the output, and use its Content ID when requesting playback.

  1. Source video

    Choose the video and audio tracks you want to protect.

  2. Encrypt and package

    Create encrypted media using CENC or CBCS, according to the target DRM system.

  3. Publish the output

    Upload the encrypted media and register its playback URLs.

  4. Content ID

    Use this identifier in your backend to request playback for the published video.

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

Choose the workflow#

DRM-X 6.0 Packager Desktop

Recommended for Windows. Save and test a protected credential profile, generate fully editable CLI parameters with Steps 1–3, import source files, choose an output folder, and monitor batch encoding, encryption, verification, and upload.

DRM-X CLI Packager

The same Windows Suite includes the complete CLI for professional automation. Linux uses CLI only with DRMX_PACKAGER_SITE_ID, DRMX_PACKAGER_ACCESS_KEY, and DRMX_PACKAGER_KMS_TOKEN supplied by a trusted environment.

CPIX integration

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

Follow a detailed tutorial#

Desktop: step by step →

Profile setup, screenshots, encoding choices, file batches and progress.

CLI: commands and recovery →

Copyable commands, automation and upload-only recovery.

Long videos, 4K and 8K →

Estimate package size, segment counts and upload time interactively.

Prepare the source correctly#

  • Desktop and CLI can encode a master source automatically before encryption. If using pre-encoded inputs, prepare the final ladder, frame rates, audio and subtitle tracks first.
  • 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#

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