A product manager at a company with offices in San Francisco, Berlin, and Bangalore schedules a product launch webinar at 2pm Pacific. Instead of sending three different times in an email, they share a single link. Each recipient sees the event in their own timezone: 5pm in New York, 11pm in Berlin, 2:30am in Bangalore.
A gaming community organizer runs a tournament with players across Europe, North America, and Southeast Asia. They post an event link in Discord. Each player clicks it and sees the start time in their local timezone, plus a countdown so they know exactly how long until the tournament begins.
A conference speaker presenting at an online event needs to tell attendees when the session starts. The event page shows the start time in 12 major timezones, and each attendee can add it to their Google Calendar with one click using the generated calendar link.
A freelancer in Cape Town schedules a client call with someone in Auckland. The 14-hour time difference makes manual conversion error-prone. By using the event announcer, both parties see the correct local time and the freelancer avoids scheduling the call at 2am by mistake.
You enter an event name, date, time, and the timezone the event is scheduled in. The tool converts that moment to UTC and then displays it across 12 major world timezones. Each row shows the city name, timezone abbreviation, local time, and whether it is the same day, the next day, or the previous day relative to the event's origin timezone.
The tool generates a shareable URL that encodes the event details as query parameters. When someone opens that URL, the page loads with the event pre-filled, and their own timezone row is highlighted. This means you only need to share one link, and every recipient sees the event in their local time.
For calendar integration, the tool generates a Google Calendar link and an .ics file download. The Google Calendar link opens the Google Calendar event creation page with the date, time, title, and timezone pre-filled. The .ics file works with Apple Calendar, Outlook, and any calendar app that supports the iCalendar standard.
A live countdown shows the time remaining until the event starts. The countdown updates every second and displays in days, hours, minutes, and seconds. This is useful for building anticipation in community channels or reminding participants how long they have to prepare.
Input
Event: "Team Standup" at 9:00 AM Pacific (America/Los_Angeles)
Output
New York: 12:00 PM. London: 5:00 PM. Berlin: 6:00 PM. Tokyo: 1:00 AM (next day). Sydney: 2:00 AM (next day).
Each viewer sees the time in their own timezone when they open the shared link.
Input
Event: "Webinar" at 3:00 PM Central European (Europe/Paris)
Output
New York: 9:00 AM. Los Angeles: 6:00 AM. London: 2:00 PM. Tokyo: 10:00 PM. Sydney: 11:00 PM.
The Paris 3pm webinar is early morning for the West Coast team.
Input
Event: "Conference Keynote" at 10:00 AM India (Asia/Kolkata)
Output
New York: 12:30 AM. London: 5:30 AM. Tokyo: 1:30 PM. Sydney: 3:30 PM. San Francisco: 9:30 PM (previous day).
India is UTC+5:30, which creates half-hour offsets in many timezone conversions.
Pitfalls to avoid
How does the shared link work?
The link encodes the event name, Unix timestamp, and source timezone as URL query parameters. When someone opens the link, the page loads with the event pre-filled and shows the time in their local timezone highlighted in the table.
Does the tool handle daylight saving time?
Yes. The tool uses the IANA Time Zone Database, which includes DST rules for all timezones. When you select a timezone, the tool automatically applies the correct UTC offset for the date you chose, including DST adjustments.
Can I add the event to my calendar?
Yes. The tool generates a Google Calendar link that opens Google Calendar with the event pre-filled. It also generates an .ics file you can download and import into Apple Calendar, Outlook, or any calendar app that supports the iCalendar standard.
What timezones are shown in the table?
The table shows 12 major world timezones: Los Angeles, New York, London, Paris, Berlin, Dubai, Mumbai, Singapore, Tokyo, Sydney, Auckland, and your local timezone. Your local timezone row is highlighted automatically.
How accurate is the countdown?
The countdown uses your device's system clock, which is typically synchronized with internet time servers (NTP). It updates every second and shows days, hours, minutes, and seconds remaining until the event starts.
Can I share the event link in Discord or Slack?
Yes. The shareable link is a regular URL that works in any messaging app. When recipients open it, they see the event time in their local timezone. You can also paste the link in Discord alongside a Discord timestamp code for maximum clarity.
What happens if the event is in the past?
The countdown shows a negative value (time since the event) and the table still displays the correct times. The calendar export buttons still work, allowing you to add past events to your calendar for reference.
Why does the day differ across timezones?
Because timezones are offset from UTC, the local date can differ. An event at 11pm on July 28 in New York is 4am on July 29 in London and 1pm on July 29 in Sydney. The tool shows the day offset so you know when the event falls in each timezone.
Timezone conversions use the IANA Time Zone Database, which is maintained by the Internet Assigned Numbers Authority. DST transitions are handled automatically based on the event date. The countdown uses your device's system clock, which is typically synchronized with NTP servers.