---
title: "Fix an ICS file Google Calendar won't import — Import Desk"
description: "Check an .ics calendar for supported errors and split oversized files for Google Calendar, keeping recurring events whole. Free preview, $9 once."
url: "https://importdesk.io/calendar-rescue"
site: "Import Desk"
updated: "2026-11-19"
---

# Fix the ICS file Google Calendar won’t import

Calendar Rescue checks your .ics file for the errors it supports, repairs them, and splits calendars that are too big for one import, keeping each recurring event together with its exceptions.

[Check my file free](https://importdesk.io/app/calendar-rescue)$9 once, only when you download

## The errors it solves

> Imported 0 out of 0 events. Unable to process your iCal/CSV file.

> Oops, we couldn’t import this file.

Google Calendar documents a 1 MB limit for imported files, and large exports often fail with these messages. A file with a structural fault can fail at any size.

## What it does

Oversized calendars

Splits into parts under 900 KB and 1,000 events. A repeating event and its changed occurrences always land in the same part.

Structure faults

Adds a missing VERSION or PRODID, closes events missing their END line, and adds the final END:VCALENDAR when it is gone.

Formatting faults

Fixes line endings, folds lines over 75 bytes, removes control characters and a leading byte-order mark.

Events with no UID

Gives them a stable ID so they import as separate events instead of overwriting each other.

Events with no start date, an unreadable start date, or an end before the start are never guessed at. They go into a separate file exactly as they were, and the report counts them.

## What you get that a plain splitter doesn’t

Cutting a calendar into smaller pieces is only part of the job. A file with a structural fault can fail at any size, and a cut in the wrong place can break a repeating event.

Repairs, not just smaller files

Missing VERSION, PRODID and END lines, line endings and events with no UID are fixed first, so you don’t end up with several broken files.

Repeating events stay together

Each repeating event and its changed occurrences go into the same part, so an import doesn’t leave a series without its exceptions.

Nothing dropped or guessed

Events with no usable start date are set aside exactly as they were, in their own file, instead of being deleted or given a date.

A report and your original

A plain-text report says what was found and changed, and your untouched file comes back in the same zip.

## Free before-and-after preview

Fictional sample. Nothing here is a real person, place or calendar.

## Before: the sample file

```
BEGIN:VCALENDAR
BEGIN:VEVENT
UID:book-club@example.invalid
DTSTART:20260105T190000Z
DTEND:20260105T203000Z
RRULE:FREQ=WEEKLY;COUNT=8
SUMMARY:Harbour Book Club
END:VEVENT
BEGIN:VEVENT
UID:book-club@example.invalid
RECURRENCE-ID:20260112T190000Z
DTSTART:20260113T190000Z
DTEND:20260113T203000Z
SUMMARY:Harbour Book Club (moved a day)
END:VEVENT
BEGIN:VEVENT
DTSTART:20260120T100000Z
DTEND:20260120T110000Z
SUMMARY:Garden swap
DESCRIPTION:Bring seedlings, cuttings and jars. Tables are set up from nine and the swap runs until noon, with tea and a lost-and-found for labels.
END:VEVENT
BEGIN:VEVENT
UID:quiet-hold@example.invalid
SUMMARY:Hold for later
END:VEVENT
BEGIN:VEVENT
UID:film-night@example.invalid
DTSTART:20260131T180000Z
SUMMARY:Film night
END:VEVENT
```

For this tiny sample the limit is set to 3 events per file so you can see a split. Your own file is checked against the real limits.

Events found

5

Recurring

1

Kept whole with their exceptions

File size

759 B

Files out

2

Plus 1 set aside

## What the check found

- RepairedLines ended with LF or CR instead of the CRLF that calendar files use. (29)
- RepairedFolded lines longer than 75 bytes, as the calendar format requires.
- RepairedAdded the missing END:VCALENDAR line at the end of the file.
- RepairedAdded the VERSION:2.0 line the format requires.
- RepairedAdded the PRODID line the format requires.
- RepairedGave events with no UID a stable ID so they import as separate events.
- Set asideSet aside events with no start date. Nothing was filled in for them.
- RepairedSplit the calendar into 2 files. Each event with its recurrence exceptions stays in one file.

## Files you would get

| File | Events | Size |
| --- | --- | --- |
| sample-part-01.ics | 3 | 705 B |
| sample-part-02.ics | 1 | 193 B |

## Before and after

An event with no UID

Before

```
BEGIN:VEVENT
DTSTART:20260120T100000Z
DTEND:20260120T110000Z
SUMMARY:Garden swap
DESCRIPTION:Bring seedlings, cuttings and jars. Tables are set up from nine and the swap runs until noon, with tea and a lost-and-found for labels.
END:VEVENT
```

After

```
BEGIN:VEVENT
UID:import-desk-dac8a009
DTSTART:20260120T100000Z
DTEND:20260120T110000Z
SUMMARY:Garden swap
DESCRIPTION:Bring seedlings, cuttings and jars. Tables are set up from nine
  and the swap runs until noon, with tea and a lost-and-found for labels.
END:VEVENT
```

## How it works

1. Add your .ics file. It is read in this browser and not uploaded.
2. See the free check: what was found, how many files it becomes, and a before-and-after example.
3. Pay $9 once to download a zip with the repaired files, the set-aside events, a report and your untouched original.

## What you download

- Repaired calendar files, ready to import one by one
- Set-aside events, unchanged
- A plain-text report
- Your original file

[Open Calendar Rescue](https://importdesk.io/app/calendar-rescue)

## Other import problems

- [Contacts Import Fix ($8)](https://importdesk.io/contacts-import-fix)
- [My Maps Splitter ($9)](https://importdesk.io/my-maps-splitter)
- [How your files are handled](https://importdesk.io/privacy)
