How this works
Rather than looking the answer up in a table that goes stale, this page reads your browser's own timezone database and searches forward for the next moment the UTC offset actually changes. That means it stays correct when a country amends its rules, and it works for every zone your browser knows about, not just a handful of popular ones. The countdown runs against the real clock, so you can leave the page open.
Why the dates move each year
Daylight saving transitions are defined by a rule rather than a fixed date — "the second Sunday in March", "the last Sunday in October" — so the calendar date shifts annually. Transitions are also scheduled in the small hours deliberately, when the fewest people are travelling, working shifts, or running scheduled jobs. That is why 2:00 a.m. is such a common changeover time.
The gap that does not exist, and the hour that happens twice
When clocks spring forward, an hour of local time simply never occurs. In the United States, 2:30 a.m. does not exist on the morning of the change — a meeting scheduled for it is not a valid local time. In autumn the reverse happens and an hour repeats, so 1:30 a.m. occurs twice, an hour apart. This is why software should store timestamps in UTC and convert for display: local time is genuinely ambiguous twice a year.
Not everywhere participates
Roughly a third of the world observes daylight saving, and the share has been falling. Most of Africa and Asia never adopted it, Russia abandoned it in 2014, Mexico scrapped it nationally in 2022, and Brazil dropped it in 2019. Within countries that do observe it, exceptions are common — Arizona and Hawaii in the United States, Queensland and Western Australia in Australia, Saskatchewan in Canada. The countries below each have their own page with the specifics.