Free · No account · Works in your browser
Event Time
What time is an event in another city
Event Time
Enter values below, then calculate.
The event time converter answers a cross-time-zone question that wall clocks alone confuse: “If the keynote starts at 9:00 a.m. in Berlin, what time is that for me in Chicago?” Enter the event city, its local start time, and your location—the page maps the same instant on both sides, accounting for offsets and daylight saving where data allows.
Wall clock versus calendar date
International events can fall on different calendar dates for participants. A late-night webinar in Tokyo may still be “yesterday evening” in Los Angeles. Always check both time and date columns before adding holds to your monthly calendar. Missing the date shift causes missed launches more often than missing the hour.
All-day announcements without a zone— “release on March 15”—need a different tool; this page expects a specific clock time tied to a place. For day-only math, use date tools.
Planning webinars and investor calls
Organizers pick a host city time and publish conversions for major regions. Attendees verify personally because automated invites occasionally embed wrong offsets after policy changes. Run the event time check, then paste results into your invite description so recipients can sanity-check without opening a spreadsheet.
Recurring series crossing DST weekends need revalidation each spring and fall—a meeting at “ten a.m. New York” shifts absolute UTC offset when US clocks change even if local wording stays identical. Pair with the daylight saving time page for transition dates in 2026.
Travel and on-site attendance
Flying to a conference? Convert session start times to your home zone before booking return flights. Jet lag makes mental math unreliable; write converted times on a pocket card keyed to the 2026 yearly calendar entry for the trip.
Hotel wake-up calls use local property time—do not assume your phone auto-adjusted correctly on landing. Confirm event time again once you arrive and the device picks up local towers.
Sports, broadcasts, and global product drops
Kickoff times publish in stadium local time; fans abroad convert to watch parties. Esports tournaments stack brackets across regions—misconverted semifinal hours spoil viewing parties. Stream announcements often list UTC; translate UTC to your city here instead of doing offset arithmetic in your head during a busy workday.
Simultaneous product launches may stagger by region for operational reasons even when marketing says “global.” Verify each regional clock independently.
Relationship to world clock and meeting planner
The world clock shows what time it is now in several cities—a snapshot. The meeting planner finds overlap windows across work hours. Event time anchors one scheduled future instant between two places—better for “when does this start for me?” than scanning a grid of current clocks.
Use all three during quarterly planning: planner for recurring staff syncs, event time for one-off external keynotes, world clock for “are they awake right now?” checks before Slack pings.
DST edge cases and ambiguous hours
Spring forward creates nonexistent local times; fall back repeats an hour. Scheduling tools sometimes reject or duplicate those hours. If your event sits inside a transition window, confirm with organizers which offset interpretation they used—US Eastern “2:30 a.m. on transition day” may not exist.
Historical events before modern time zones are out of scope; this tool targets contemporary IANA zones used in calendars today.
Worked example: keynote from London to Denver
Marketing emails “Tuesday 14:00 GMT” for a product reveal. You are in Denver. Enter London or GMT as the event zone with 14:00, select Denver as yours, and read the converted Tuesday time and date. Add calendar buffer fifteen minutes early for stream login—not every platform starts punctually.
Share the converted string with teammates in Slack so sales engineers in multiple US zones align without each redoing math.
Legal deadlines and broadcast blackouts
Regulatory filings sometimes cite “midnight local time” in a named city—convert that instant carefully because midnight belongs to the ending day, not the beginning, in plain language most people use conversationally. Sports blackout rules reference local kickoff; fantasy leagues care about lock times in your home zone even when the stadium is three states away.
When counsel says “close of business Eastern,” clarify whether that means five p.m. or literally market close—finance and law teams disagree more often than newcomers expect. Write the converted result into the ticket so engineers in other zones implement the same absolute instant.
Family events and religious observances
Wedding livestreams list temple local time; relatives abroad convert to know when to dress for video, not only when to send gifts. Observances tied to sunset in one city require different tools—this page expects clock times, not solar tables—but reception dinners afterward still benefit from city-to-city conversion when guests fly in from multiple continents.
Birth announcements and graduation streams repeat the pattern: one authoritative host city time, many personal calendars updated through verified conversion rather than mental arithmetic during emotional weeks.
Broadcast and ticketed events
Concert streams list showtime in venue local time—convert before sharing watch links with international fans. Daylight saving mismatches cause hour-long errors twice yearly; verify both cities on daylight saving time around 2026 transition weekends. Sports finals with fixed UTC kickoff still display locally per broadcaster; trust the city pair on this page over headline abbreviations.
ICS invites should list both UTC and recipient local time in the description field when 2026 board meetings include directors in three regions.
Esports and live streams
Tournament showtimes advertised in venue local time need conversion before 2026 global Discord announcements—double-check daylight saving on both ends when spring patches land near finals weekend. VOD upload schedules should list UTC in metadata even when thumbnails use friendly local copy.
Fan meetups streaming on multiple platforms should list both venue local and home city times in 2026 event descriptions to reduce no-show disputes.
Related tools
Visit the time tools hub for world clock, meeting planner, and daylight saving time. Long-range countdowns: days until on date tools.
Frequently asked questions
How is event time different from the world clock?
World clock shows current time in multiple cities at this instant. Event time converts one scheduled local start time in a host city to the equivalent clock time and calendar date in your city, which is what you need before adding a future hold to personal calendars.
Why can the converted date differ from the event date?
Time zones span the international date line. A morning event in Asia may still be the previous calendar evening in North America. Always copy both date and time into your calendar entry and verify AM or PM carefully when sharing with teammates.
Do daylight saving changes affect recurring meetings?
Yes. A slot defined as ten a.m. in New York shifts absolute UTC offset when US clocks spring forward or fall back. Re-run conversions after DST weekends even if the invite wording unchanged, especially for global teams mixing zones that transition on different dates.
Can I convert an event given in UTC?
Select UTC or GMT as the event zone when organizers publish the start that way. Then pick your home zone to see local wall time without manual offset arithmetic, which reduces mistakes during busy launch weeks or late-night on-call pages.
What if the event spans multiple sessions?
Convert each session separately because host cities or broadcast feeds may change between keynotes, workshops, and social hours. Multi-day conferences often mix on-site local tours with fixed broadcast hours that reference different reference cities, so one conversion rarely covers the entire trip itinerary.
Should I trust this instead of my calendar invite?
Use it to verify invites, especially after zone or daylight saving changes. Official calendar files from organizers remain authoritative when correct—this page catches offset mistakes before you miss the start because an automated system picked the wrong region or outdated transition rules.