Export Google Calendar when you need the events outside the app

There are two reasons people go looking for the export button in Google Calendar, and they lead to completely different files. One reason is custody: the events need to exist somewhere that is not a Google account, because a job is ending, an account is being closed, or a backup is overdue. The other reason is analysis: the events need to become rows, so that a quarter of meetings can be added up. Google Calendar has an answer for the first reason and almost nothing for the second, which is why the same search term produces such contradictory advice.

Sorting out which file you actually want takes about a minute, and it saves the hour that gets lost downloading a zip archive, opening it, and discovering that the contents are plain text calendar files rather than a table.

What the word export covers here

Google Calendar produces exactly one format on its own: the iCalendar file, ending in .ics. That format is a text file describing events, one block per event, and it is the standard that Apple Calendar, Outlook and almost every other calendar program reads. It is not a spreadsheet, and no setting in Google Calendar turns it into one.

Around that single format sit four different operations, and they are not interchangeable:

• Export from Settings. Every calendar you can manage, packed into one zip file of .ics files.
• Export a single calendar. One .ics file for one calendar.
• Google Takeout. The account-wide download tool, which can deliver calendar data alongside mail, Drive and Photos, and can be put on a schedule.
• The secret iCal address. Not a file at all. A link another calendar program reads on a loop.

The first three give you a snapshot that stops being accurate the moment you make the next edit. The fourth stays current and gives you nothing to hold. Choosing wrong is the source of most of the frustration in this task.

Export every calendar at once

This is the route Google documents first, and for a backup it is the right one.

1. On a computer, open Google Calendar. This cannot be done from the mobile app.
2. At the top right, open Settings.
3. On the left, click Import and export.
4. Under Export, click Export.

A zip file lands in the download folder. Inside it is one .ics file per calendar, named after the calendar address.

Two conditions are worth knowing before you plan around this. Google states that you must hold the "Make changes and manage sharing" permission on a calendar in order to export it, which means a colleague's calendar you can merely view will not appear in the archive. And if the account belongs to a workplace or a school, the administrator can restrict export settings, so an empty or partial archive is not always a bug.

The zip itself is a container, not an importable file. Google's own import instructions say to open the zip, take the individual files out, and import each .ics separately. Anyone who feeds the zip straight into another calendar and gets an error has found this the hard way.

Export one calendar on its own

When only one calendar matters, exporting all of them and then deleting the rest is wasted work.

1. On a computer, open Google Calendar.
2. On the left, under My calendars, hover over the calendar name.
3. Open Settings and sharing from the three dot menu.
4. Under Calendar settings, click Export calendar.

A single .ics file downloads. This is the file to hand to someone migrating one project calendar, or to keep as a record of a shared team calendar before it is deleted.

If the export attempt returns a feed processing error, the cause is usually the wrong address. Google's guidance is to use the secret iCal address rather than the public one, and if no secret address is visible, the calendar cannot be exported by you at all.

When Takeout is the better tool

Google Takeout is the account-level export, and it exists for a job the calendar settings page does not do: keeping the archive going without anyone remembering to click a button.

Takeout lets you pick which products to include, then choose how the archive arrives. The delivery options are an emailed download link, or a drop into Google Drive, Dropbox, Microsoft OneDrive or Box. Files come as zip or tgz, and you set a maximum archive size, above which the export is split into several files.

The setting that justifies the extra clicks is the export type. A one-time archive builds a single copy. Scheduled exports automatically create an archive every two months for one year, starting immediately. For anyone who has ever wanted a calendar backup and never made a second one, that is the difference between a habit and a good intention.

One practical note on the delivery choice. Sending the archive to Drive, Dropbox, OneDrive or Box means the calendar backup lands in a service that other people may be able to reach, and Google's own instructions include the reminder to make sure the destination folder is not shared with anyone. A calendar is a record of where a person was and who they met, so it deserves the same care as a mailbox archive. The emailed download link keeps the file on one machine, which is usually the right default for a personal export.

Two caveats Google states plainly. Downloading your data does not remove anything from Google's servers, so Takeout is a copy and not a move. And the archive may not include changes made between the moment the request is placed and the moment the archive is built, so a Takeout file is not a precise point-in-time snapshot.

The link that does not go stale

If the goal is to see Google Calendar events inside another program on the Mac rather than to hold a file, the export button is the wrong control entirely.

