How to Handle Time Zones in Calendar Events: The Complete Guide

Time zones are the #1 source of calendar confusion. You schedule a meeting for 2pm, but half the attendees show up at the wrong time. Or you import an event and it appears 5 hours off. This guide explains how time zones work in calendar apps and how to get them right every time.

How Time Zones Work in Calendars

The Problem

When you create an event at "2:00 PM," your calendar needs to know: 2:00 PM where?

Without time zone info:

• Event shows at 2:00 PM in your time zone
• But what about attendees in other time zones?
• If you travel, does 2:00 PM follow you or stay where it was created?

The Solution: Time Zone Data

Modern calendar formats (ICS) store time in two ways:

1. Local Time with Time Zone ID

DTSTART;TZID=America/New_York:20260120T140000

This means "2:00 PM in New York" — the event adjusts when viewed from other time zones.

2. UTC (Universal Time)

DTSTART:20260120T190000Z

The Z means UTC (Greenwich Mean Time). 7:00 PM UTC = 2:00 PM Eastern = 11:00 AM Pacific.

What Happens Without Time Zone Data

DTSTART:20260120T140000

No time zone specified = "floating time." Calendar apps guess based on your settings. This causes problems.

Common Time Zone Issues (And Fixes)

Issue 1: Events Show Wrong Time After Import

Symptom: You import an ICS file and events appear hours off.

Cause: The ICS file either:

• Has no time zone data (floating time)
• Uses a different time zone than you expected
• Uses UTC but you expected local time

Fix:

1. Open the ICS file in a text editor
2. Look for DTSTART lines
3. Check for ;TZID= or Z (UTC) indicator
4. If missing, add time zone data:

Before:

DTSTART:20260120T140000

After (with time zone):

DTSTART;TZID=America/New_York:20260120T140000

After (UTC):

DTSTART:20260120T190000Z

For more import troubleshooting, see ICS File Not Importing to Google Calendar.

Issue 2: Meeting Shows Different Times for Attendees

Symptom: You schedule 2:00 PM, but coworker in London sees 2:00 PM (not 7:00 PM).

Cause: Event created with floating time or incorrect time zone.

Fix (Google Calendar):

1. Open the event
2. Click More options
3. Look for time zone next to start/end time
4. Click it → Select correct zone
5. Save

Fix (Apple Calendar):

1. Open event
2. Check Time zone field (may need to enable in Preferences → Advanced → Turn on time zone support)
3. Correct if wrong

Fix (Outlook):

1. Open event
2. Check Time zone dropdown
3. Select correct zone

Issue 3: All-Day Events Shift by One Day

Symptom: You create an all-day event for January 20, but it shows as January 19 or 21 for some people.

Cause: All-day events are stored as dates, not times. But the "boundary" of the day differs by time zone.

How all-day events work:

DTSTART;VALUE=DATE:20260120
DTEND;VALUE=DATE:20260121

This means "January 20, all day" — starts at midnight, ends at midnight the next day.

The problem: If calendar app interprets this in UTC but displays in your time zone, the day shifts.

Fix:

• Most calendar apps handle this correctly
• If importing ICS files, ensure the source calendar uses the same date interpretation
• For critical all-day events, consider making them timed events (9am-5pm)

Issue 4: Recurring Events Wrong After Daylight Saving

Symptom: Weekly meeting at 10 AM moves to 9 AM or 11 AM after DST change.

Cause: Event stored in UTC instead of local time with time zone.

How DST works with calendars:

• UTC time: Event stays at same UTC instant → local time shifts
• Local time + TZID: Event stays at same local time → UTC shifts

Example: Weekly standup at 10:00 AM Eastern

With TZID (correct):

DTSTART;TZID=America/New_York:20260120T100000
RRULE:FREQ=WEEKLY;BYDAY=MO

Result: Always 10:00 AM in New York, even after DST.

With UTC (problematic):

DTSTART:20260120T150000Z
RRULE:FREQ=WEEKLY;BYDAY=MO

Result: 10 AM in winter, 11 AM in summer (or vice versa).

Fix: Recreate event using local time with time zone, not UTC.

Setting Up Time Zones in Calendar Apps

Google Calendar

Enable secondary time zone:

1. Settings (gear icon) → Settings
2. General → Time zone
3. Enable Display secondary time zone
4. Select your other frequently used zone

