Recording duration is controlled by both the live source and the user's entitlement. It is not a fixed video-template length.
Free duration
The Free plan has a 3,600-second cap. When one live has both Free and paid recipients, the service can capture the full eligible source once and produce a capped delivery variant for Free users. A failure to create a safe capped variant must never expose the paid full-length artifact to a capped recipient.
Paid duration
Basic and Pro have no KickLiveRec product duration cap. Kick source availability and connection interruptions can still end a recording.
The recorder should not stop a paid live at 60 minutes merely because the default Free value exists. Each target's plan is evaluated when it joins the recording.
Who decides when recording ends?
Normally the creator does. KickLiveRec continues while the refreshed public source represents the same logical live. A /stop request, shutdown drain, source identity change or unrecoverable media failure can close it earlier.
What happens to a large video?
KickLiveRec verifies the completed media and checks its final duration. If the output exceeds Telegram's single-file limit, KickLiveRec creates ordered parts and sends them in order with the contact sheet.
Does a long live take longer to deliver?
Yes. More bytes require more download, verification, merge and Telegram upload time. /pending can show that the recording is still being processed after capture ends.