How to see a sender's time zone and local time in Gmail

Sarah, a project lead in New York, opens her inbox on a Tuesday evening and sees a message from Kenji in Tokyo stamped 9:12 PM. It looks as if Kenji is working late. He isn't. In Tokyo it was 10:12 AM on Wednesday, and he had just started his day.

That gap is the whole problem. The time Gmail shows is on your clock, so it says nothing about the sender's day. This guide explains how to see a sender's time zone in Gmail with what Gmail already shows, a few manual methods that take seconds, and a habit that makes the answer instant for the people you email most. It also covers the two traps that catch careful people: daylight saving weeks and the international date line. Everything here works without installing anything.

Does Gmail show a sender's time zone?

Gmail on the web puts a time on every message. In the inbox list it's a short stamp: a clock time for today's mail and a date for older mail. Open a message and its date and time appear at the top, beside the sender's name. For more, Gmail Help describes clicking Show details, next to the recipient line, to open a panel of extra information about the message.

All of those times are shown in your own time zone. None of them is labeled with the sender's local time. A stamp of 9:12 PM means 9:12 PM where you are, wherever the sender happened to be.

The retired "Sender time zone" feature

If you remember Gmail showing this, you're not imagining it. In April 2009, Gmail added an experimental Labs feature called Sender time zone. Once you switched it on, a small green or red phone icon hinted whether it was a reasonable hour to call the sender, and the message details showed their local time. Google retired it from Labs on October 5, 2012, explaining that few people used it and that it confused people who had forgotten turning it on. Old forum threads that tell you to enable it describe a setting that no longer exists.

What the other person sees when you email them

The rule works in both directions. When you email someone in another time zone, their inbox shows your message on their clock, not yours. If Priya sends a note from Bengaluru at 11:40 PM on a Tuesday, Lukas in Berlin sees it stamped 8:10 PM. Neither of them sees the other's time unless someone writes it down.

That's why the rest of this guide is about finding one fact, the city someone works from, and then doing a small calculation for the right date.

How to see a sender's time zone in Gmail: five manual methods

You don't need a tool to work out a sender's time zone. You need one reliable clue, and then the date you care about. Start with the strongest clue you have.

1. Read their signature

A signature often answers the question outright: an office address, a line like "Based in Singapore", or a city under the job title. A city is the best clue you can get, because a city has one time zone and its daylight saving rules are public.

A phone number is weaker. The country code +81 points to Japan, which uses a single time zone. The code +1, though, covers the United States, Canada and several Caribbean countries, which together span many time zones. Mobile numbers also travel with their owners, so a +44 number can belong to someone who moved from London to Lisbon last year.

2. Look for a time they wrote

People often state their frame of reference without thinking about it: "Can we talk at 2 pm Indonesia time?" or "I'm free after 17:00 CET." A time with a zone attached is the sender telling you which clock they live by.

Read these carefully. Indonesia spans three time zones, so "Indonesia time" usually means Jakarta (UTC+7), but not always. Many people keep writing "CET" in summer, when Central Europe is actually on CEST, one hour later. Some abbreviations name more than one place entirely, which is why time zone abbreviations can be ambiguous.

3. Notice when their replies arrive

If a colleague's messages consistently land between 1:00 AM and 9:00 AM on your clock, that window is probably their working day. It's a soft clue, since people answer email at odd hours, but over a few weeks the pattern is usually clear. Use it to form a guess, then confirm the guess another way.

4. Ask once, and write the answer down

Asking is fast and nobody finds it rude. Try: "So I don't email you at 3 AM, which city's time do you work on?" Ask for a city rather than an abbreviation or an offset. An offset such as UTC−5 changes when daylight saving starts or ends. A city doesn't, and any converter can turn a city into the correct offset for a given date.

5. Look up the city for the date that matters

Once you know the city, search for its current time or check a world clock. If you're planning something for next month, check the time difference for that date, not today's. Daylight saving changes can move the gap by an hour in between, as the section below shows.

A clue to ignore: the email domain

A .de or .co.uk address doesn't place anyone in Germany or Britain. Companies use one domain worldwide, people work remotely, and addresses like @gmail.com say nothing at all about location. Treat the domain as, at most, a reason to ask.

How to read the time an email was sent

Gmail's stamp tells you when a message was sent, on your clock. To know what that moment meant for the sender, convert it into their time zone. It takes three steps:

1. Find the time difference for that date. Berlin and Bengaluru are 3 hours 30 minutes apart in September. In December, after Berlin's clocks go back, they are 4 hours 30 minutes apart.
2. Add or subtract. If the sender is ahead of you, add the difference to the stamp. If they're behind, subtract it.
3. Check whether the day changed. If the result crosses midnight, it was the next or previous day for them.

Here is what that looks like for three real city pairs:

What a late or early timestamp does and doesn't mean

An email sent at 11:40 PM the sender's time might be urgent. It might also be someone clearing their inbox before bed. The hour alone doesn't say which, so read the message rather than the clock. What the hour does tell you is practical: the sender is probably about to stop working, so a reply from you won't be read for several hours.

Some people also write at night and send in the morning, or send from a phone while traveling. The stamp records when a message left, not always when it was written or where the person normally works.

