The short answer: a calendar invite shows the wrong time when there is a time-zone mismatch somewhere in the chain. The usual culprits are a floating event with no fixed zone, a misconfigured device zone, the sender having created it in their zone, or daylight saving out of sync. The clock value is usually correct; the zone attached to it is not.
You accept an invite for 3:00 PM. It appears at 4:00 PM, or shifts a whole day. The instinct is to blame the app, but calendars are very good at arithmetic. What goes wrong is the information they are doing the arithmetic on: which time zone the event belongs to, and which one your device thinks it is in.
What is actually happening?
Every well-formed calendar event stores a moment in time plus the zone it was created in. Your device then converts that moment to your local clock. If any piece of that chain is wrong or missing, the conversion drifts. The time you see is the device doing exactly what it was told, with bad input.
The four common causes
Nearly every wrong-time invite traces back to one of these. Work down the list in order; the first two cover most cases.
- A floating event. Some events carry no fixed offset at all. They show the same wall-clock number everywhere, so two people in different zones each see it on their own clock and arrive hours apart.
- Your device zone is wrong. If your Mac, phone or laptop is set to the wrong region, or did not update after travel, every event converts against the wrong base.
- The sender created it in their zone. A correct, fixed-zone event still surprises you if the sender quietly built it around their own local time and you read the raw number instead of your converted one.
- Daylight saving out of sync. Clocks spring forward and fall back on different dates in different regions. For a few weeks each year, an offset you assume is fixed is actually an hour off.
| Symptom | Likely cause |
|---|---|
| Same wrong time on every device | Floating event, no fixed zone |
| Only your device is off | Device zone misconfigured |
| Off by exactly one hour, certain weeks only | Daylight saving mismatch |
| Off by the gap between two cities | Created in the sender's zone |
| Wrong day entirely | Crossed midnight after conversion |
How do I diagnose it?
Two checks tell you almost everything. They take less than a minute and point straight at the cause.
- Read the zone on the event. Open the invite and look for the time zone shown next to the start time, often under an edit or advanced view. Note it, or note that there isn't one (a sign of a floating event).
- Check your device zone. Open your system date-and-time settings and confirm the region. If the event's zone and your device's zone tell different stories, you have found the mismatch.
A device set to update its zone automatically avoids the single most common cause. If you fix it by hand and forget to change it back, every future invite converts against the old city. For the provider-specific version of this, see Google Calendar showing the wrong time zone.
How do I fix it?
Once you know the cause, the fix follows:
- Floating event: ask the organiser to re-send with an explicit time zone, or recreate it yourself and pin a zone.
- Wrong device zone: set your device to the correct region, ideally on automatic, and the event will re-convert correctly.
- Sender's-zone confusion: always read your own converted time, not the raw number in the message body.
- Daylight saving: confirm both regions' current offset for the event date, not for today.
For a step-by-step walkthrough of repairing a specific bad invite, see how to fix a meeting invite with the wrong time zone.
Stopping it from happening again
The durable fix is to never rely on a number you have converted in your head. When you schedule across zones, decide on a single moment, attach an explicit time zone, and confirm the person in the other city sees the same instant you intended. This is exactly what Atlas does: it shows each person's real local time, finds the moment everyone is awake, and adds the meeting to your calendar in everyone's correct local time with daylight saving handled, so there is no mental arithmetic left to get wrong.
Frequently asked
Why did a calendar invite show up at the wrong time?
What is a floating time-zone event?
How do I check which time zone an event is stored in?
How can I stop invites landing at the wrong time?
Stop doing timezone math
Atlas finds the time everyone's awake and adds it to your calendar in one tap.
One-time purchase, yours forever.