Time Zone Converter
See one moment in several time zones at once.
About this tool
Pick a date, time and time zone and see the same moment in every other zone you care about, with offsets and day changes. Handy for scheduling across teams and reading log timestamps.
How to use it
- Pick a date, a time and the time zone that time is in.
- See the same moment in every zone on your list, with offsets and day changes.
- Add or remove time zones; your list is remembered in this browser.
Questions
- Does it handle daylight saving time?
- Yes. It uses your browser’s up-to-date time zone database, so offsets are correct for the chosen date, including the days when clocks change.
- What is the difference between UTC and GMT?
- For everyday purposes they show the same time. UTC is the precise scientific standard; GMT is a time zone used in the UK in winter. Servers and logs should use UTC.
- Why are some rows dimmed?
- Rows where the time falls between 22:00 and 07:00 are dimmed, which makes it easier to spot a meeting time that works for everyone.
- What time zone should servers and databases use?
- UTC. Set servers to UTC, store timestamps in UTC or in a zone-aware type such as timestamptz in PostgreSQL, and convert to local time only when displaying. Logs in UTC sort correctly and never contain a repeated or missing hour around daylight saving changes.
- What happens to times that don’t exist during a clock change?
- When clocks spring forward, an hour is skipped: in Berlin on 29 March 2026, 02:30 never happens. When they fall back, an hour repeats, so 02:30 happens twice. Software has to pick an interpretation for these times, so avoid scheduling jobs or meetings inside that hour.
- Why do some time zones have 30 or 45 minute offsets?
- Offsets are set by governments, not by geography alone. India uses UTC+05:30, Iran UTC+03:30, Newfoundland UTC−03:30, Nepal UTC+05:45 and New Zealand’s Chatham Islands UTC+12:45. Converters that assume whole-hour offsets get these places wrong, which is why using IANA zone names matters.
How to convert time between time zones
Converting a time between zones takes two steps: turn the local time into one exact instant, then show that instant in the other zones. 09:00 in New York on 15 March 2026 is 13:00 UTC, because New York is already on daylight saving time (UTC−04:00) by then. On 1 March the same 09:00 would be 14:00 UTC. Pick a date, time and source zone here, and every row shows the same moment.
The date matters as much as the time, because offsets change during the year and a conversion can cross midnight. When it does, the row shows +1 day or −1 day next to the date. Tokyo is ahead of the Americas, so an afternoon call in San Francisco is already the next morning there. Copy a row to get a value like 2026-03-15 13:00 UTC for a calendar invite or chat.
Time zone names vs abbreviations: why use Europe/Berlin
Names like Europe/Berlin and America/New_York are IANA time zone identifiers from the tz database that operating systems and browsers ship. Each one records the full history of a region’s offsets and daylight saving rules. Abbreviations don’t: CST can mean US Central, China Standard or Cuba Standard Time, and IST is used in India, Ireland and Israel. That ambiguity is why software should never rely on abbreviations.
A fixed offset like UTC+01:00 isn’t a time zone either. It is right for one instant but wrong for half the year in places with daylight saving. Store an IANA name when you need future local times, such as a weekly 09:00 meeting, and store UTC for events that already happened. This time zone converter lists every zone your browser supports and remembers your chosen list in this browser.
How to schedule a meeting across time zones
Start with the people who have the least overlap. Add their zones to the list, set a candidate time and look for a slot where no row is dimmed. Teams spanning Europe and the US West Coast often land on 08:00 or 09:00 in San Francisco, which is 17:00 or 18:00 in Berlin for most of the year. With Asia in the mix there is often no good slot, so rotate the inconvenient time.
Watch the weeks in March and in October or November when the US and Europe change their clocks on different dates. For those weeks the gap between New York and London is four hours instead of five, and a recurring meeting moves for one side. Check a date inside that window before sending the invite. For log timestamps, convert with the Unix Timestamp Converter first, then compare zones here.
Something not working, or a result looks wrong? Report a problem with this tool