Per-event time zone:

1. Create or edit event
2. Click time zone link next to times
3. Select zone for this specific event

World clock:

1. Settings → World clock
2. Add cities you work with regularly
3. Appears in left sidebar

Apple Calendar

Enable time zone support:

1. Calendar → Preferences (or Settings on iPhone)
2. Advanced tab
3. Check Turn on time zone support
4. Default time zone appears in toolbar

Per-event time zone:

1. Double-click event
2. Look for time zone field in editor
3. Select correct zone

Travel adjustment:

1. When you travel, your calendar can auto-adjust
2. Or keep events in original time zone

Outlook

Default time zone:

1. File → Options → Calendar
2. Time zones section
3. Set primary and secondary zones

Per-event time zone:

1. Create/edit event
2. Look for Time zone dropdown next to start time
3. Select correct zone

Multiple time zones in view:

1. View → Time Scale → Show second time zone

Scheduling Across Time Zones

Best Practices for Remote Teams

1. Always specify time zone in communication

• Bad: "Let's meet at 2pm"
• Good: "Let's meet at 2pm ET / 7pm UK"

2. Use a shared reference time zone

• Many teams use UTC as neutral reference
• Or use HQ time zone as standard
• Document this in team guidelines

3. Share time zone in calendar invites

• Google Calendar does this automatically
• Include zone in event title for clarity: "Standup (10am ET)"

4. Use scheduling tools that show overlap

• World Time Buddy
• Every Time Zone
• Calendar apps' scheduling assistant

Finding Meeting Times

Google Calendar: Suggested times feature

1. Add all attendees
2. Click Suggested times
3. Shows slots that work for everyone

Apple Calendar: Travel time awareness

1. Add location to events
2. Calendar calculates travel time
3. Blocks buffer automatically

Outlook: Scheduling Assistant

1. Click Scheduling Assistant when creating meeting
2. Shows all attendees' availability
3. Highlights overlapping free time

ICS Files and Time Zones

Correct ICS Time Zone Format

Well-formed ICS files include time zone definitions:

BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Example//Calendar//EN
BEGIN:VTIMEZONE
TZID:America/New_York
BEGIN:STANDARD
DTSTART:20251102T020000
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
TZNAME:EST
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20250309T020000
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
TZNAME:EDT
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=America/New_York:20260120T140000
DTEND;TZID=America/New_York:20260120T150000
SUMMARY:Team Meeting
END:VEVENT
END:VCALENDAR

The VTIMEZONE block defines:

• Time zone ID (America/New_York)
• Standard time offset (-0500)
• Daylight time offset (-0400)
• When transitions happen

Common Time Zone IDs

Full list: IANA Time Zone Database

Validating ICS Time Zones

Before importing, check your ICS file:

1. Upload to our ICS Viewer
2. Verify event times look correct
3. Check for time zone warnings
4. Download corrected version if needed

Creating Events Across Time Zones

When you need to schedule events for people in different locations:

Option 1: Use the Attendee's Time Zone

Schedule in their zone, your calendar converts:

1. Create event in Google Calendar
2. Click time zone selector
3. Choose attendee's time zone
4. Enter time that works for them
5. Your calendar shows it in your time zone

Option 2: Use UTC

Neutral ground—everyone converts equally:

1. Calculate UTC time for your desired slot
2. Include UTC in event title: "All Hands (3pm UTC)"
3. Calendar converts for each viewer

Option 3: Let the Tool Handle It

Use Text-2-ICS to create properly formatted events:

1. Paste event details with time zone mentioned
2. AI detects time zone from context
3. Generates ICS with correct TZID
4. Import shows correct time everywhere

Pro Tips

• Travel mode: When traveling, update your calendar's time zone to avoid confusion—or don't, depending on your preference
• Test before sending: Create test event with yourself, verify it appears correctly
• Use city names: "Tokyo time" is clearer than "JST" for most people
• Buffer for confusion: Schedule 15 minutes of slack for meetings across many time zones
• Record time zone in notes: For important events, note the original time zone in the description
• Recurring events: Always use local time + TZID, never UTC, for recurring events

Quick Reference

---

Master Time Zones Automatically

Generate calendar files with proper time zone data built in.

Try Text-2-ICS →