Install it
- 1Open the TimedFlow Stage Timer listing and choose Add to Chrome.
- 2Pin it to the toolbar so it is always one click away.
- 3Click the icon to open the launcher, or Browse templates to open the side panel.
Without an account
Everything below works signed out, offline, with nothing to set up. This is the fastest way to put a countdown on a screen.
- All 54 timer templates — Pomodoro, TED talk, church service, wedding ceremony and the rest.
- A custom timer: one duration, or a rundown you build row by row.
- The stage window, for a second screen or a projector.
Signing in
Signing in connects the extension to your rooms. You never type a password into the extension: choosing Sign in opens timedflow.com, you sign in there the normal way — email or Google — and approve the connection once. The extension remembers it across browser restarts.
Signing out of the extension only signs out the extension. A timedflow.com tab you have open stays signed in.
Driving a show
With an account connected, My rooms lists the rooms you own. Opening one gives you a controller in the side panel: start and pause, next, reset, nudge the clock, blackout the stage, and flash a message to your presenter. It stays in sync with timedflow.com within about a second, in both directions.
What it deliberately cannot do
The extension drives a show. It does not author or review one — that stays on the website, where there is room to do it properly.
- Creating, editing, reordering or deleting timers.
- Themes, branding, PINs and scheduling.
- Activity log, session insights, CSV import and the moderator queue.
Every one of those is one click away: the controller links straight back to the room on timedflow.com.
If something looks wrong
- The side panel will not open. Chrome only allows it directly from a click. Press the button again rather than reopening the popup first.
- Times look stale. The panel shows a reconnecting notice when live updates drop; it falls back to polling and catches up on its own.
- A timer kept running while the panel was closed. That is intended. Timers are anchored to a timestamp rather than counted in the panel, so closing it, minimising Chrome or restarting the browser all leave the clock correct.