Why your reply can lose a day

The time difference also decides when your answer is read. If Sarah replies to Kenji at 9:00 AM on Wednesday in New York, it's already 10:00 PM on Wednesday in Tokyo. Kenji reads it on Thursday morning, a full day after he asked. If Sarah had answered before logging off on Tuesday evening, he'd have had it at the start of his Wednesday.

Once you know someone's zone, it's worth thinking about which end of your day overlaps with the start of theirs, and saving quick answers for that window.

Before you reply or call: is it a good time for them?

Email can arrive at any hour without harm, but calls, chat messages and anything urgent should respect the other person's day. Before you pick up the phone, check three things.

Their working hours. Don't assume 9 to 5. Some people start at 7:00, others work split shifts or late evenings to overlap with a team abroad. If you work with someone regularly, ask what hours they keep, and note it next to their city.

Their weekend. Not everyone's weekend is Saturday and Sunday. Saudi Arabia, Egypt, Qatar, Kuwait and several other countries take Friday and Saturday off, according to The National, and the UAE moved to a Saturday–Sunday weekend in January 2022. A Sunday-morning email from a colleague in Riyadh is a normal start to their week. At 10:00 AM on a Sunday in Riyadh, it's 8:00 AM in London and 3:00 AM in New York.

Their public holidays. A silent inbox during a national holiday isn't a slow reply. If you're waiting on someone and hear nothing, check whether it's a holiday where they are before you follow up.

Daylight saving weeks and the date line

Most time zone mistakes don't come from people who never checked. They come from a time difference someone memorized that quietly changed.

The weeks your usual difference is wrong

Countries that use daylight saving time don't all change their clocks on the same day. In 2026 the United States moved its clocks forward on March 8 and moves them back on November 1, following the rules published by NIST. The UK moved forward on March 29 and goes back on October 25, as listed on GOV.UK; the EU changes on the same days. For the week between, New York and London are 4 hours apart instead of 5.

The southern hemisphere moves the other way, which can stretch a gap twice in one month. On October 1, 2026, Sydney is 9 hours ahead of London. Sydney's clocks go forward on October 4, making it 10 hours. London's go back on October 25, making it 11. The same thing will happen again next spring: the US changes on March 14, 2027 and the UK on March 28, 2027, so for two weeks New York and London will again be 4 hours apart. There's a fuller guide to the weeks when US and European clocks are out of sync.

Places that don't use daylight saving time, such as India, Japan, China and Singapore, cause a quieter version of the same problem. Their clocks don't change, so the gap to them changes when yours does. Priya in Bengaluru is 9 hours 30 minutes ahead of New York in September and 10 hours 30 minutes ahead after November 1.

The fix is simple: calculate the difference for the date you care about, not from memory.

When "tomorrow" is already today for them

Near the international date line, the date itself is as likely to trip you up as the hour. When it's 4:00 PM on Thursday in New York, it's already Friday morning in Auckland. How early on Friday depends on the week, because both cities change their clocks in the autumn:

• On September 17, 2026, 4:00 PM Thursday in New York is 8:00 AM Friday in Auckland (16 hours ahead).
• On October 1, after New Zealand's clocks go forward, it's 9:00 AM Friday (17 hours).
• On November 5, after US clocks go back, it's 10:00 AM Friday (18 hours).

Relative words break across that line. If a client in Auckland asks for something "by the end of Friday", their deadline passes at 1:00 AM on Friday in New York, which is really Thursday night for you. When you reply, use a weekday and a date rather than "tomorrow", and name the city whose clock you mean. The guide on how to write a meeting time in an email covers the wording in detail.

Build a saved-time-zone habit

Working out someone's time zone once is easy. Working it out again every time you email the same person is where mistakes creep in. For the people you write to every week, keep the answer somewhere you'll see it while you're writing.

A short list is enough. Record four things for each person:

A few rules keep the list accurate:

• Store the city, not an abbreviation or an offset. "Tokyo" is right every day of the year. "UTC−5" is right for New York only in winter.
• Write working hours in their time. Then the entry stays true when your own clocks change.
• Keep it where you write. The notes field on their contact card, a pinned note or a small shared sheet for your team all work. A list you have to go looking for won't get used.
• Update it when a signature changes. A new office address or a line like "now based in Lisbon" means the old entry is wrong.
• Re-check recurring calls around each clock change. Because you stored cities, the list doesn't go stale, but the gaps between cities shift when clocks change in spring and autumn.

With the list in place, most questions take a glance: what time is it for Kenji now, what time was it when he wrote, and is this a reasonable hour to call. If you need a slot that suits several people at once, see how to schedule meetings across time zones.

Checklist: before you reply to or call someone abroad

Run through this in under a minute:

• I know the city they work from, not just an abbreviation or an offset.
• I've converted Gmail's timestamp into their time, for the date it was sent.
• I've checked whether the day was different for them.
• I've checked for a daylight saving change between then and now, or before the date I'm planning for.
• It's inside their working hours, and not their weekend or a public holiday.
• If I'm proposing a time, I've written a weekday, a date and a city.
• Their city and hours are saved somewhere I'll see next time.

Frequently asked questions