Calendar inspection
Event inspection, not a complete RFC validator. Previews start at the file’s DTSTART, not today.
Source: your calendar file · RFC 5545Parsed locally with ical.js.
What’s in your calendar?
Drop a calendar file. Understand its times, repeats, and date problems.
Your file stays in this browser. No upload, account, or saved history.
The core tool stays free. There is no premium plan.
Accounts, cards, onboarding tours, or upgrade nags.
A check never becomes a public listing.
The indie shelf
More small tools, ready now.
This tool stays focused on one job. Other tools by turushan are ready for the next small task.
Calendar details, in plain language.
Why is my event at the wrong time?
A date-time ending in Z means UTC. A TZID points to a timezone definition. A date-time with neither is floating: the file does not name a timezone. IndieICS shows the original fields and never guesses a missing zone.
How much of a repeating event can I see?
Up to 10 occurrences from its original start, within ten years. Processing stops after two seconds. Exclusion dates apply to the preview. Overrides, unsupported fields, or unresolved timezone data can withhold the preview. No result promises every calendar app will interpret a file identically.
Does my calendar leave this device?
No. This page reads and inspects the file in your browser. It never uploads the contents, adds them to a URL, or saves them. Cookieless traffic analytics receives no calendar contents. Clear removes the input and result from the page.