NO SIGNUP · NO SERVER
THE LINK IS THE SYNC
Shared timer, synced by link

One timer. Every screen. In sync.

Copy the link, send it anywhere — everyone who opens it counts down to the same instant. No server, no signup.

For classrooms, exams, webinars, workshops, standups, game nights and auctions.

00servers to run this
Anyone opening your link right now sees exactly this.

Set your countdown

Quick timer, or count down to a moment on the clock — both produce a shareable link.

Why doesn't CountLink limit viewers like competitors do?

Real-time competitors like ShareMyTimer and Stagetimer push live control changes to every open viewer, which needs a server holding a connection open per viewer — that cost is why their free tiers cap devices and timers. CountLink works differently: the countdown's end time is written into the link itself, so each device just checks its own clock against that timestamp. No ongoing connection, no per-viewer cost, no reason to cap viewers.

Common questions

Is CountLink free?

Yes — no viewer limit, no device limit, no paid tier. Syncing happens in the link itself, so one more viewer costs nothing.

Do I need to sign up or make an account?

No. Nobody — neither the person who starts the timer nor anyone who opens the shared link — ever needs an account.

How does the timer stay in sync across devices?

The countdown's end time is a timestamp written into the shared link, not stored on a server. Every device that opens the link counts down to that same timestamp using its own clock.

Can the timer go down or lose sync if a server has an outage?

No — there's no server in the sync path, so there's nothing to go down. Each device does its own local math against the shared timestamp.

Can I pause or extend a countdown that's already running?

Not live, for everyone already viewing — there's no ongoing connection to push a change through. If plans change, start a fresh countdown and re-share the new link.

What if two people's device clocks are slightly different?

Accuracy depends on each device's own clock, typically within a second. The countdown itself doesn't drift — any difference you see comes from the devices' clocks, not from CountLink.