02 / invitation inspection
What time does this calendar file actually store?
Read a local .ics export and compare its start times, embedded timezone rules and this browser. No upload, sign-in or automatic event changes.
Inspection results
Choose a file, paste text or load a sample.
Three mappings, three questions
Pinned reference UTC asks which instant the stored wall time represents under the selected IANA location’s 2026e rules. Embedded file UTC uses the file’s own VTIMEZONE definition, when supported. This browser UTC uses the runtime’s local timezone formatting to find the candidate instant.
A result may contain no candidate or two candidates. A clock fallback can repeat an hour; unsupported zone definitions can prevent reconstruction. These are review states, not successful repairs.
What to do next
Keep the original file. Record the event’s intended date, wall time and location with the organizer. Compare a fresh export after a source update. For account-specific help, follow the Google Calendar diagnostic workflow.
For a test you control, use the invitation round-trip worksheet. An imported ICS file, a subscription feed and a newly issued invitation are different delivery paths; test the path that is actually failing.