One moment to look forward to, wherever you are.
Examples & helpTarget instant:
The target uses the selected named time zone and its rules in your browser. Skipped times are rejected; repeated times require an explicit choice. The remaining duration is recalculated from your device clock on every update and when you return to this tab. Days mean 24 elapsed hours. Device clock accuracy matters.
Open an explicitly created share link to restore the countdown after reloading. Birth dates from the age tool are never added to countdown links.
A countdown needs a specific moment, not just a calendar day. Set the event’s date, clock time and named time zone so people in different places can count toward the same instant.
These examples use fixed moments. A running countdown uses your device’s current clock, so its remaining time keeps changing.
This is 05:00 UTC on 1 January. Midnight UTC would be a different target, five hours earlier. People opening the shared countdown count toward the same instant.
The clock moves forward during this interval. The countdown shows elapsed time in 24-hour days, while the days-between-dates calculator would report one calendar day.
The countdown measures elapsed seconds and groups them into 24-hour days. Calendar-day counting follows date boundaries. Daylight saving and the target time of day can make those totals differ.
Yes, when they open the optional share link. The link stores a resolved target instant and the event’s zone. Keep your device clock accurate, since each browser uses its own current time to show what remains.
The event title, target instant and zone are readable in the URL fragment. Use a title you are comfortable sharing. Countdown details stay in the page unless you deliberately create a link.