Time Zone Finder
Compare two time zones: the current local time in each, the offset difference, and the hours that suit both ends.
Two zones, one clock
Pick two zones. The page reads each one's current offset with Intl.DateTimeFormat, shows the local time and date in both, states the difference in hours and minutes, and lays out twenty-four hours of the first zone beside the matching clock time in the second. A cell is highlighted when both zones read between 09:00 and 18:00, which is the row to look at before proposing a call.
The zone list comes from Intl.supportedValuesOf('timeZone') and the offsets from the browser's own Intl data, so no timezone database file is downloaded and no request is made. A browser without that method gets a short built-in list and a line on the page saying so. Offsets are read for the instant shown, so a pair whose gap changes at a daylight-saving transition reports today's difference only, and public holidays are not modelled.
The clock runs until you stop it, and stopping it clears the interval. The two zones live in this tab; nothing is uploaded and nothing is stored.
Compare two time zones: the current offset and local time in each, the difference between them, a live clock and a meeting planner over the coming hours.
Offsets come from the browser's Intl data rather than a downloaded database, and the planner highlights the hours that fall between 09:00 and 18:00 in both zones.
How to use it
Pick the two zones. Each panel prints the offset now and the local time, the difference is stated once, and the clock runs only while the button says Stop the clock — stopping it clears the interval.
Reading the planner
Each cell is one hour that starts at that clock time in the first zone, with the second zone's time beside it. A cell is highlighted when both zones read between 09:00 and 18:00 at that moment, and the page states when there is no overlap at all.
Where it stops
Two zones, today's offsets and no calendar integration. Daylight saving comes from the browser's Intl data, so a zone whose rules changed in a browser update reads differently, and nothing is stored after a reload.
What to Expect
Best for
- finding a call window that suits two places
- checking the offset difference before booking
What this tool keeps
- The zones and the clock live in this tab; a reload resets them and nothing is uploaded.
Frequently asked questions
Where do the offsets come from?
From the browser's Intl.DateTimeFormat data and its zone list, so daylight saving follows that data rather than a fixed offset typed into the page.
What does a highlighted cell mean?
That both zones read between 09:00 and 18:00 at that hour in the first zone. The page also says when no hour in the plan overlaps at all.
Does the clock keep running?
Only while the button says Stop the clock. Stopping it clears the interval, and reloading resets both zones.
Build custom tools for your store
Join the SDK program to create useful ecommerce utilities for your store.