OBS Integration Guide

Put a Church Countdown
in OBS (Browser Source)

If your service already runs through OBS, you don't need a second computer or a dedicated stage clock. OBS can render a web page as a source — so the countdown becomes one more layer you can show, hide, or move. Here is the setup that survives a Sunday morning.

What you need

Three things: OBS Studio on the machine that already drives your stream or projector, a Castimer countdown created and running, and a URL that renders that countdown on its own without any interface around it. Castimer gives you two such URLs, and they solve different problems.

Option A — the display link (/event-timer/display?room=YOUR-ROOM). This is the full-screen stage view: current segment name, remaining time, and what comes next. It follows an agenda you control from your phone. Use this when you want the whole service timed, not just one countdown.

Option B — the widget URL (/widget?type=event&title=Service&date=...). This is a compact countdown to a fixed date and time — the pre-service clock that counts down to 10:30. Use this when you only need “how long until we start.”

Both are ordinary web pages. OBS does not care which one you use; the difference is what the page shows and who controls it.

Step 1 — create the countdown and copy its link

For a service agenda, open the church service template — it pre-fills welcome, worship set, scripture reading, sermon, response, offering and benediction with editable durations. Castimer assigns your controller a room code and generates the matching display link; copy it from the controller's “copy display link” action.

For a pre-service countdown, copy the iframe/URL from the embed panel on a holiday or preset page, or build the URL directly: type event, a title, and an ISO date. The widget also accepts theme (light or dark), lang, and tz. Set show_brand=0 if you don't want the small Castimer wordmark in the corner on screen.

Keep the link somewhere you can reach in ten seconds — a note on the streaming phone, or a bookmark on the OBS machine. You will paste it into OBS exactly once, but you will re-open the controller every week.

Step 2 — add a Browser Source in OBS

In OBS, add a new source and choose Browser. Paste the Castimer URL into the URL field.

Set the width and height to the same resolution as your canvas. If you stream or project at 1080p, that is 1920 by 1080. This matters more than it looks: a browser source set to 800 by 600 renders a 800-pixel-wide page, and OBS then scales it up — the digits get soft and the layout shifts. Match the canvas and the countdown stays crisp.

Leave Shutdown source when not visible off. It sounds efficient, but it also means the page stops updating while hidden, and you get a stale number when you bring it back mid-service.

Two more toggles worth knowing: Refresh browser when scene becomes active is safe to leave on for the widget option; for the display link, leave it off so a scene switch doesn't reload the page and briefly blank the countdown.

Step 3 — decide how it sits on screen

There are two honest layouts, and the right one depends on whether the countdown is the main content or a corner reminder.

Full-frame: the countdown fills the screen. Best for the pre-service clock and for the moment before the sermon starts. Nothing competes with the number.

Lower-third or corner: the browser source is scaled down and positioned over your camera feed. The number stays visible while the congregation still sees the room. At 1080p, keep the digits at least 120 pixels tall — that reads from roughly the back third of a typical sanctuary on a 3-metre screen.

Whichever you choose, test it with the real projector, not on the OBS preview. Preview is a metre from your face; the congregation is twenty metres away.

Step 4 — control it from your phone, not the OBS machine

This is the part that makes the setup usable week after week. The OBS machine can stay untouched behind the desk: the countdown is driven by the controller, which runs on a phone in your pocket.

On the phone you can start, pause, jump to the next segment, add or remove a minute, and push a short message to the screen. Because the display page is connected to the same room code, every one of those actions shows up in OBS within a second or two — no alt-tabbing, no climbing behind the desk, no interrupting the operator.

If you run two services, keep the same room and reset the agenda between them; if you run a separate youth venue, use a different room code so the two displays never cross.

Troubleshooting the three failures that actually happen

The source is blank. Almost always the URL lost its query string when it was copied, or the page is being blocked. Paste the full URL into a normal browser on the OBS machine first — if it renders there, OBS will render it too.

The number is frozen. Either the source was shut down while hidden, or the page was loaded from a cached copy. Toggle the source off and on, or right-click the source and refresh.

The phone changes nothing. The controller and the display must be in the same room. If you regenerated the link, the old URL in OBS points at the previous room — re-paste the new display link.

None of these are subtle; all three are visible in under a minute if you test before the service rather than during it.

A note on the “right” number to show

OBS makes it tempting to show everything: countdown, segment name, next item, a message ticker. Resist at least half of it. The congregation needs one number; the stage team needs the segment context. If both are on the same screen, the number should dominate and everything else should be small.

The display page is built with that hierarchy already — large remaining time, small supporting labels. If you need something different, the widget URL is the simpler building block: one number, your choice of theme colour and language.

Build a service agenda first

Load the church service template, then paste its display link into OBS.

Open the service template