Settings

The export

The zip from Google Takeout, from Facebook or Instagram's "Download your information", or from Apple's privacy portal, or the folder it was unpacked into. JSON, mbox, CSV, vCard, ICS and Chrome bookmark files inside are read; anything else is listed by name only. It is read in this tab and never uploaded.

Drop the zip or the folder here One zip, several zips, or the unpacked folder

How it works

The export is designed to be technically complete and practically unreadable

Ask Google, Meta or Apple for your data and what arrives is a zip of folders named after products, with the interesting parts buried in JSON files nobody is expected to open. The obligation is to give you the data; there is no obligation to make it legible, and it is not. A Records.json with three million location points satisfies the law and tells you nothing.

This reads that zip (or the folder you unpacked it into) and lays it out by product: where you have been, what you searched for and watched, what the advertising side has written down about you, who wrote to you and how often, what you posted and what you liked. Every table is searchable, exports as CSV or JSON, and the location tracks export as GPX so TRAIL can cut your home out of them before you share anything.

How it opens a file bigger than the memory in the machine

These exports run to gigabytes, and the obvious approach fails on the first one. A browser cannot hold a one-gigabyte string, let alone parse it as JSON: the engine's own limit stops it before your memory does.

So none of the reading happens on the page. It happens in a Web Worker, and the zip is never unpacked into memory at all. A streaming unzip hands each entry over as a run of chunks, and each chunk goes straight into a streaming parser for its format. The big JSON files are not parsed as one document: a byte-level splitter finds the elements of the top-level array and parses each element on its own, so three million location points cost the memory of three million small rows rather than the memory of the file. The mbox is read the same way, line by line, keeping only the From, Date, Subject and label headers.

The page itself never holds the data. It asks the worker for one screen of one table at a time. That is why a multi-gigabyte export opens here while the tab stays responsive, and it is the same reason nothing can leave: there is no point in the pipeline where a copy exists to send.

What to look at first

Location history is usually the one that lands. Google has kept it in at least five different shapes over the years (the flat Records.json, the Semantic Location History months, Timeline Edits, the on-device Timeline from Android, the location-history file from an iPhone), and all of them are read here, because which one you have depends on when you asked and what you carried. Seeing several years of your own movements plotted is a different experience from knowing abstractly that they were recorded.

Then the advertising folder, which is the one people find genuinely unsettling: the inferred interests, the categories you have been put in, the things a company concluded about you that you never told it. It is written in plain language because it was written for advertisers rather than for you.

Then search and watch history, which is the longest and most personal record most people have of their own attention, kept in full, in order, for as long as the account has existed.

When you have looked, the useful next step is to reduce what gets collected from here on: turn the histories off in the account settings, and use EXPUNGE for the brokers who bought the parts that were sold. DATASCAN finds personal data hiding in any spreadsheet you export from this, before you send it to anybody.

The guide: What is actually in a Google Takeout export

Questions people ask about TAKEOUT

What does it read?

From Google Takeout: the location history in every shape it has taken (Records.json, the Semantic Location History months, Timeline Edits.json, the Timeline.json an Android phone exports and the location-history.json an iPhone does), the My Activity folder and the YouTube history, the Ads folder, Chrome’s history and bookmarks, the contacts vCard, calendars and the mbox from Gmail. From Facebook and Instagram: messages, posts, comments, likes and reactions, ad interests and topics, the advertisers who uploaded your contact details or used your activity, and the off-Facebook activity. From Apple: the CSV files its privacy portal writes, each as a table, plus contacts and calendars. Every CSV, vCard and ICS anywhere in an export is read the same way. Files are recognised by what is inside them, so a renamed or translated folder still reads.

Will a twenty-gigabyte Takeout work?

Yes, given time. The zip is never unpacked into memory: it is streamed through a worker, file by file, and each file is read as it streams, so the size of the export is not what limits it. What is kept is the rows: up to 500,000 per table (300,000 for mail), after which the counts and the charts go on but the table and the exports stop. A Records.json with three million points is kept in full, as numbers, and takes about a minute. Several zips can be dropped at once, which is how Takeout splits a large export.

Does it read my emails?

No. From the mbox it keeps the From, Date and Subject lines and Gmail’s labels, and nothing from the body of any message. That is enough to say how many messages there are by year, who wrote most, and what the labels hold. To read the messages themselves, POSTBAG opens the same mbox, or the Takeout zip it came in, and MAILBOX takes one email apart.

Why do the accents in my Facebook messages come out wrong everywhere else, and right here?

Facebook and Instagram write their JSON with every non-ASCII character as the bytes of its UTF-8 form escaped one at a time, so “é” arrives as “é”. A string that holds only characters in that range is read again as UTF-8 bytes here, which puts the accents back. A string that is not valid UTF-8 read that way is left as it came.

Why is there no map under the tracks?

A map means asking a tile server for the tiles round the places you have been, which tells that server where you have been. The tracks are drawn over a plain latitude and longitude grid instead, with no request to anyone. Export the GPX and open it in TRAIL if you want to cut your home out before sharing it, or in any map application on your own machine.

Is anything uploaded or kept?

No. The export is read in this tab, in a worker, and nothing leaves it: the page makes no network request other than for its own files. Nothing is stored either. Close the tab, or press Clear, and it is gone; there is no store to empty.

What does it not do?

It does not show photos or videos, play anything, or open documents; those are listed by name and size. It does not read the HTML versions of Takeout data (choose JSON when you order the export), Google Drive or Docs contents, iCloud Photos, WhatsApp exports, or any JSON in a shape it does not know. It counts and lists; it does not delete anything from your account, and cannot.

Doing this often? The OBSCURA Sovereign Suite reads every file in a folder and lists the credentials, card numbers, ID numbers and personal data in each. On its own, US$2 a month; with everything else, US$5 a month or US$48 a year.