Clip timing & outputs

Choose which part of the stream

Seconds before moment30 example

Include the lead-up.

Seconds after moment10 example

Include the result and immediate reaction.

Estimated chat reaction delay3 seconds example

Move the estimated moment earlier than detection.

Save to disk

1. 1

   Choose a folder

   Select a download folder for this page session. Grant access to the known replay media host when asked.

2. 2

   Keep the source available

   The local save uses available DVR and the selected saved resolution. The total before/after duration is limited to 180 seconds.

3. 3

   Watch the individual result

   The requested range stays frozen during permissions, network retries and conversion. A missing range or busy player sends the moment back to review.

Publish on Kick

Automatic publication uses Kick's native clipping action and your signed-in account. It runs before local conversion and only close to the requested ending. Kick's native action creates its latest footage; it does not accept the same fixed older UTC range as the local DVR saver.

Use the Moments queue

1. 1

   Read why it triggered

   Each moment includes its detection context and requested timing. The queue keeps at most 50 moments.

2. 2

   Check both output statuses

   Saving and publication are independent. One can succeed while the other fails or needs review.

3. 3

   Choose a manual action

   Review a local save or open Kick's editor to choose a range and publish yourself. A retained older moment may need local DVR rather than native latest-footage publication.

Limits that prevent surprises

Only one automatic job runs per page. Existing replay, recording, repair or video-saving work can defer a moment to review. Completed or cancelled queue entries can be replaced; unresolved entries are retained when the queue is full. Missing DVR dates, unavailable starts and codec limits can prevent precise output.