Every Google calendar has a secret address in iCal format. Open Settings, pick the calendar under Settings for my calendars, open Integrate calendar, and copy the link from the "Secret address in iCal format" section. Paste that into whatever program is going to display the calendar. The receiving program refetches it, so edits made in Google Calendar show up without another download.

The trade-off is that this is a read-only view, and the address is a credential. Google's warning is blunt: only you should know the secret address, and if it leaks, use Reset to invalidate the old one. Anyone holding the link can read the calendar without signing in to anything.

The other option is a full account connection, where the other program authenticates with the Google account through Sign in with Google. That gives two-way editing rather than a read-only feed, and it is the arrangement most desktop calendars on the Mac use, including the ones that let you enter events by typing a sentence instead of filling a form.

Where the file goes next on a Mac

A downloaded .ics file is inert until something opens it, and on a Mac the default handler is Calendar. That is convenient and occasionally destructive, so it is worth knowing what each destination does with the file.

Apple's Calendar app imports an .ics file in two ways: drag the file into the window, or choose File then Import, select the file, then pick which calendar receives the events. Apple documents one side effect that surprises people, which is that importing a calendar file removes the event's previous custom color. Events arrive wearing the color of the calendar they land in.

Apple Calendar also has a second, heavier format of its own. File then Export then Calendar Archive produces an .icbu file covering every calendar at once. It is useful as a local backup, and it is a trap when the file is meant for somebody else, because Apple warns that importing a calendar archive replaces all of your current calendar information and data. The limit on the receiving side points the same way: Microsoft documents Outlook's calendar upload as taking an .ics file, and an Apple calendar archive is not one. If the file has to travel to anyone else, export it as .ics.

Opening the same file in a text editor is the underrated move. An .ics file is readable, and five minutes of scrolling answers questions that no amount of clicking will. Each event sits between BEGIN:VEVENT and END:VEVENT, with the summary, the start and end timestamps, the location and any recurrence rule spelled out. Counting how many events carry a location, or whether the timestamps are stored in UTC, tells you in advance whether the next step is going to work.

If the point of the export was to see the events somewhere better rather than to archive them, the file is a detour. A calendar that holds a live connection shows the same events without a download, and it can add the things a file never carried, such as travel time between two appointments.

Picking between the routes

Route	What you get	Stays current	Best for
Settings export	Zip of one .ics per calendar	No	A full backup before an account change
Single calendar export	One .ics file	No	Handing one calendar to one person
Google Takeout	Zip or tgz, optionally every two months	No, but repeatable	An archive you do not have to remember
Secret iCal address	A read-only feed	Yes	Seeing the calendar inside another app
Account connection	Two-way sync	Yes	Actually working in another calendar

What no export carries with it

An .ics file is thinner than the calendar it came from, and the gaps show up at the other end.

Google documents that when events are imported, guests and conference data are not imported. A meeting that arrives from a file is therefore an appointment with a title and a time, not a meeting with five invitees and a video link. Anyone exporting in order to preserve attendee lists or Meet links is going to be disappointed, and the fix is a connected account rather than a better file.

Recurring events are the second gap, and the shape of the loss depends on the format. From an .ics file the recurrence rule usually survives. From a .csv file Google states that repeating events might not show as a series and will instead appear as a run of one-time events. That distinction matters the moment someone tries to route calendar data through a spreadsheet on the way to another calendar.

Time zones are the quiet third gap. An .ics file stores timestamps, and whether an event lands at the right hour at the other end depends on the receiving program reading those timestamps the same way. Events created while travelling, or all-day events that span a date boundary, are where the drift shows up. Checking a handful of known appointments after any import is faster than discovering the problem when someone misses a call.

Attachments, notification settings, calendar colors and per-event permissions are all outside the scope of a plain file transfer. Apple's Calendar documentation makes the same point from the other direction, noting that importing a calendar file removes the event's previous custom color.

What to change first

Decide whether the real need is a file or a feed, and stop there. If it is a file, set up a Takeout scheduled export once so the backup keeps happening. If it is a feed, connect the account rather than pasting a secret address, because a read-only copy is where the second calendar starts drifting from the first. For a desktop calendar on the Mac that keeps a live Google connection instead of a downloaded snapshot, see Caltimate.