Check what is really inside an .ics file
Upload an .ics file (or paste its contents) and see every event laid out in a readable table — dates, times, recurrence rules — then fix anything and re-export a clean file.
ICS files are unreadable by design
An .ics file is a machine format: DTSTART:20261015T140000, RRULE:FREQ=WEEKLY;INTERVAL=2, escaped commas, folded lines. When an import goes wrong — wrong dates, duplicated events, missing recurrence — reading the raw file tells you nothing.
This validator parses the events and shows them as a normal table. You see at a glance what the file actually contains, which is the check that matters before importing.
Fix and re-export
Because validation happens in the full editor, you do not just find problems — you fix them. Correct a wrong date, remove a duplicate, repair a recurrence rule, then download a freshly generated, standards-compliant .ics file.
Common problems this catches
Missing end times that make events render as zero-length, all-day events shifted by a day from timezone confusion, biweekly rules encoded as weekly (doubling your events), and dates in the wrong year after a copy-paste from last semester's file.
FAQ
- How do I validate an ICS file?
- Upload the .ics file or paste its contents. Every event is parsed and shown in an editable table, so you can verify dates, times, and recurrence rules before importing anywhere.
- Can I fix a broken ICS file?
- Yes. Edit any event directly in the table — dates, times, titles, recurrence — then download a clean, regenerated .ics file that follows the RFC 5545 standard.
- Why did my calendar import duplicate events?
- Usually because the file encoded a recurring event as many single events, or a biweekly rule as weekly. Open the file here and check the Repeats column — fix the rule, re-export, and re-import.
- Does the validator work with Google Calendar exports?
- Yes. Any standards-based .ics file — from Google Calendar, Apple Calendar, Outlook, or another tool — can be inspected and cleaned here.