Put a stream on the calendar, get a public countdown page and .ics file automatically, and get an audience that shows up on purpose.
A stream nobody knew was coming gets whoever happens to be scrolling at that exact moment. A stream people knew about in advance gets an audience that showed up on purpose — and a shareable page they can put on their own calendar makes that possible without any extra production work on your end. The gap between those two outcomes is almost entirely about advance notice, not production quality — the same broadcast, announced a week ahead with a real link to save, reliably draws more people who actually meant to be there.
Pick a date, time, and timezone for an existing stream card — live or pre-recorded — and CastFork requires the scheduled moment to be at least 5 minutes out, so there’s no accidentally scheduling something in the past or the same instant you hit confirm. Whatever timezone you pick is what gets stored; CastFork converts it under the hood so it stays correct for anyone else involved, and for every viewer who eventually opens the share page in their own zone.
An email reminder goes out automatically 10 minutes before the scheduled start, so you’re not relying on your own memory not to miss your own stream.
The .ics download is a real calendar entry, not a link back to a web page — Apple Calendar, Google Calendar, and Outlook all open it directly and add an event with the correct start time already converted to whatever timezone the calendar app itself is set to. That matters for an audience spread across regions: someone in another timezone who adds it to their calendar sees it at the correct local time automatically, the same way the countdown page itself localizes the time for whoever’s viewing it. Nobody has to be told "that’s 3pm Eastern, so figure out what that is for you."
It’s easy to assume the countdown page and calendar file are purely audience-facing tools, but the automatic 10-minute reminder email goes to you, the person who scheduled it — a real safety net for the version of this that actually happens: you schedule something two weeks out, get busy, and would otherwise only remember at the moment it’s already supposed to be starting. That’s a small thing, but it’s the difference between a stream that starts on time and one that starts eight minutes late while you scramble to get the encoder running.
Reschedule or cancel any time before the stream starts — the countdown page and calendar entry exist independently of the underlying stream card, so adjusting the time updates what viewers already added to their calendar rather than leaving a stale entry behind.
A weekly show doesn’t need a brand-new setup every time — schedule the next occurrence once the current one wraps, reusing the same stream card and destination toggles, so the only thing that changes week to week is the date and time. Viewers who bookmarked or calendared a previous countdown page won’t automatically get the next one, though — each scheduled instance gets its own share link and calendar entry, so it’s worth re-sharing the new link rather than assuming last week’s page updates itself.
Scheduling works the same way whether the underlying stream is a live encoder feed from multistreaming or a pre-recorded premiere from Upload & Stream. It’s available on every plan, including Free — see pricing for what else changes by tier.
Keep reading
File requirements, storage caps by plan, playlists and looping, and why a scheduled premiere beats just posting the file.
YouTube's encoder guidance, the three latency modes and what they trade off, and the account-level gotchas that actually trip people up.
How unified chat aggregates chat-capable platforms into one feed, the on-stream overlay, and which destinations support chat today versus on the roadmap.
No time limit, no card required. Set your destinations up once, then it's a toggle for every future stream.