T1 · T2 · T3
Subs
Tier 1, 2 and 3, and gifted subs. Each tier carries its own amount, so a tier 3 can be worth more than three tier 1s if you want it to be.
You set what a sub is worth and what a thousand bits is worth. The clock counts down, an event lands, the number goes up, and everyone watching sees it happen.
No account to start. Free covers the base clock with subs and bits.
28:41:48
That is the whole mechanic, and the reason a subathon clock belongs on screen rather than in a spreadsheet. An event arrives, the clock jumps, and the alert and the number read as one thing.
Sample settings. You choose every one of these values.
Four controls, each there because a long event needs it.
T1 · T2 · T3
Tier 1, 2 and 3, and gifted subs. Each tier carries its own amount, so a tier 3 can be worth more than three tier 1s if you want it to be.
1,000 bits
Counted by the thousand. A thousand bits is one amount and the clock scales the rest from it.
41:07 paused
Stops the count without losing it. You come back to the number you left, not to a guess.
MAX 72:00
An upper bound, so a good night does not turn into a four-day stream you did not agree to.
They are cheap to farm, and a follow bot would run the timer away. The default says so and the setting explains it.
So a clock that only counts bits is a valid setup, not a workaround.
The pause is a real stop and not a reset. That matters most when you are tired.
Nothing to install and nothing to update mid-event. Resizing the browser source does not reload it.
Three things people ask at hour two, answered before hour one.
Subs and bits. Tier 1, 2 and 3, gifted subs, and bits by the thousand. You set an amount for each, and anything left at zero is ignored.
Tips and the other event sources are on the Pro side of the line. They are decided and not finished.
In an OBS browser source at whatever size you want, and in a normal browser tab if you would rather watch it on a second screen.
You can cap the clock, and you can pause it without losing the count. Both exist because a subathon that runs away from its host is the common failure.
The clock as it works now is the free tier. Pro adds sources and styles; it does not take any of this away.
The same three as every other tool here.
It loads with amounts already set, and you change the ones you care about.
About a minute, with no account and no card.
One URL, belonging to your stream and nobody else's.
Treat it like a key. Anyone with the link can load the clock.
Add a browser source, drop the link in, size it on the scene.
The tool reports back once the source loads it.
Everything the clock does today is in the free column. The Pro cells say what is finished.
| Feature | Free | Pro |
|---|---|---|
| The clock in an OBS browser source | ||
| Subs: tier 1, 2, 3 and gifted | ||
| Bits, by the thousand | ||
| Set what each source is worth | ||
| Pause without losing the count | ||
| Cap the clock | ||
| Base clock style | ||
| Tips and the other event sources | In development | |
| Extra clock styles | In development | |
| Account needed | No | Yes |
It is a normal web page, so anything that can load a URL in a browser source should run it. OBS is the one it is built and tested against, so that is the one this page claims.
The browser source in OBS is a separate load, so closing your own tab does not take the overlay down.
Each link is its own clock, so two links are two clocks. A collab timer that stays in step across channels is a Pro idea and is not built.
No. What the clock does today is what the free column lists, and Pro is additive.
It takes about two minutes, it costs nothing, and you can throw it away afterwards.