How to Write Time Zones in Emails, Invites and Discord
To write a time that people in other time zones can’t misread, give the day, the time and a place or UTC offset, and convert it for the main readers yourself. For example: “Thursday, March 18, 2027, 9:00 AM Vancouver (UTC−7) / 12:00 PM Toronto / 4:00 PM London.” Avoid bare abbreviations like “EST” or “IST”, which can be wrong for the season or mean different places, and never write “12 AM” for a deadline. For documents and data, use the international format 2027-03-18T09:00:00−07:00. On Discord, use a timestamp tag such as <t:1805385600:F> and every reader sees their own local time. This guide gives copy-ready formats for emails, calendar invites, documents and chat, with the rules behind them. Facts are as of November 2026.
At a glance
- Always include the day of the week and date, not just the time.
- Name a city (“Toronto time”) or an offset (“UTC−4”). Both are unambiguous.
- Use “ET”, “PT” and “CT” for “local time there in any season”; “EST” is only correct in winter.
- Data and documents: ISO 8601 / RFC 3339, like 2027-03-18T16:00:00Z (“Z” means UTC).
- Discord: <t:UNIX:F> shows a full date and time converted for each reader.
The four rules
- Say the day. A 5 PM call in Vancouver is already the next morning in Sydney. “Thursday 5 PM PT” removes the doubt; “5 PM PT” does not.
- Anchor the time to a place or an offset. “2 PM Toronto time” or “2 PM UTC−5” can only mean one thing. Abbreviations are conventions, and some clash: “CST” is used for both US Central Time and China Standard Time, 14 hours apart.
- Convert for your main readers. Don’t make five people do the maths. Give two or three local times, starting with the organiser’s.
- Use noon and midnight in words. “12 PM” and “12 AM” confuse people. For deadlines, NIST suggests using “11:59 p.m. or 12:01 a.m.” instead.
Copy-ready formats for emails and messages
| Situation | Write it like this |
|---|---|
| Meeting with people in a few cities | Thursday, March 18, 2027 · 9:00 AM Vancouver / 12:00 PM Toronto / 4:00 PM London |
| Global audience (webinar, launch) | Thursday, March 18, 2027, 16:00 UTC (9 AM PT, 12 PM ET, 4 PM London, 9:30 PM India) |
| Deadline | Submit by Friday, March 19, 2027, 11:59 PM Toronto time (UTC−4) |
| North American TV-style listing | 8 PM ET / 5 PM PT |
| Formal document | 18 March 2027 at 16:00 UTC |
All local times above were computed from the IANA time zone database for March 18, 2027. That date is a good example of why conversion matters: North America moves its clocks forward on March 14, 2027 but the UK not until March 28, so for two weeks Toronto is only 4 hours behind London instead of 5. On April 1 the same 9 AM Vancouver call is at 5 PM in London. Our clock changes list has every country’s dates.
ET or EST? PT or PST?
“EST” means Eastern Standard Time, UTC−5, used in winter. From March 14 to November 6, 2027, New York and Toronto are on EDT (UTC−4). Writing “3 PM EST” in July is technically an hour off, and some people will take it literally. The generic forms avoid the problem:
| Write | Means | Winter 2026–27 | Summer 2027 |
|---|---|---|---|
| ET | Eastern Time (New York, Toronto) | UTC−5 (EST) | UTC−4 (EDT) |
| CT | Central Time (Chicago) | UTC−6 (CST) | UTC−5 (CDT) |
| MT | Mountain Time (Denver) | UTC−7 (MST) | UTC−6 (MDT) |
| PT | Pacific Time (Los Angeles, Seattle) | UTC−8 (PST) | UTC−7 (PDT) |
Canada adds a 2026 wrinkle. British Columbia’s year-round time is officially Pacific Time, abbreviated PCT (UTC−7 all year), so “PT” no longer means the same thing in Vancouver and Seattle in winter. If both matter, write “9 AM Vancouver / 8 AM Seattle”. Likewise Alberta uses Alberta Time (ABT), UTC−6, and Manitoba Manitoba Standard Time (MBT), UTC−5, all year. See our daylight saving time explainer for who changed.
Calendar invites
- Create the event in your own time zone and let the calendar convert it. Google Calendar, for example, says an event “will also show up in the local time zones for anyone you invite”.
- Still put the times in the description. People read forwarded invites and email previews that don’t convert.
- Recurring meetings follow the organiser’s clock. When one side changes clocks and the other does not, the meeting moves by an hour for the other side. Manitoba’s government warns that events created before a time zone update, or on another platform, may display an hour earlier or later than intended, and asks people to check recurring meetings and meetings organised from outside the province.
- For a global meeting, schedule in UTC if no one city is “home”. Our best meeting times guide shows the hours that work for the US, Europe and Asia.
Documents, data and code: ISO 8601 and RFC 3339
For anything a computer may read, use the ISO 8601 format in its internet profile, RFC 3339: year-month-day, a “T”, the time, and then the offset. RFC 3339 gives the example “1996-12-19T16:39:57-08:00”, which it describes as having “an offset of -08:00 from UTC (Pacific Standard Time)”. The letter “Z” is “A suffix which, when applied to a time, denotes a UTC offset of 00:00”.
| Meaning | RFC 3339 / ISO 8601 |
|---|---|
| 9:00 AM in Vancouver, March 18, 2027 | 2027-03-18T09:00:00-07:00 |
| The same moment in UTC | 2027-03-18T16:00:00Z |
| The same moment in Toronto | 2027-03-18T12:00:00-04:00 |
| The same moment in India | 2027-03-18T21:30:00+05:30 |
An offset records a moment, but not the rules of a place. If you are storing a future event that should stay at “9 AM in Toronto” even if Ontario’s rules change, store the zone name too (America/Toronto), as calendar apps do.
Email headers (for the curious)
The email standard, RFC 5322, puts a numeric zone in every message’s Date header, such as “-0400”. It says the plus or minus sign shows whether the time is “ahead of (i.e., east of) or behind (i.e., west of) Universal Time”. Old letter codes such as EST and PST are kept only as obsolete forms, and the one-letter military zones “SHOULD all be considered equivalent to “-0000″” because the older email standard, RFC 822, defined them with an error. The lesson for humans is the same: numbers beat letters.
Discord timestamps
Discord lets you post a time that converts for every reader. Write <t:TIMESTAMP:STYLE>, where TIMESTAMP is Unix time in seconds. Discord’s documentation lists these styles:
| Style | Shows | Discord’s example |
|---|---|---|
| t | Short time | 16:20 |
| T | Medium time | 16:20:30 |
| d | Short date | 20/04/2021 |
| D | Long date | April 20, 2021 |
| f (default) | Long date, short time | April 20, 2021 at 16:20 |
| F | Full date, short time | Tuesday, April 20, 2021 at 16:20 |
| s | Short date, short time | 20/04/2021, 16:20 |
| S | Short date, medium time | 20/04/2021, 16:20:30 |
| R | Relative time | 4 years ago |
For our example meeting (9:00 AM Vancouver on March 18, 2027, which is 16:00 UTC), the Unix time is 1805385600, so you would type <t:1805385600:F> for the full date and time, or <t:1805385600:R> for “in X days”. The Discord developer reference says timestamps “display the given timestamp in the user’s timezone and locale”, so the wording and date order vary by reader.
Common mistakes and fixes
| Written | Problem | Better |
|---|---|---|
| “Call at 3 PM EST” (in July) | EST is winter time; in July it is EDT | 3 PM ET, or 3 PM New York time |
| “Due 12 AM Friday” | Start or end of Friday? | Due Thursday 11:59 PM, or Friday 12:01 AM |
| “9 AM IST” | India, Israel or Ireland? | 9 AM India (UTC+5:30) |
| “Tuesday 4 PM my time” | Readers don’t know your zone | Tuesday 4 PM Vancouver (UTC−7) |
| “15:00 GMT” (in summer, meaning London) | London is on BST (UTC+1) in summer | 15:00 London time, or 14:00 UTC |
Check any conversion with our time zone converter, or see every zone in our time zones list.
How we checked
All example conversions were computed from the IANA tz database version 2026e with Python’s zoneinfo and repeated with the operating system’s date command. The Discord Unix value was computed for 16:00 UTC on March 18, 2027.
Sources
- RFC 3339: Date and Time on the Internet: Timestamps
- RFC 5322: Internet Message Format (sections 3.3 and 4.3)
- Discord developer reference: message formatting, timestamp styles
- NIST: Times of day FAQs
- Google Calendar Help: Use Google Calendar in different time zones
- BC Government: Pacific Time, PCT
- Government of Alberta: Alberta Time (ABT)
- Government of Manitoba: Time change
Frequently asked questions
How do I write a time zone in an email?
Give the day, date and time with a city or UTC offset, and convert for your main readers: “Thursday, March 18, 2027, 9:00 AM Vancouver / 12:00 PM Toronto / 4:00 PM London.”
Should I write EST or ET?
ET, unless you specifically mean winter time. ET is correct in every season; EST only from early November to mid-March.
What is the correct format for time zones in data?
RFC 3339 / ISO 8601 with an offset, such as 2027-03-18T09:00:00-07:00, or with “Z” for UTC.
How do I post a time in Discord that shows in everyone’s time zone?
Use <t:UNIX:F>, replacing UNIX with the Unix time in seconds. For 16:00 UTC on March 18, 2027 that is <t:1805385600:F>.
Is UTC or GMT better for international emails?
UTC. It never changes for summer time, while London switches from GMT to BST.