Original reference guides · Reviewed 8 October 2026
Calendar Import Notes
Practical notes for diagnosing ICS calendar imports: snapshots, time zones, all-day boundaries, repeating events, and text encoding. Start with the symptom that matches your file.
- Import or subscribe? Choose before troubleshooting
events arrived once, but later changes never appeared.
- Wrong hour? Separate the instant from its display
everything is shifted by an hour, or an event moves when you travel.
- All-day events: the end date is a boundary
a two-day event displays as one day, or a holiday appears as a midnight appointment.
- Repeating events, exceptions, and duplicate identities
a moved occurrence appears twice, a skipped date returns, or re-importing fails to update an event.
- Valid-looking text: escaping, folding, and UTF-8
descriptions disappear, accented text breaks, or a file imports only partly.
Synthetic ICS examples
Five small UTF-8 calendar files, with no real appointments or personal data. Save a file rather than opening it if you only want to inspect its text.
- all-day-weekend.ics · 372 bytes
- floating-local-time.ics · 372 bytes
- recurring-exceptions.ics · 613 bytes
- single-utc.ics · 345 bytes
- text-and-folding.ics · 419 bytes