When does the countdown roll over?

At local midnight in the timezone you select. If no timezone is set, the browser's local zone is used.

Can I countdown to a past date?

Yes. Past dates show a negative count and the "days since" framing, which is useful for tracking anniversaries or build ages.

How precise is the live timer?

It refreshes once per second from your device's clock, accurate to within whatever your system clock is synced to (usually 50–500 ms via NTP).

Is my target date saved on a server?

No. The target is stored only in the URL or local storage of your browser; nothing is uploaded.

countdown · live · days · hours · minutes

Live countdown to any date

Ticks once per second so days, hours, minutes, and seconds all update in real time. Handles past dates as elapsed time.

Quick Start

How the countdown ticks

Every second, we read Date.now() again and recompute the difference. Past dates flip to "time elapsed" with the same display.

01
Pick a target
Future = countdown. Past = elapsed. Use the +30 days shortcut to try it.
Parsing accepts ISO 8601, RFC 3339, RFC 2822, and Unix epoch seconds/milliseconds. The Date constructor handles the rest with browser-engine consistency.
inputISO 8601RFC 3339epochlive
target · timestampdt · ISO
```
2027-01-01T00:00
```
loaded · ISO 8601zone · ready
02
Compute diff
Target - now in ms, then break into days, hours, minutes, seconds.
All math runs in UTC internally to avoid DST landmines; presentation converts back to the user’s zone via Intl.DateTimeFormat.
mathUTC mathIntlDST-safelive
Δ · optionsms · live
```
(t - now)
```
options applied · UTCDST-safe
03
Tick once a second
The seconds field reflects every refresh of the timer.
Output respects the chosen timezone offset (Z vs +05:30) and pads digits per ISO conventions so sorts stay chronological.
liveoffsetzone-awaresortablepadded
tick · computed1s · ready
```
setInterval
```
computed · instantsortable
04
Copy or share
Click copy to grab "Xd Yh Zm" — handy for share-the-countdown moments.
Copy writes via the Async Clipboard API; nothing pings a time server — the browser’s clock is the only oracle.
shareclipboardno oracledeterministicclient-side
✓ · copiedready · done
```
✓ Copied
```
shipped · ready to shipsuccess

Pro tips

Time math without DST landmines

Always store UTC

Convert to local for display only. UTC storage avoids DST jumps and timezone drift in databases.

Watch leap seconds

POSIX time doesn’t count leap seconds; some systems do. Don’t use timestamps for sub-second precision across boundaries.

Prefer Temporal eventually

The Date API has many quirks. Temporal is shipping in modern engines and handles zones correctly.

Cron is timezone-tricky

Cron expressions run in the daemon’s local zone unless told otherwise. Pin a TZ explicitly for predictable runs.

ISO 8601 sorts naturally

YYYY-MM-DDTHH:mm:ss sorts correctly as a string. Don’t use US-style MM/DD/YYYY for anything machine-readable.

Beware Y2K38

Signed 32-bit Unix timestamps overflow in 2038. Use 64-bit storage end-to-end for long-lived systems.

Use Cases

When to count down

Launches, deadlines, birthdays.

Product launch

Days/hours until go-live for a status page. Math runs in UTC under the hood to dodge DST jumps — local time is only for display. That means scheduling logic and date diffs survive March / November fall-back without the classic off-by-one-hour bug.

DST-safe

Conference

Speakers love a countdown to their talk slot. Browser clock is the only source — no external time server, no privacy leak, no rate limit. Pair with NTP-synced server time for high-accuracy use cases, but for human-scale work the browser clock is plenty.

UTC-correct

Birthdays

Lighter use: when's grandma's 80th? ISO 8601 output sorts naturally as strings, perfect for filenames (report-2026-01-15.pdf) and log lines that need chronological ordering without parsing. Drop into S3 keys for free time-bucketing.

ISO-sortable

Certificate expiry

Days until a TLS / domain renewal is due. Pairs cleanly with cron, scheduled tasks, and timestamped log analysis. The tool's output drops directly into APScheduler, Linux cron, or GitHub Actions schedule expressions without re-formatting.

spec-grade

Sprint end

Seconds tick under a kanban board. Output respects the chosen timezone offset (Z vs +05:30) so REST APIs and database TIMESTAMP WITH TIME ZONE columns round-trip cleanly. No ambiguity between "noon UTC" and "noon local".

zone-aware

Holidays

Days until the next bank holiday in any country. Confirms the difference between epoch seconds (10 digits) and milliseconds (13 digits) before you commit code that mis-multiplies by 1000 — a classic bug in cross-language time handling.

epoch-accurate

FAQ

Frequently asked questions

Why seconds in remainder, not total?

Total seconds would be billions for far-future dates. The remainder makes the digit-roll satisfying without overflow.

What if I pick a past date?

It flips to 'time elapsed'. The same numbers tick upward (well, the seconds will roll).

Tab in background?

Browsers throttle setInterval in background tabs — counters may pause and jump when you return.

Time zones?

The datetime-local picker uses your browser's local timezone. The countdown is to that exact wall-clock time in your tz.

Is anything sent to a server?

No — the countdown runs locally in your browser tab.

Suggest a tool

Something missing?

Tell us what you need. We ship the top requests every two weeks.

47 in queue·8 shipped this month

Request queued. Thanks!