CorrectICS

Help Center

Simple, non-technical guidance for fixing broken ICS files, understanding calendar import failures, and getting events back into Google, Outlook, or Apple Calendar quickly.

Common problems

Start here if something is broken right now

In-depth guides

Longer walkthroughs and reference material

Getting started

Tip For a quick fix, go straight to /fix and upload your file — no deep reading required.

The basics

  • What is an .ics? It’s a calendar file format that stores events. Most calendar apps (Google, Outlook, Apple) can import it.
  • Validate & fix a file: Go to /fix, upload your .ics, review the results, and click Download fixed file if offered.
  • Is it safe? Files are processed in memory; results are not stored. See “Limits & Privacy” below.

Popular how-tos

  • Export from Google: Calendar settings → your calendar → Export → download .ics.
  • Export from Outlook: File → Open & ExportImport/ExportExport to a file → choose iCalendar (.ics).
  • Export from Apple Calendar: Select calendar → File → ExportExport… → save .ics.
  • Merge multiple .ics: Zip them and use the Bulk tab on /fix, or open each file in a text editor and copy events together.
  • Inspect events: Open the file in a text editor; each BEGIN:VEVENTEND:VEVENT block is one event.

Troubleshooting

Common error types explained
DTSTART / DTEND issues

Events need valid start and end values. Missing, malformed, or inconsistent timestamps are one of the most common reasons an ICS file fails to import.

TZID problems

Time zones need valid identifiers like America/New_York. Aliases, abbreviations, or missing VTIMEZONE blocks often cause cross-calendar failures.

RRULE errors

Recurring events need valid recurrence rules such as FREQ=DAILY. Broken RRULE values may import partially, repeat incorrectly, or be rejected outright.

UID / PRODID missing

Missing IDs can make events hard to track or de-duplicate. CorrectICS can generate safe defaults when repair is possible.

Limits & Privacy

Privacy first Files are processed in memory; we do not store your calendar.

Retention

We do not persist your uploaded calendar. Logs store minimal request metadata (request ID, status) for operations and abuse prevention.

Encryption

Data is encrypted in transit (HTTPS). At rest, only minimal logs live in provider systems.

Size limits

Typical files up to a few MiB work. Very large or unusually complex calendars may be refused for safety.

Billing & Accounts

Free vs paid
Free runs the validator and shows issues. Paid plans add repaired-file workflows and automation features. See pricing for the full breakdown.
Receipts & refunds
Manage billing from /account. For billing questions, contact us.
Cancel anytime
You can downgrade or cancel from the account portal.

Still need help?

Send us a message and include your X-Request-Id if you have one.