Create a calendar schedule file

Create an ICS file for the daily, time‑specified, repeating schedule. Verify the actual occurrence date and time zone, then import it directly into the calendar.

Input

Check or change the value using the input public example.

Region/city name · e.g.: Asia/Seoul (Seoul)

Loop·Location·Description

Semi‑monthly time overlap handling

Do not move non-existent times; only provide modification instructions.

Input is processed only in the browser. Refreshing returns a public sample.

Result

Check the result directly using the sample value.

Share result

Share the tool link and result text together. No URL is included in the result. Check the below content and then share it.

Calculation·file generation criteria

Create an ICS file to import the daily/repeating schedule into the calendar.

Convert local date and time to UTC → VEVENT DTSTART·DTEND. Full-day events have a DATE value and a end time that does not include the next day. Repeats are recorded as RDATE based on the date.

Input example

Seoul is saved from 2026-10-05 10:00 to 11:00 UTC as 01:00 to 02:00. If the last date of the full-day schedule is October 5th, ICS DTEND is October 6th.

The Seoul schedule on October 5, 2026, from 10:00 to 11:00 is saved as 01:00 to 02:00 UTC. If the last date of the full-day schedule is selected as October 5th, it includes that date, and the file end date is October 6th. Check each repeat date and download the file directly.

How to use

  1. Type the provided example or change the required value. Expand additional settings for verification.
  2. After checking the result, review the city, schedule, calendar, and time blocks. Errors are not excluded; corrections are provided.
  3. Copy the result or save as a real file. Import and print use device support functions.

Supported range and boundaries

A schedule with up to 100 repetitions per day and 366 days until the last date. It only supports daily and weekly repetitions, and the actual occurrence date and UTC interval are fixed in the file. The file does not auto-update when time zones change after export. The file is imported directly from a calendar app, and email, invitations, and account connections are not provided.

Frequently Asked Questions

Is the local time of the loop schedule retained?

Every day·every week repetition is up to 100 times, and up to 366 days until the last date. The start and end times in each date are converted from UTC and listed as the actual occurrence time. If there are times not available due to daylight saving time, it is instructed to modify the entire input.

Will the invitation be sent or auto‑registered in the calendar?

No. It only downloads the file; email, invitations, and automatic synchronization are not provided. Check the date of occurrence in the app you import. Input and file content are created in the browser, and certain information is included during result sharing.

Calculation criteria and reference materials

Verification of calculation criteria: · Calculation·verification principles · Report errors