Proclaim Integration Guide

A Countdown Beside Proclaim
Two Setups That Work

Proclaim is built to carry the presentation: lyrics, slides, scripture, media. Adding a live countdown to that mix is possible, but the cleanest setups don't touch Proclaim at all — they put the number on a layer of its own.

First, be honest about the constraint

Proclaim is a presentation application, not a compositing tool. Its outputs are slides, media, and the items you build inside the presentation. Whatever countdown you want on screen has to exist either as an item Proclaim itself renders, or as something outside Proclaim that the projector or switcher sees instead.

Proclaim does have built-in timer capabilities in current versions, and if a static countdown to a fixed time is all you need, using the tool you already own is the simplest answer. Menu locations differ between versions, so check your version's documentation rather than a blog post — including this one.

What Proclaim's built-in timers do not give you is phone control, per-segment service agendas, or a countdown that keeps running independently of the presentation operator. Those are the cases where a separate layer earns its place. Here are the two setups that hold up on a Sunday.

Setup A — a second display (simplest, most reliable)

If your projection computer already drives two screens, this is the zero-risk option. The projector keeps showing Proclaim. A second screen — a confidence monitor, a stage TV, or a small display facing the platform — shows only the countdown.

Steps are minimal. Open a Castimer countdown on that second screen and press full-screen. Set the duration for the sermon or for the pre-service window. Control it from a phone: start, pause, add a minute.

The advantage is isolation. Nothing you do in Proclaim can hide the countdown, and nothing in the countdown can appear on the congregation's screen by accident. The trade-off is that the congregation doesn't see it either — the timer is for the platform, which is usually exactly what a preacher actually needs.

Open the Castimer timer on that machine once, and leave the tab open between services.

Setup B — capture the countdown into your video layer

When the countdown has to appear on the same screen as the presentation — for a stream, or for a congregation-facing countdown that sits over the camera — the practical route is to composite it outside Proclaim and feed the result in.

Concretely: run a browser window with the Castimer display URL, capture it (OBS browser source is the most direct method — full walkthrough in the OBS guide), and use that composited output as the video source your projector or streaming software shows. Proclaim stays the lyrics machine; the countdown rides on top of the video.

This adds one piece of software to the chain, so it needs a rehearsal. Do it once on a Saturday, not at 10:20 on Sunday. The failure mode to watch for is a resolution mismatch: capture at 1920×1080 and keep everything downstream at 1080p, or the digits will look soft.

Building the right URL for a service

Two URL shapes cover almost every church use. For a countdown to a fixed moment — the start of the service, midnight on Christmas Eve — use the widget with an ISO date:

https://castimer.com/widget?type=event&title=Service&date=2026-11-22T10:30:00&tz=America/New_York&theme=dark&show_brand=0

For an agenda-driven service — where the number changes as you move from worship to sermon to response — use the display link instead: /event-timer/display?room=YOUR-ROOM. The room code is what lets your phone drive the screen.

The widget supports theme, lang, tz, and show_brand; set show_brand=0 for a clean projector frame. Timezone matters more than people expect — a countdown built in UTC will be hours off in a local sanctuary.

Pre-service countdown, then the service agenda

The common Sunday pattern is two different timers in sequence, and they should not be the same object.

Ten minutes before the service, the screen shows a countdown to 10:30. It creates urgency in the room without anyone announcing anything. When the service starts, that countdown is irrelevant — what matters now is the worship set length, the sermon slot, the transition into response.

Build the first as a widget with a fixed date. Build the second with the church service template — seven segments, editable durations, auto-advance off by default so you stay in control of transitions. Switching between them is a scene or input change, not a reconfiguration.

What to rehearse before Sunday

Four things, in this order. Confirm the countdown renders on the actual projector — not the laptop screen. Confirm the phone can control it from where the preacher stands (sanctuary Wi-Fi is often worse than the office). Confirm what the screen shows at 00:00, because that is the frame everyone will remember if it goes wrong. And confirm the fallback: if the countdown layer dies mid-service, who switches back to Proclaim, and how long does it take.

A timer that fails silently is worse than no timer, because the stage team keeps trusting a frozen number. The rehearsal is what makes the number trustworthy.

Set up the countdown you actually need

A single sermon countdown, or a full service agenda with seven segments — both free, both phone-controlled.

Start a countdown