01
Upload your file
Drop your .ics into the fixer at /fix. Validation is free, so you can see what is wrong first.
ICS rescue for broken calendar files
Your calendar file is broken. Let's fix it now.
Upload your .ics file and get a repaired download fast — no manual edits, no subscription required for a one-time rescue.
Processed in memory, not stored Works with Google Calendar, Apple & Outlook One-time fix available — no subscription
Does this sound familiar?
These are the most common failure cases we fix. If yours is here, you're in the right place.
🟦 Google Calendar
ICS won't import into Google Calendar
File uploads but events do not appear, or Google rejects it with a vague error.
🟪 Outlook
Outlook ICS import fails or is incomplete
Only some events import, or Outlook throws an error on the file entirely.
🍎 Apple Calendar
Apple Calendar won't open the .ics file
macOS says the file is invalid, or it opens but nothing gets added to Calendar.
📅 Duplicates
Duplicate events after importing
Your calendar shows the same event multiple times after importing the ICS file.
🌐 Timezone
Events showing at the wrong time
All-day events or meetings appear at incorrect times due to timezone issues.
📂 General
The file won't open on any platform
Something structural is wrong with the file, such as missing headers, malformed events, or bad line endings.
How it works
02
We find the problems
Every property is checked against the iCalendar spec and against real-world client behavior in Google Calendar, Apple Calendar, and Outlook.
03
Download a fixed file
Get a repaired .ics immediately. The one-time rescue option includes 5 fixes for $20, with credits that never expire.
What we fix automatically
- Invalid RRULE, DTSTART, and DTEND fields
- A common reason calendars silently reject an ICS or import only partial events.
- Timezone mismatches and TZID errors
- The hidden timezone problems that often break cross-platform calendar imports.
- Line folding and line ending errors
- Long lines and incorrect CRLF handling can break strict parsers.
- Event property normalization
- Event fields are brought into cleaner, more standards-friendly shapes where safe.
- Multi-event structure problems
- Malformed BEGIN:VEVENT / END:VEVENT blocks can cause only one event to import.
Privacy
Processed in memory
Your calendar events are processed in memory and are not stored as uploaded files.
Minimal logging
Logs contain request IDs and operational status only, not calendar payloads.
Encrypted in transit
All uploads and downloads happen over HTTPS.
Building something with calendars?
CorrectICS also has an API for developers who need validation and autofix in production workflows.
Simple REST API
POST a raw .ics, get validated results and a fixed file in one response.
curl -X POST "https://api.correctics.com/api/validate-ics?autofix=1" \
-H "Authorization: Bearer $CORRECTICS_KEY" \
-H "Content-Type: text/calendar" \
--data-binary @meeting.ics