About

The world's clock, following the sun.

timezone.io answers everyday time questions: what time it is somewhere else, when the clocks change, and when a meeting works for everyone. It also gives teams a shared board of everyone's local time, and developers an API with the same data.

From team app to time reference

The timezone.io domain began as a team app: a page that showed where your teammates were and what time it was for each of them. Links to those old team pages are still out there, and they now lead to our new team boards.

Team boards are back. Around them, timezone.io has grown into a reference for time zones, countries and cities, with an API for developers.

What you'll find here

The reference site

Current local time, UTC offsets and daylight saving dates for every time zone, country and major city, plus a converter for comparing two places.

Time zones →Countries →Converter →

Team boards

Create a team, share an invite link, and see everyone grouped by their local time. Teammates join without an account.

Make a team board →

The API

The same data as JSON: time zones, abbreviations, countries, cities and conversions, with a free API key.

API docs →Get an API key →

Data sources

Our time and place data comes from open, authoritative sources:

  • IANA Time Zone Database (tzdb) — the canonical source for time zone boundaries, offsets, and daylight saving rules. Our times are currently computed with release 2026e. iana.org/time-zones
  • GeoNames — city names, coordinates, and populations, licensed under CC BY 4.0. geonames.org

Editorial policy

We keep the facts and the writing apart, so each can be checked on its own terms.

  • Reference data comes from the sources. Current times, UTC offsets, abbreviations and daylight saving dates are computed from the IANA tz database (release 2026e). City names, coordinates and populations come from GeoNames.
  • Descriptions are AI-assisted, then checked. The descriptions, histories and FAQs on zone, country and city pages start as drafts written with the help of AI models. We check every factual claim in them (counts, offsets, dates and daylight saving rules) against our database and the tz database, and a person reviews them before they're published.
  • No claims that go stale. We avoid wording like “currently” or “next March” in written text. Anything that depends on today's date — the local time, whether daylight saving is in effect, the next clock change — is computed live instead.
  • Kept up to date. When governments change their clocks, the change reaches the tz database, and we update our data and any text it affects.

Spotted a mistake? Email [email protected] with the page and what's wrong, plus a source if you have one. We read every report and correct confirmed errors.

Get in touch

Questions about the API, team boards or our data, or just want to say hello? Contact us.