Features

One stream, four stages, and you are only needed for two of them

You stream, and later you approve. Everything between those two is the product.

Stage one

Capture

A small desktop app runs on the PC that runs OBS. It is the only piece of Aftercast that ever touches your footage, and it does not move it.

It connects to OBS over the WebSocket server built into OBS 28 and later, so it knows when you start recording, when you stop, and what your scene looks like. A session begins the moment recording starts — not when you go live, because a stream with no local recording has nothing to cut from.

A setup check screen that tests every requirement and says exactly which one is wrong.
Reads OBS’s own WebSocket port and password rather than asking you to copy them.
Works with OBS on a second machine, given its address and an open port.
Signs in with your email and password, or pairs with a single-use code for a shared or headless studio PC.

The full recording is cut on your machine. Only the seconds around each scored moment are uploaded, plus one compressed audio track used for the transcript. Uploading the whole file is a setting, and it is off unless you turn it on.

Segments, not streams: Only the seconds around a scored moment are uploaded, with a compressed audio track for transcription. Archiving the full recording is a setting, off by default, throttled if you are still recording when it runs.
The replay buffer, if you run one: With OBS’s replay buffer started, a marked moment can be captured while you are still live instead of waiting for the stream to end. Without it, nothing breaks — clips are cut afterwards.
A marker hotkey that works mid-game: Ctrl+Shift+M by default, registered globally so it fires while your game has focus. If another program already owns the combination, the setup check tells you rather than leaving you to wonder.
Scene layout, not guesswork: OBS reports where each source sits, so a vertical crop can be taken from your actual layout instead of inferred from a flat video.
Recovers on its own: If the capture PC is off when the server asks for a segment, the request is repeated when the machine comes back. A session waits rather than losing the clip.
Credentials in the OS, not a file: A paired machine holds a device credential in the Windows credential manager. Pairing codes are single-use and expire after ten minutes.

Stage two

Detect

Signals are collected and scored while the stream is running, then clustered into moments. Overlapping signals combine, so several weak unrelated hints add up — and ten of the same hint do not.

Chat activity: Message rate, unique chatters and emote density, including third-party emotes from 7TV, BetterTTV and FrankerFaceZ.
Channel events: Follows, subscriptions, cheers and raids, received live rather than reconstructed from a finished VOD.
Game logs: Events parsed from a supported game’s local log files. Treated as a bonus signal, because most games either write no log or run on a console.
Audio: The mix your viewers hear, captured as a compressed sidecar for transcription and audio-based detection.
Your markers: The hotkey, and a Mark moment button on the dashboard. Weighted highest, because it is the only signal that is not an inference.

Each lane is one kind of signal. A moment where several kinds coincide scores higher than a moment where one kind repeats — agreement between independent sources is a better indicator than volume from a single one.

What a score means

It is a measure of how much independent evidence coincided at one point in your stream — not a prediction of how a clip will perform. Every candidate lists the signals that produced it. Clips are cut with a lead-in before the moment and a tail after it, because the setup usually matters as much as the payoff, and you can adjust both.

Sessions tell you where they are

live: The stream is running and candidates are being scored.
footage_pending: The stream ended and at least one segment has not arrived. Almost always the capture PC being off.
in_review: Everything expected is in. The queue is waiting for you.
done: Every candidate has been approved or rejected.

Stage three

Polish

The queue is where you spend your ten minutes. Most of the work that used to fill an evening has already been done by the time you open it.

Review and trim: Score, signals and preview on each candidate. Trim either end, approve, reject with a reason, or download the file. Rejection reasons are the record of what the scoring got wrong, so they are worth giving honestly.
Transcript beside the clip: The stream transcribed and searchable, shown next to the clip while you edit it. Export as SRT, VTT or plain text.
Chat beside the clip: The messages from the moment itself, in the editor. Usually the fastest way to tell whether a spike was the thing you remember.
Word-level captions: Timed per word and restylable, rather than a block of text sitting under the video.
Vertical reframe: A 9:16 crop derived from your OBS scene layout, adjustable by hand. When the scene data exists, nothing is being guessed at.
Cover frames and thumbnails: Pick a cover frame, or build a thumbnail in a layer editor with export presets.
Titles, descriptions, hashtags: Drafted per platform from the transcript. They are suggestions and they are sometimes wrong — read them before they go out under your name.
Brand kit: Logos, palette, caption styles, watermark and bumpers, applied everywhere instead of re-picked per clip. Pro and above.
A clip library: Everything you have approved, searchable across sessions, so a clip from three streams ago is findable.

Stage four

Publish

Approved clips go out on a cadence you set, and the things around the stream — overlays, the schedule, your public page — are managed from the same place.

Where it posts: TikTok, YouTube Shorts and Instagram Reels, with preflight checks, retries and quota tracking so a failed post is visible rather than silent.
What you can connect: Twitch, YouTube, Kick, TikTok and Instagram. Twitch and Kick are also where chat and channel events come from. Disconnect any of them at any time.
A scheduling calendar: Queue clips across the week with cadence guardrails, so an enthusiastic Sunday does not become nine posts in one afternoon.
Auto-publish: Approved clips released on a schedule without a second visit. Pro and above.
Overlays for OBS: Alerts, chat, event list, goals and now-playing. The desktop app adds them as browser sources to a scene you pick — it only ever adds, never moves or removes what you already have, and refuses to run while you are recording.
Go-live and recap posts: Announcements when you go live and a recap after, to Discord and Bluesky, with caps so nobody gets spammed.
Analytics: Peak and average viewers, chat rate, follower change and event totals per stream; views, likes and shares per clip at 24 hours, 72 hours and a week; live concurrents across platforms on one screen.
A public creator page: Live status, a player, a clip gallery, your VOD archive and your schedule on one link, themed by your brand kit.
A workspace, if you have help: Owner, admin and member roles, so an editor can cut without touching billing, with an audit trail of who changed what. Staff plan.

What is not here yet

The capture app is Windows only. Invites are links you send yourself rather than emails, because no mail provider is wired up on every deployment. Some of the catalogue above is newer than the rest and will have rough edges. The FAQ is the honest version of this list.

The fastest way to judge this is one stream

Detection either agrees with you or it does not, and nothing on this page answers that. The free plan surfaces up to ten clips a stream, which is enough to find out.

Get started free Compare the plans

Free plan, no card. You need OBS 28 or newer on Windows 10 or 11.