Reduce costs
Lower bandwidth and storage expenses without compromising quality.
Encrypt your HLS streams with AES-128 for industry-standard video protection.
AES-128 encryption scrambles your HLS video segments so they can't be played without the decryption key. Unlike DRM, which locks playback to devices, AES encrypts the stream itself—making it safe to deliver over untrusted networks and harder for casual pirates to download from CDN caches. It's the standard for mainstream streaming and works on every device that plays HLS.
Specify AES-128 encryption in your transcode configuration.
Use a Qencode-managed key or provide your own.
Every .ts segment in your HLS stream gets encrypted with the AES key.
Players fetch the key from a separate, protected endpoint.
Even if intercepted, video files are unplayable without the key.
Lower bandwidth and storage expenses without compromising quality.
Automate complex processing that would take hours manually.
Handle thousands of videos with the same API call.
Simple REST API with comprehensive SDKs and documentation.
A streaming platform encrypts all library content with AES-128 so cached files on CDNs can't be downloaded and played standalone. Reduce bandwidth theft by 70% and protect against casual piracy while maintaining compatibility with all standard HLS players.
An online university encrypts lectures with AES-128 so students can watch securely even over open WiFi networks. Meet compliance requirements for educational data protection and reassure students that enrollment videos are secure.
A company encrypts internal training and compliance videos with AES-128 so they can't be extracted from corporate networks. Prevent insider threats and satisfy security audits requiring encryption in transit for sensitive content.
Watch a quick walkthrough showing how to configure and use AES Encryption through the Qencode dashboard and API.
| API Method | POST /v1/start_encode2 after creating a task with /v1/create_task. |
| Key Parameters | output: "advanced_hls", encryption, stream[]. |
| Encryption Object | encryption.key, encryption.iv, encryption.key_url. |
| Encryption Standard | AES-128 encryption for HLS output. |
| Key Management | Customer-provided key. Generate a 16-byte key file, host it on your server, and provide its URL in key_url. |
| Key / IV Format | key is the hex value of the generated key. iv is a generated initialization vector in hex. |
| Supported Output Format | advanced_hls. |
Enable AES-128 encryption on an advanced_hls output with Qencode-managed keys.
{
"query": {
"source": "https://your-storage.com/video.mp4",
"encoder_version": "2",
"format": [
{
"output": "advanced_hls",
"separate_audio": 1,
"stream": [
{
"video_codec": "libx264",
"resolution": 2160,
"optimize_bitrate": 1,
"framerate": "30",
"keyframe": "90"
},
{
"video_codec": "libx264",
"resolution": 1440,
"optimize_bitrate": 1,
"framerate": "30",
"keyframe": "90"
}
],
"segment_duration": "6",
"encryption": {
"key": "your_encryption_key",
"iv": "your_encryption_key_iv",
"key_url": "https://your-server.com/aes-128/encryption.key"
}
}
]
}
}Copy this payload and use it with your API key to test AES Encryption on your own videos.
View AES Encryption TutorialIncluding with HLS Transcoding
AES-128 encryption is available for HLS outputs. Pricing follows standard HLS transcoding usage, with no separate encryption feature fee.
We love creating powerful solutions that are aligned with the needs of your business.
Please send us a message if you have a question or Schedule a call for a demo to discuss your integration.
Contact us with any questions. We'd love to help.
Los Angeles, CA - (HQ)
San Francisco, CA
New York, NY