Timezones when creating calendar events from text
Understand browser timezones, relative dates and international meeting invitations. Check the event time before saving to Google Calendar.
Start with the timezone shown on the form
Text2Calendar sends your browser timezone with the event description. The badge above the form shows which timezone is being used. A phrase like “tomorrow at 3pm” needs both a reference date and timezone. If your device settings are wrong or you are travelling, check them before generating the link.
Keep the invitation’s timezone in the text
For an international meeting, include the date and the original timezone. For example: “Project call on November 12, 2026 at 15:00 Europe/Berlin for 30 minutes”. Named regions help distinguish daylight saving rules. Abbreviations such as CST can refer to more than one timezone, so use a full region name when possible.
Check daylight saving and the final Calendar view
Different regions change clocks on different dates, and some do not change at all. A fixed UTC offset may not match a city on the meeting date. AI extraction can still misinterpret a timezone. Open the result in Google Calendar and compare the displayed time with the original invitation before saving.
Telegram and recurring meetings
The Telegram bot has its own timezone setting: use /timezone before sending a relative date. The website browser setting does not change the bot setting. Each generated link describes one event. For a weekly meeting, set recurrence in Google Calendar and check its timezone there.