ICS Calendar Parser
Drop in an .ics or iCalendar file to see what is inside it: the calendar name and the app that produced it, then every event with its title, start and end date, time range, location, organizer, status and recurrence rule. All-day events are flagged. The file is read entirely in your browser and is never uploaded.
How to read an ICS file
- Drag an .ics file onto the box, or click to browse for one.
- Read the calendar summary at the top: name, producing app, and event count.
- Scan the event list for each title, date and time range, and location.
Examples
An invite exported from email
invite.ics with one VEVENT for a 10:00 to 11:00 meeting
1 event: Team Meeting, 2026-06-10 10:00 to 11:00 UTC, Room A
Frequently asked questions
Is my calendar file uploaded anywhere?
No. The .ics file is read and parsed entirely in your browser using JavaScript. Nothing is sent to a server, so private invites, attendee emails and meeting notes never leave your device.
Does this work fully in the browser, even offline?
Yes. Parsing happens client-side with no network request, so once the page has loaded you can read calendar files with your connection off. The file stays on your computer.
What is an ICS file?
ICS is the iCalendar format (RFC 5545) used by Google Calendar, Apple Calendar and Outlook to share events. A single file holds a VCALENDAR with one or more VEVENT blocks, each carrying a title, start and end time, location and more.
Which fields does it read from each event?
Title (SUMMARY), description, location, start and end (DTSTART and DTEND), organizer with any mailto prefix removed, unique id (UID), status, and recurrence rule (RRULE). Events marked VALUE=DATE are shown as all-day.
How are dates and times handled?
Times ending in Z are read as UTC and labeled as such, times with no zone are shown as written, and date-only values are treated as all-day. The tool shows the values exactly as stored without converting between time zones.
Does it handle folded lines and multiple events?
Yes. Long lines folded onto continuation lines (per the iCalendar spec) are joined before parsing, and every VEVENT in the file is listed. To-do (VTODO) blocks are counted but not detailed.
Related tools
File Type Identifier
Find out what a file really is from its magic bytes, not its extension. Detects images, audio, video, archives, fonts, and more in your browser. Private.
CSV File Inspector
Inspect a CSV file in your browser: detect the delimiter, encoding and BOM, count rows and columns, guess the header, and preview sample rows. Private.
Strings Extractor
Extract readable text from any binary file in your browser, like the Unix strings command. See each printable run with its byte offset, set a minimum length.
Base64 File Encoder
Encode any file to Base64 and a data URI in your browser. Drop a file to get the raw Base64 and a ready data: URI to copy. Nothing is uploaded.
CBOR Decoder
Decode a CBOR file (RFC 8949) to readable JSON in your browser. Handles integers, byte strings, arrays, maps, tags, and floats. Nothing is uploaded.
ELF Header Inspector
Drop a Linux or Unix binary to read its ELF header: 32 or 64-bit, endianness, file type, CPU architecture, OS ABI and entry point. Runs in your browser.