Time zone converter
See one moment written out in every major zone at once.
- Runs in your browser — nothing you enter is uploaded
- No sign-up, no quotas, free to use as often as you like
How it works
Scheduling across time zones goes wrong because of daylight saving, which starts and ends on different dates in different hemispheres, and not at all in some countries. Converting a specific date rather than an offset is the only reliable way to get it right.
Daylight saving is handled by date
Your browser holds the full time zone database, so a time in June and the same time in December convert differently where daylight saving applies. This is why converting by fixed offset — “they are five hours ahead” — fails twice a year.
Enter the date as well as the time
A time on its own cannot be converted correctly, because the offset depends on the date. Leave the box empty to convert the present moment instead.
Zones that do not shift
India, most of Africa and much of Asia do not observe daylight saving, so the gap between them and Europe or North America changes twice a year even though nothing changed locally. This is the usual cause of a meeting being an hour out.
The day can change
Converting between, say, Los Angeles and Sydney frequently lands on a different calendar day, so the weekday and date are shown alongside each time rather than the clock alone.
Time zone converter — questions
Does it handle daylight saving?
Yes. Conversion uses the full time zone database for the specific date you enter, not a fixed offset.
Why do I need to enter a date?
Because the offset between two zones depends on the date. Leave it empty to use the present moment.
Why is the day different?
Large time differences frequently cross midnight, so the weekday and date are shown with each time.