ProTimer


ProTimer — Free Download. Live production timer

ProTimer is a free timer and rundown application for conferences, livestreams, church services and other live productions. It provides countdown, stopwatch and clock modes, a multi-cue rundown with planned times, speaker messages, lower thirds, and clean frameless timer windows that can be placed on stage displays, audience screens or OBS overlays. The operator control panel stays centred and readable while separate output windows are moved, resized or sent to fullscreen on any connected monitor. The application runs on macOS and Windows, supports Bitfocus Companion, OSC, HTTP API, QR phone remotes and multiple local outputs without requiring a cloud account.

5.0(1 ratings)
File size: 105 MB
The latest version of ProTimer is: 2.1.0
Operating system: Windows, Mac OS
Languages: English, Serbian
Price: $0.00 USD (Open Source (MIT))
  • Countdown, stopwatch and clock. Three core timer modes are available in the same interface. Countdown runs from a set duration to zero with configurable color thresholds that shift from white to yellow to red as time runs out, then flash at zero and continue into overtime. Stopwatch counts upward for sessions that need elapsed time. Clock mode displays the current system time, and a fourth option allows counting down to an exact future time such as a scheduled broadcast start. All modes keep the same large readable preview in the control window.
  • Rundown with planned times. A full run of show can be built as a list of cues. Each cue holds its own duration, title and planned start time. The rundown view shows the current cue, the next cue and an over/under indicator that compares planned times against actual progress. A single START RUNDOWN button launches the first cue and subsequent cues can be triggered in order. Long rundown lists scroll at a fixed row height instead of compressing entries.
  • Frameless audience output. The stage or audience window renders only the timer with no borders, toolbars or operator controls. The window can be dragged and resized directly with the mouse, placed into an exact grid cell on a monitor, or pushed to fullscreen from the control panel. Fullscreen control is deliberately separated from window movement to prevent accidental changes during a live show.
  • OBS Browser Source overlay. A transparent output mode is designed for OBS Studio. The timer is added as a Browser Source so the countdown appears cleanly over existing video content without a background rectangle. NDI routing is possible through OBS when the overlay is included in a scene that uses NDI output tools.
  • Phone remote and QR codes. Operator phones can control the timer over the local Wi-Fi network through a control token. The audience output can show a scannable view-only QR code that opens a timer page on phones. The phone view uses host-clock synchronisation so the displayed time matches the main timer without drift caused by phone clock differences. Share Online exists as a beta tunnel, while LAN and QR remain the recommended path for show-critical viewing.
  • Speaker messages and lower thirds. Text messages can be prepared in advance and sent to the audience output during a live event. Lower third overlays display speaker names, session titles or other short text lines over the timer or over a separate screen. These messages are triggered from the control panel and appear without interrupting the running timer or rundown progression.
  • Color thresholds and overtime. Countdown timers can be configured with warning zones. A typical setup starts white, shifts to yellow at a set remaining time, then red closer to zero. At zero the display flashes and overtime is counted upward in a visually distinct format. Threshold values are set once and apply consistently across all countdown cues in the rundown.
  • Grid placement. Output windows can be assigned to predefined grid cells on any connected monitor. This is used when a single screen shows multiple elements such as timer, lower third and backstage view simultaneously. The operator preview in the control window remains centred and unaffected by grid placement of the real output.
  • Bitfocus Companion integration. A packaged Companion module provides named actions, presets, variables and live feedback for Stream Deck hardware. Operators can start, stop, reset, load cues and trigger messages from physical buttons. Variables expose current timer state, remaining time and active cue for feedback displays on the Stream Deck keys.
  • OSC and HTTP API. OSC input is supported from QLab, TouchOSC and other production tools. A local HTTP GET API allows scripts and external systems to control the timer and rundown. Both methods operate on the local network and do not require cloud connectivity or online accounts.
  • Backstage view. A separate backstage output shows NOW and NEXT cue information for speakers, stage managers and crew. This view can be placed on a monitor away from the audience and paired with its own QR code for phone viewing. The backstage view remains synchronised with the main rundown without showing operator controls.
  • Multiple local outputs. ProTimer can drive several output windows at once: a clean audience timer, a backstage display, a lower third overlay for OBS and a phone-accessible view. Each output is managed independently from the control panel, allowing a single operator to run the entire production timer setup from one computer.

ProTimer was created by Srdjan Kotarlic and first released as a public project in 2023. The application is written in HTML, CSS and JavaScript, packaged as a desktop application for macOS and Windows. Development has been driven by direct use in live production environments, with releases shaped by operator feedback from conferences, church services and livestream events. The current build focuses on a centred operator preview, a unified duration picker, fixed-height rundown rows and safe frameless output handling. Builds are not code-signed, so Windows SmartScreen may show an unknown publisher warning and macOS Gatekeeper may require opening the app through System Settings after confirming the source. The project does not rely on cloud services for core operation; all timer, rundown and remote functions work over the local network.