vMix already knows how to render a web page as an input. That makes a live countdown one of the cheapest upgrades you can make to a service production: no extra hardware, no new operator workflow, and the number stays under phone control.
vMix's input types are built around sources: cameras, NDI feeds, video files, and web pages. A countdown is not video and not hardware — it is a live web page that updates every second. Treating it as a web input means vMix handles the compositing you already understand (layer, position, scale, transition) while Castimer handles the timekeeping.
The practical benefit: you never encode a countdown into a video file, and you never have to re-export anything when the service length changes. You change a number on a phone and the input follows.
Agenda display URL — https://castimer.com/event-timer/display?room=YOUR-ROOM. Use this when the screen should follow a full service flow: welcome, worship set, scripture reading, sermon, response, offering, benediction. The room code is the link between what your phone controls and what vMix renders.
Widget URL — https://castimer.com/widget?type=event&title=Service&date=.... Use this for a single countdown to a fixed moment: the pre-service clock, a five-minute warning before the stream goes live, a Christmas Eve service countdown.
The widget accepts theme (light or dark), color, lang, tz, and show_brand. Two of those matter here: pick theme=dark if the countdown will sit over dark stage footage, and set the correct tz so the countdown matches local service time instead of UTC.
In vMix, add an input and choose the Web Browser type. Paste the Castimer URL into the URL field and give the input a name you will recognise at 10:25 on Sunday — “Service Countdown” is better than “Web 3”.
Set the input resolution to match your production. For a 1080p workflow that is 1920×1080. If you let the input default to a small size and scale it up in a layer, the digits will be interpolated and look soft on a large screen — the number is the one element in the frame that must be razor sharp.
Then treat it like any other input: overlay it as a layer, use a fade transition, and set it to appear on the programme output when you need it. Because it is an input, you can also put it in a multi-view preview so the operator sees the number without putting it on air.
Full-frame countdown. The input fills the programme output. This is the pre-service pattern: ten minutes of a large number, then a clean cut to the room when the service begins. Nothing competes with the digits.
Corner or lower-third overlay. Scale the input down and position it over the camera or presentation feed. Keep the number tall enough to read — at 1080p, 120 pixels or more — and leave it in the same corner for the whole service, because a number that moves is a number people stop trusting.
Avoid the middle ground where the countdown is big enough to notice but too small to read. That is worse than no overlay: the congregation sees something changing and can't tell what it says.
With the display URL and a room code, the vMix operator only manages video. The countdown is driven by whoever holds the controller: start at the top of the service, advance at each transition, add a minute when the preacher signals for one.
This separation is not cosmetic. In most small productions the same volunteer runs vMix and watches the room. If advancing the timer required touching vMix, one of those two jobs would get dropped. With a phone controller, the operator's screen never changes — the input just keeps up.
If a second venue needs its own countdown, use a different room code. Rooms are isolated, so two services never fight over the same numbers.
Blank input: open the same URL in a browser on the vMix machine. If it loads there, re-check that you pasted the full URL including the query string.
Countdown not advancing: the page may have been loaded before the controller started. Refresh the input; the display reconnects to the room automatically.
Wrong time: the date is being interpreted in a different timezone. Add or fix the tz parameter.
Soft digits: the input resolution doesn't match the canvas. Set both to 1920×1080.
One habit that prevents all four: build the input on Saturday, run it for five minutes, and confirm the phone changes show up in the programme output — not just the preview.
Load the church service template to get a room-based display link, or build a widget URL for a fixed-time countdown.
Open the service template