Does it handle daylight saving correctly?
For any normal time, yes. The offset for each zone is recomputed for the specific instant you are converting, using the IANA rules that ship with your browser, so a July meeting and a January meeting in the same city convert differently. The one place to be careful is a wall time that falls inside a DST transition, which is either nonexistent or ambiguous by definition.
What happens if I enter a time inside the DST changeover hour?
The converter resolves it by taking a single offset correction, which means it silently picks one of the two possible interpretations rather than asking you. In practice you get a valid result, but it may not be the one you meant. The real fix is not to schedule anything in the hour a country shifts its clocks, which is why airlines and calendars avoid it too.
How do I copy the whole conversion out?
Copy result puts one line per target zone on your clipboard, in the format "New York: Oct 14, 2026 09:30 (UTC-04:00)". That is a paste-ready block for a meeting invite or a Slack message, and it includes the offset so nobody has to guess.
Which zone should I use as the source?
Whichever city the time was quoted in. If a colleague says "3pm my time" and they are in Berlin, set the source zone to Berlin and type 15:00. Converting from your own zone when the time was quoted in theirs is the single most common way to end up an hour off.
Is any of this sent to a server?
No. Both the offset calculation and the formatting use the Intl APIs built into your browser, which include the IANA time-zone database. There is no API call, so the converter also works with the network off.
My city is not in the list. What do I do?
Pick any listed city that shares its offset and daylight-saving rules, and the times will be identical. The picker holds 44 curated zones plus UTC rather than the full IANA database of several hundred, and there is no free-text search, so for an unusual zone choose the nearest listed city that follows the same rules.
Does it show seconds?
The target rows display hours, minutes, and seconds on a 24-hour clock, but the input only accepts hours and minutes, because it is a standard datetime-local field. So you can read a seconds figure, you just cannot set one. For second-level work on log timestamps, an epoch converter is the right tool.
Do my chosen cities stay next time I open the page?
No. The board resets to your detected source zone and the three default targets on every reload. There is no local storage and no account, so nothing about where you are or who you work with is retained between visits.
Is it free?
Yes, free with no signup and no limit on how many target zones you add. Everything is computed by your browser, so there is no quota to hit and no server cost to pass on.
How accurate are the offsets?
As accurate as the time-zone database shipped with your browser and operating system, which is where the IANA rules live. That is normally current, but a very old, unpatched device can carry stale rules for a country that has recently changed its daylight-saving policy, and no page-level tool can correct for that.