Streaming a wedding for the guests who couldn't fly in

Someone always misses the wedding. A grandparent who cannot travel. A sibling on deployment. Friends stuck across oceans with flights that never lined up. The ceremony still happens in one room — but a careful stream can put the people who love them in the seats they could not take.

This is not a multi-camera TV show. It is one operator, a browser, a private link for family, and a recording you can hand the couple later. ApexStream’s Web Studio is built for that kind of day: one tab, invite links for anyone who needs to appear on camera, scenes you can switch without a control room, and cloud recording on Hobby and above so the stream does not vanish when the last guest closes the window.

Decide what “private” means before you book the venue Wi‑Fi

Family streams fail less from camera choice than from the wrong audience surface. A public YouTube premiere is fine for some couples. Many want the opposite: only people who received an invite.

ApexStream multistreams from a single encode to the platforms you choose, including custom RTMP and custom SRT destinations. For a wedding, that usually means one private endpoint — a password-protected player, a church or venue RTMP target, or a destination the couple’s planner already uses — rather than fanning out to every social profile at once. Free plans reach two destinations; Hobby three; Creator five. For a private family day, one well-chosen destination is enough. Leave the rest empty.

If anyone in the party will watch on Facebook or Twitch as well, you can still add those — just treat them as intentional, not default. The point of the stream is presence for people who could not fly in, not growth metrics.

Run the day as a single operator in Web Studio

Weddings do not give you a second engineer. Web Studio is a browser production studio: you open it, pass noise suppression (required before go-live), and work from scenes and layouts instead of a cart of switchers.

A simple scene plan is enough:

• Wide room — processional, vows, recessional
• Closer frame — readings, rings, anything faces matter for
• Holding / welcome — soft title or couple names while people join early
• Optional portrait 9:16 output under Scenes → Output if the primary remote audience is on phones

Guests join by invite link: five on Free, ten on paid plans. That is useful when an officiant, a reader, or a musician is remote and needs to be in the mix without shipping hardware. For a classic in-person ceremony, you may only need the operator and one camera operator who is also holding the laptop — keep the invite list short so nobody accidentally becomes “talent” mid-vows.

Overlays, a ticker, and a countdown exist if you want them. Use restraint. A countdown for “ceremony starts in” is kind to late joiners. A lower-third with the couple’s names once, clean Brand Kit colors if they already have a wedding palette, then get out of the way. Live captions (host mic only, S/M/L) help hard-of-hearing relatives when the room mic is on the host path — they are not a full multi-mic caption system, so place the mic you care about accordingly.

Audio is the real guest of honor

Remote family will forgive a soft wide shot. They will not forgive vows they cannot hear. Prefer a lav or a discrete shotgun near the couple over the laptop’s built-in mic. Noise suppression in Web Studio is mandatory before go-live for a reason: hotel ballrooms and outdoor gardens are noisy. Still, suppression is not a substitute for putting a microphone where the words are.

Test the full path the night before if you can: Web Studio → your private destination → a phone on cellular, not the venue Wi‑Fi. Upload a short sample, play it back, confirm the stream key is for the right event. Custom RTMP mistakes show up as “we’re live” on a blank player.

Treat the recording as the keepsake, not an afterthought

Cloud recording starts on Hobby. Free cannot record. For a wedding, that plan line matters: the live stream is for people who could not fly in; the file is for people who were there and still want to rewatch the processional, and for the couple six months later.

Hobby and Creator keep recordings for 15 days of retention (Hobby also 15; Free is 7 and still cannot record). Scale is 30; Enterprise 365. Storage follows the plan — 25GB on Hobby, 100GB on Creator, 500GB on Scale — which is plenty for a ceremony-length file if you are not also archiving every rehearsal. Download the master soon after the day ends and put a copy in the couple’s shared drive. Do not assume the cloud retention window is the archive.

Stream length caps are generous for a wedding block: Free 2 hours, Hobby 6, Creator 8, Scale 10. A ceremony plus greeting rarely needs more than Hobby if you start when doors open and stop after the recessional. If you are also covering speeches later, start a second session rather than leaving a single stream idle for hours.

Resolution on Free tops out at 720p with a watermark. Hobby reaches 1080p on the encoder path (Web Studio itself is 720p on Hobby). Creator and above unlock higher ceilings. For family watching on a living-room TV, 1080p without a watermark is the floor you want; plan the account accordingly before the weekend, not during hair and makeup.

One stable wide, one clear mic path, one private destination, one cloud recording downloaded the same night — that is a complete wedding stream.

A day-of checklist that fits on a note card

1. Confirm the private custom RTMP or SRT destination and test key the day before.
2. Open Web Studio early; pass noise suppression; lock the scene order.
3. Place the mic for vows first, cameras second.
4. Start cloud recording when you go live (Hobby+).
5. Switch only when the room switches — processional, vows, rings, kiss, exit.
6. End cleanly; download the recording; send the private replay link only to the invite list.

Unified chat (Hobby+) can matter if remote guests watch on YouTube, Facebook, or Twitch and you want to read reactions in one place — less relevant on a fully private player with no chat surface. Skip tools you will not staff. A wedding stream dies when the operator is debugging chat instead of watching the aisle.

What success looks like

Success is not a highlight reel. It is an uncle in another timezone who saw the exchange of rings in real time, and a file the couple can open on their anniversary without hunting through someone else’s phone. Web Studio keeps the operation small enough that one calm person can own it. A private destination keeps the day for the people it belongs to. Cloud recording turns the stream into something that outlasts the Wi‑Fi.

Do that, and the guests who could not fly in still get a seat — not a production credit, not a social campaign, just a clear view of the moment they would have stood for if the flight had existed.