Shaka Packager started in 2014 as part of Google's Shaka project (Shaka Player + Shaka Packager). It reads MP4, WebM, MPEG-TS, WAV and other formats; outputs CMAF segments, HLS playlists, DASH MPDs; supports CENC encryption with key servers from Widevine, PlayReady and FairPlay; runs as a CLI binary or a C++ library. By 2026 it is the default packager for tens of thousands of self-hosted OTT pipelines and the underlying engine in several managed services.
The reason for its dominance is composition. Shaka Packager handles the file-format glue without imposing a workflow: an FFmpeg encode pipes into Shaka, Shaka emits CMAF and manifests, Shaka writes to local disk or S3, downstream services take it from there. The CLI is scriptable, the configuration is JSON, the output is deterministic. Bug fixes and updates are frequent — the project sees multi-monthly releases through 2026.
Shaka Packager competes with commercial packagers (Wowza, Unified Streaming, Bitmovin Packager, AWS Elemental MediaPackage) and one other open-source choice (Bento4). The commercial tools often add JIT packaging, fine-grained DRM features, or managed-service convenience; Shaka is the choice for teams that want self-hosted control and don't need those extras. Most cloud-native OTT pipelines launched after 2020 use Shaka Packager in some role.
