How to Convert Time Zones Without Getting It Wrong (The Daylight Saving Trap)

I’ve missed exactly one client call in eight years of remote work, and it was because the client wrote “3 PM EST” in March, the week after the US had moved to daylight time but before the UK had. EST, it turned out, was not what they meant. That mistake taught me more about time zones than any explainer, so this article is the version I wish I’d read first: how the abbreviations mislead, how to convert without guessing, and how to write a meeting time that nobody can misread.

Why “EST” is usually wrong

Most people in New York say “EST” all year, but for eight months they are actually on EDT, one hour ahead. The same happens with PST/PDT, CET/CEST and BST/GMT. A time zone abbreviation names a fixed offset; a place uses two different ones across the year. So when someone writes “9 AM EST” in July, they mean 9 AM New York time, which is 9 AM EDT, which is 13:00 UTC, not the 14:00 UTC that “EST” literally says.

The fix is to think in locations, not abbreviations. “9 AM New York” is unambiguous on any date, because the converter can look up whether New York is on daylight time that day. That is what the Time Zone Converter does: pick a city on each side, pick the date, and it applies the correct offset for that day.

Advertisement

Daylight saving is where the errors live

Countries change their clocks on different dates, and some do not change at all:

• United States and Canada: second Sunday in March to first Sunday in November.
• UK and EU: last Sunday in March to last Sunday in October.
• Australia (most states): first Sunday in October to first Sunday in April, the opposite direction, because it is the southern hemisphere.
• No DST at all: Pakistan, India, China, Japan, most of Africa and South America, and Arizona in the US.

So the gap between Lahore and London is 4 hours in summer and 5 in winter, while Lahore to New York is 9 hours in summer and 10 in winter. And for roughly two weeks in March and one week in October, the US and Europe are out of step with each other, which is exactly when my call went wrong.

Converting by hand, if you must

1. Convert the source time to UTC by subtracting its current offset. New York in July is UTC−4, so 9 AM becomes 13:00 UTC.
2. Add the destination’s current offset. Lahore is UTC+5 all year, so 13:00 UTC becomes 18:00.
3. Check whether the date changed. Tokyo (UTC+9) at 13:00 UTC is 22:00 the same day; Auckland (UTC+12 or +13) is already tomorrow.

Step 1 is where hand conversion fails, because you have to know the current offset, and that means knowing the DST rules for that country on that date. A converter removes the guess.

How to write a time nobody can misread

After that missed call I settled on a format and have not had a problem since:

Thursday 18 September, 14:00 London (09:00 New York, 18:00 Lahore)

Three rules behind it:

1. Name cities, not zones. “London” is precise; “GMT” or “BST” invites someone to apply the wrong one.
2. Give the time in every participant’s city. It takes ten seconds with a converter and removes any need for the reader to do arithmetic.
3. Include the day and date. Near the date line, “Thursday” is a different day for some people.

If you send calendar invites, the calendar handles this automatically as long as your own time zone is set correctly. The trouble starts in email, chat and documents, where a written time is just text.

Scheduling across three or more zones

The realistic overlap between London, New York and Lahore is small: roughly 13:00–17:00 London, which is 08:00–12:00 New York and 17:00–21:00 Lahore. Adding Sydney kills it entirely; someone is always at 3 AM. Two approaches that work:

• Rotate the pain. Alternate meeting times so the early or late slot moves between teams.
• Go asynchronous. Record the update, decide in a document, reserve live calls for the things that genuinely need everyone present.

Frequently asked questions

What is the difference between GMT and UTC?

For scheduling, none; they are the same offset. Technically UTC is the atomic-clock standard and GMT is a time zone. The UK uses GMT in winter and BST (UTC+1) in summer, so “GMT” is not always the current London time.

Which countries do not use daylight saving time?

Most of Asia, Africa and South America, including Pakistan, India, China and Japan. Within the US, Arizona and Hawaii do not.

How do I convert a time for a date months away?

Use a converter that takes a date. The offset for a city can differ between today and a date three months from now if a DST change falls in between.

What does “Z” mean at the end of a timestamp?

Zulu time, meaning UTC. 2026-09-18T13:00:00Z is 13:00 UTC, which you then convert to local time.