Why a calendar export uses UTC timestamps

Choose an unambiguous instant

A calendar export downloads an ICS file containing one calendar event. The exported event uses UTC DTSTART and DTEND values. UTC keeps the instant unambiguous, but it can look different in your local calendar after import. The export does not send email or invitations, and it does not add the event to any calendar automatically. The event title may contain Unicode, and the exporter escapes and folds ICS text as needed.

A worked example

Suppose the export contains UTC 2026-12-31 23:30 with a duration of 60 minutes. The event ends at 2027-01-01 00:30 UTC. If your local timezone is ahead of UTC, the calendar may show the event starting on January 1 instead of December 31. If your timezone is behind UTC, it may still show December 31. The UTC instant has not changed; only the displayed local time has changed.

Duration is supported from 1 to 1440 minutes. In this example, 60 minutes equals one hour. The exported file should not change the event length when imported. A calendar that applies a daylight saving shift may still show the same duration if the event is treated as a fixed UTC interval.

Check the exported event

Before sharing, import the file in your calendar and check the local date, time, duration, and title. Confirm the start and end match the intended local equivalent of the UTC instant. Confirm the title is displayed correctly, especially if it contains Unicode characters. The export does not create a cloud copy or notify other people, so no attendee will receive an invitation.

A useful check is to compare the event end with the event start. For the example above, the difference should remain one hour. If the imported event shows a different duration, review whether your calendar applied a timezone rule or ignored the UTC designation.

Limits and common mistakes

The exporter creates a single event without recurrence. There is no attendee management, no reminder configuration, and no cloud sync implemented. Do not expect the ICS file to update a calendar automatically or to send an email to participants. Those actions must be handled outside the export.

A common mistake is to assume that the exported date is the local date. Always convert the UTC timestamp to your timezone. Another mistake is to expect recurrence or reminder data in the file. Since the file contains one event only, each export represents a single fixed interval.