Time & DatesDST-aware

Time Zone Converter & Meeting Planner

Pick a date and time in one city and read it instantly in four others. Daylight saving transitions are handled by your browser's own time zone database, so summer and winter offsets are always current.

Source Moment

Everything below is the same instant, shown in different places.

SOURCE TIME
City 1
City 2
City 3
UTC
Your device
A +1 or −1 next to a time means the date rolls over in that city — the single most common cause of a meeting invite landing a day out.
Share & embed

Offsets are not fixed, and that is the whole problem

Most time zone mistakes come from treating an offset as a constant. New York is not "UTC−5"; it is UTC−5 in winter and UTC−4 in summer. London is not always UTC; it is UTC+1 from late March to late October. The gap between London and New York happens to stay at five hours most of the year — but for roughly two weeks each spring and autumn the two regions switch on different dates and the gap becomes four or six hours. Meetings booked during those windows are the ones that go wrong.

This converter never hard-codes an offset. It asks your browser's own IANA time zone database for the offset that applied on the specific date you entered, so a meeting three months out is converted with the rules that will be in force then, not the rules in force today.

Places that do not shift at all

Singapore, Dubai, Mumbai, Ho Chi Minh City, Tokyo and most of Asia do not observe daylight saving. Their offset is stable all year, which means the gap to Europe and North America changes twice a year purely because the other end moved. If you schedule a recurring call between Singapore and London, it will drift by an hour twice a year unless you re-anchor it.

Half-hour and quarter-hour zones

India is UTC+5:30, Nepal is UTC+5:45, and parts of Australia sit on UTC+9:30 or +10:30. Any mental arithmetic that assumes whole hours will be thirty or forty-five minutes out for a significant share of the world's population. Reading the converted time directly avoids the issue.

Booking a meeting people can actually attend

Once you have the converted times, sanity-check them against working hours rather than just the clock. A 09:00 New York start is 22:00 in Singapore and 23:00 in Sydney. Spreading the inconvenience — rotating which region takes the awkward slot — tends to survive longer than a fixed time that quietly excludes one office.

Frequently Asked Questions

Does this handle daylight saving time?
Yes. The conversion uses your browser's IANA time zone database and looks up the offset that applies on the exact date you entered, so a meeting scheduled months ahead is converted with the rules that will be in force then.
Why does the gap between two cities change during the year?
Regions switch to and from daylight saving on different dates, and many places never switch at all. For a week or two each spring and autumn the usual gap is an hour larger or smaller, which is when most scheduling mistakes happen.
What does the +1 or −1 beside a time mean?
It means the date is different in that city. A Monday evening meeting in New York can be Tuesday morning in Singapore, and missing that rollover is the most common reason an invite lands on the wrong day.
Are half-hour time zones supported?
Yes. India at UTC+5:30, Nepal at UTC+5:45 and the Australian central zones are converted exactly, so there is no need to round to the nearest hour.