A .ics file is an iCalendar document: a text container of events, to-dos, journal entries and free/busy blocks, written as folded property lines inside BEGIN/END component blocks. It is what every calendar invitation you have ever received is made of.
Private for supported formats — processed in your browser
Convert supported files
Runs on your device
+
Drop ICS files here
Batch files can each use a different output. Nothing uploads for local conversions.
Working inputs include camera RAW, browser-local audio/video, PDF, CBZ/CBR comics, office documents, ebooks, markup, 3D models, structured text, images, and archives.
RFC 2445 defined iCalendar in 1998, building on the earlier vCalendar work from the Versit consortium, and RFC 5545 replaced it in 2009. It became universal because it solved interoperability between Outlook, Lotus Notes and everything that followed — an emailed .ics attachment is still the only calendar invitation format that every client understands.
Line folding makes the format deceptively hard to parse correctly
RRULE is powerful enough that clients disagree on edge cases
Verbose relative to the information it carries
Compatibility
Read by Google Calendar, Outlook, Apple Calendar, Thunderbird and effectively every scheduling tool. Novus Convert parses events locally and converts to JSON and CSV, unfolding continuation lines first so long descriptions and locations survive intact.
Event fields — UID, summary, start, end, location and description — are preserved. Recurrence rules and embedded timezone definitions are not expanded into flat tabular output.