Skip to content

Current formats and limits

These are the currently implemented limits. An installation may also be limited by its disk, processing resources, and operational configuration.

Area Scope
File size Up to 5 GiB
Duration Up to two hours
Configured maximum resolution 1080p by default; optional 1440p or 2160p
Upscaling Smaller sources are not upscaled
Video playback HLS fMP4, H.264/AAC
Audio only MP3, WAV, FLAC, M4A, Ogg, and AAC sources
Output audio HLS AAC and M4A downloads available depending on the resource
Subtitles SRT/WebVTT; WebVTT chapters
Alternate audio Up to ten additional tracks per asset
Video downloads MP4, generated independently
Analytics history 30 days
Monitoring 24 hours
HLS VOD import Finite, with ENDLIST; up to 10,000 segments and 16 playlists
Watermarks Up to five PNG/JPEG images; 10 MiB and 4096×4096 per image
Test videos Up to ten published seconds; asynchronous removal after 24 hours
Attached local text UTF-8 SRT/WebVTT up to 5 MiB
Usage Up to 90 days; storage is the latest observation
Usage CSV 10,000 assets and 20 MiB; v3 adds auxiliary tracks
Incident channels Up to 50 active per environment

Creation or import does not imply immediate availability. Content must finish processing. Generated renditions depend on source dimensions and content; portrait aspect ratios are preserved and the selected resolution policy applies.

Audio normalization is optional when creating an asset. It does not change original bytes and is not offered as a retroactive toggle for an existing asset.

A public link, temporary access, a download, and the original have different lifecycles. Creating a download does not publish the asset. A temporary URL may expire while its file remains stored.

Revocation does not remove previously downloaded files. Delete the asset only when you also want to remove associated objects, with the appropriate permissions.

The platform covers video and audio on demand. It does not include live video, DRM, AI capabilities, or public billing. The SDK and player are built from the repository; do not assume they are published on npm.

Local playback verification covers Chromium. It does not certify all browsers, physical mobile devices, AirPlay, or Cast.

See details for HLS, tests and watermarks, clips, monitoring, and Usage. Implementation status distinguishes available code from its local and remote evidence.