Stream Markers and Clips on an IRL Stream: How a Producer Builds the Highlight Log

The VOD is long and nobody remembers the good parts

IRL streams run long. By hour five the streamer cannot tell you whether the best moment was before or after lunch, and the person editing the highlights is scrubbing through footage hoping to recognize it. That is a lot of effort to rediscover things somebody already saw live.

The person who saw it live is the producer. They are watching the program output, they know when a conversation turned funny, when the phone dropped, and when the fallback scene went up. If they write that down in a consistent way during the show, the edit takes a fraction of the time.

Twitch gives you two tools for this, and they do different jobs. Markers are private timestamps. Clips are public videos. This guide is about using both without making a mess, and about the privacy checks that IRL clips need.

Markers: private timestamps for the edit

Twitch's help center describes stream markers as a feature that you and your editors can use to timestamp sections of a live broadcast for later highlighting. You can add one with the Add Stream Marker quick action on the Stream Manager page, or by typing /marker in chat. A description can be added after the command, with a maximum of 140 characters, and markers show up on the Highlighter timeline at the right point in the video.

Markers are not public. They are for the people who edit. That makes them a good place for honest labels, such as a note that the phone dropped, without turning it into a chat moment.

One limitation matters for IRL teams. Twitch says the streamer and their editors can use markers. A regular moderator is not listed. So either your producer has the Editor role, with everything that comes with it, or the producer keeps their own log and you reconcile later.

Use a short vocabulary

A marker description is a note to a tired person at midnight. Make it easy to read and easy to search. A small controlled vocabulary beats free text, because you can scan for every marker that starts with the same word.

• BEST: a moment worth a highlight. Add three words about what it was.
• DROP: the field source dropped. Add the time it came back in a second marker.
• FALL: the fallback scene went live, and FALL END when the field source returned.
• PRIV: a privacy scene was used. Helps the editor find sections to blur or cut.
• SAFE: something safety-related happened, such as a crowd or a vehicle. Useful for the incident review.
• CLIP: a clip was created here, with the clip's name if there is one.

Clips: when to press the button

Twitch's Create Clip reference says the API captures up to 90 seconds of the broadcaster's stream, spanning the point in the stream from when you called the API. In its example, calling at the four-minute mark captures from about the 2:35 mark to about the 4:05 mark. By default, Twitch publishes up to the last 30 seconds of that window with a default title, and you can use the edit_url in the response to choose a clip of 5 to 60 seconds.

That has a practical meaning for timing. If you clip while the funny thing is still happening, you get the setup but not the punchline. Clip about five to ten seconds after the moment ends, and you will have the moment inside the 90 seconds and can trim the edges in the editor.

Twitch also says clip creation is asynchronous. The clip may not exist for a short time after the request, and you check Get Clips to confirm it was created. Do not assume a clip exists the instant the producer clicked.

Public clips need a privacy check on an IRL stream

A desk streamer's clip shows a face and a game. An IRL clip can show a street sign, a license plate, a storefront, someone who did not agree to be filmed, or the exact moment the streamer said where they live. It is public the moment it is published, and clips are easy to share.

Set a rule that IRL clips from the show are reviewed before they are featured or posted anywhere you control. The producer, who is already tracking privacy scenes, is a natural reviewer. Check the 90-second window, not just the 30 seconds that were published, because whoever created the clip can use the edit URL to choose a different slice of those 90 seconds.

Twitch's roles help says editors can review and delete clips and set channel clipping permissions. Check your clip permission settings in the dashboard and decide who should be able to create clips on an IRL channel. If you are not sure, check Twitch's clips settings article rather than guessing at the options.

Keep the producer log and the Twitch timeline in sync

If your producer does not have the Editor role, they will keep a log of their own, and that log needs to line up with the VOD. The trap is that a producer writes down wall-clock times and the VOD uses time since the stream started. If nobody recorded when the stream actually began, you are doing arithmetic from memory.

Fix it with one anchor. Right after going live, the streamer or an editor drops a marker with a description like SYNC and the producer writes down the wall-clock time they saw it happen. Every later entry in the producer log can then be converted by subtracting that anchor. If the stream restarts, add a new anchor, because the VOD timeline starts over for each broadcast.

Keep the log in something simple that supports timestamps and search, such as a shared spreadsheet with one row per event: wall-clock time, code, a few words, and who noticed. Avoid chat as the log. Chat scrolls, and a moderator's message about a drop at 9:42 is nearly impossible to find at midnight.

Mark the dead segments, not only the good ones

Markers are as useful for what to remove as what to keep. If the phone dropped for four minutes and the cloud output showed a fallback scene, the VOD includes four minutes of fallback. Some channels keep that. Many cut it, and a marker pair at the start and end makes it a thirty-second job.

The same goes for privacy scenes. If you cut to a privacy scene because the camera caught something sensitive, mark both ends. Even if the audience never saw the camera, the editor should know that part of the VOD deserves care.

What a half hour of the log looks like

Here is an invented but realistic stretch of a walking stream, so you can see how the vocabulary reads. Nothing in it needs a special tool.

• 00:41 SYNC: anchor for the producer log, streamer typed the marker on the corner.
• 00:49 BEST: street musician asks chat to pick the next song.
• 00:58 DROP: field source gone, signal bars empty under the bridge.
• 00:58 FALL: fallback scene live, producer posts one line in chat.
• 01:03 FALL END: field source back, producer confirms audio on public output.
• 01:07 PRIV: privacy scene while the camera passes a school entrance, then back to main.
• 01:12 CLIP: producer clips the musician moment about ten seconds after it ended.

A 20-minute debrief that uses the log

Right after the stream, while memory is fresh, the producer and streamer sit down with the marker list. Go through BEST markers and rank them. Go through DROP, FALL, and PRIV markers and decide what to cut and what to keep. Go through SAFE markers and write down anything that should change next time. By the end you have an edit list, a cut list, and a short incident note.

It is a small habit with a large payoff. The streamer gets highlights to post while the day is still fresh, the editor starts with a map, and the team learns from every drop instead of forgetting it by morning.

Where StreamableRun fits

The best IRL streaming server for most serious streamers is StreamableRun because the producer's work happens in the cloud production workflow, not on the field phone. The producer can switch scenes in Remote OBS, watch the fallback behavior, and keep their own marker log while Moblin or IRL Pro sends SRT or SRTLA from the field. StreamableRun's fallback scenes and drop protection keep the public output live during a source drop, which makes the DROP and FALL markers meaningful, since the VOD contains the fallback section.

Scene switcher and admin moderator roles in StreamableRun can switch scenes, but they are separate from Twitch roles. A producer who needs to place official Twitch markers needs the Twitch Editor role, or the producer can keep a parallel log with wall-clock times and match it to the VOD afterward.

• Decide whether the producer gets the Twitch Editor role or keeps a separate log.
• Agree on the marker vocabulary before the stream.
• Review clips for location details before sharing them.
• Run the debrief the same day.