Google Takeout is useful for exporting data, but it leaves developers and system administrators with a less elegant problem: what to do with potentially hundreds of gigabytes of ZIP files containing MBOX mailboxes, JSON metadata, photos, calendars, activity records, and service-specific directory structures. Takeout Reports is a free macOS application designed to inspect those archives in place, count the actual records they contain, and expose their structure without first extracting the dataset.
Takeout Reports in 30 seconds
- Takeout Reports parses Google Takeout exports directly from ZIP or TGZ archives, as well as already extracted directories.
- It reports records rather than simply counting files, covering Gmail, Photos, Activity, Drive, Chrome, Calendar, Contacts, YouTube, Maps, and other services.
- Multipart Takeout exports are presented as a single logical tree, with warnings when volumes are missing.
- Processing is local and the developer says the macOS application has no network entitlement.
- The current reporting and browsing features are free, with transformation and search capabilities planned separately.
The application comes from Color Vivo Internet, the developer behind Mbox Viewer, and is currently available for macOS 14 and later on both Apple Silicon and Intel Macs. While its interface is intended to make Takeout accessible to ordinary users, some of its more interesting characteristics concern storage, privacy, parsing, and large-archive handling.
For administrators dealing with account migrations, long-term archives or user data recovery, the distinction between opening an archive and fully extracting it can become important very quickly.
Inspecting a 200 GB archive without another 200 GB of storage
Takeout Reports’ most practical architectural decision is to read files directly from the archive.
A traditional workflow around a large Takeout export often looks something like this: download the archives, verify that every part is present, extract them somewhere with sufficient capacity, inspect the resulting directory hierarchy and then decide which datasets are actually useful.
The extraction stage can become expensive in terms of temporary storage.
Takeout Reports instead reads the contents from ZIP files without creating an extracted copy on disk. Its developer gives the example of analyzing a 200 GB archive on a Mac with only 30 GB of remaining free space, provided the original archive itself is already accessible.
That approach can also be useful when Takeout exports reside on external storage and the objective is inspection rather than migration.
ZIP is the recommended format, although the application also accepts TGZ archives and previously extracted directories.
Large Takeout jobs introduce another complication: multipart archives.
Takeout Reports recognizes these parts and represents them as a single logical tree rather than forcing the administrator to inspect every volume independently. More importantly, it attempts to detect missing parts and warns about them before presenting a report that could otherwise be mistaken for a complete dataset.
For backup verification and old exports, that is more useful than simply reporting that several ZIP files opened successfully.
Parsing records instead of counting JSON files
Another important distinction is what Takeout Reports considers useful information.
A filesystem-level inventory can tell an administrator that a directory contains three JSON files. It cannot tell them whether those files describe three records or 300.000.
Takeout Reports parses supported datasets and attempts to count the underlying records.
For Gmail and Google Groups, the report can include message counts, unique senders, Gmail labels, the years represented in the mailbox and the number of messages carrying attachments.
Google typically exports Gmail data as MBOX, so this also gives administrators an initial overview before deciding whether a mailbox requires deeper processing.
For Google Photos, the application distinguishes photos from videos and analyzes information such as albums, year-based folders, edited copies and available metadata. It can also report photos for which it could not find dates or geographic coordinates.
That last capability may be particularly relevant when the Takeout export is intended for migration into another photo-management system. Moving the binary image files is relatively straightforward; preserving the relationship between those files and their metadata is often the more complicated part.
The application also analyzes My Activity, including the number of actions represented in the export, the products associated with them and the historical period covered.
Drive, Chrome, Contacts, Calendar, YouTube, Tasks and Maps are among the other supported services.
There is an important limitation to the approach. Google Takeout is not a single stable data schema. Different Google products export different formats, and those structures can evolve.
Takeout Reports therefore distinguishes between datasets it has fully measured and cases where only part of a service could be analyzed. According to its developer, partial measurements are explicitly identified rather than silently presented as complete counts.
A read-only explorer for JSON and other Takeout files
The generated report is not the only way to inspect the archive.
Takeout Reports includes a read-only archive explorer for navigating the complete Takeout hierarchy service by service.
Individual files can be opened without first extracting them to disk. An administrator could, for example, inspect the JSON metadata associated with a photo, look at a Calendar record or examine an activity entry directly from the archive.
The read-only model is intentional.
The current release focuses on inspection rather than mutation. It does not attempt to rewrite a Takeout archive or transparently “fix” its contents.
The developer plans additional capabilities including full-archive search, batch export and photo metadata repair. Those features are intended for a later paid version and are not available in the current release.
Reporting and archive navigation are currently free, with no declared limit on archive size or the number of Google services represented.
An offline architecture makes sense for Takeout data
There is also a security argument for avoiding a SaaS architecture in this particular use case.
A complete Google Takeout export can be an unusually concentrated collection of sensitive information. Depending on the services selected, a single dataset may contain email, contacts, documents, browser information, photographs, calendar entries and activity history.
Uploading such an archive to a third-party web service simply to understand its contents creates an additional data-handling problem.
Takeout Reports processes the archive locally.
More unusually, its developer states that the macOS application has no network-access entitlement. In practical terms, the application is designed to operate without network connectivity rather than merely promising not to upload the archive under normal circumstances.
It can therefore perform the same analysis with Wi-Fi disabled.
Color Vivo Internet also says Takeout Reports contains no analytics or application-specific identifiers and does not require an account.
The Mac App Store privacy information currently states that the developer does not collect data. As usual, Apple’s privacy label represents information supplied by the developer rather than an independent security audit.
For administrators, the distinction is still useful: an offline parser substantially reduces the number of systems that need to be trusted with the exported dataset.
It does not, however, remove the need to protect the Takeout archive itself. An unencrypted external disk containing years of Gmail, documents and photographs remains sensitive regardless of whether the application used to inspect it has network access.
Gmail exports lead naturally to MBOX tooling
Email is one area where Takeout Reports deliberately stops short of becoming a complete viewer.
Google commonly exports Gmail messages as MBOX files. Takeout Reports analyzes those mailboxes and provides statistics, but message browsing is handled by Mbox Viewer, another application from the same developer.
Mbox Viewer runs on macOS and Windows and specializes in MBOX and EML files.
The separation creates a relatively clear workflow: Takeout Reports inventories the complete Google export, while Mbox Viewer handles deeper inspection of the email dataset when required.
The latter is optional. Takeout Reports does not require Mbox Viewer to parse the overall export or generate its report.
For developers, the project also has an open-source connection. Mbox Viewer is based on mboxShell, an open-source command-line utility available on GitHub. Takeout Reports itself, however, is distributed as a macOS application and should not be assumed to be open source on that basis.
Google Takeout remains responsible for the export
Takeout Reports does not communicate with Google APIs or replace Google’s export mechanism.
Users still initiate the job through Google Takeout, select the required services and wait for Google to prepare the dataset. Once the resulting archives have been downloaded, Takeout Reports analyzes those local files.
That means there is no Google OAuth flow, no account password and no direct Gmail, Drive or Photos access involved in the analysis.
From an administrative perspective, this creates a useful separation of responsibilities.
Google generates the portable dataset. Takeout Reports performs local discovery and inspection. Specialized tools can then handle whichever data needs to be migrated, converted, indexed or preserved.
The application requires macOS 14 or later, supports Intel and Apple Silicon Macs and is currently available in 18 languages.
Takeout Reports is not affiliated with or endorsed by Google.
Its current value for technical users is less about replacing existing migration tools than providing an intermediate inspection layer. Before writing scripts against thousands of JSON records, importing an enormous MBOX file or allocating hundreds of gigabytes for extraction, an administrator can first establish what the Takeout export actually contains and whether all of its parts are present.
Frequently Asked Questions
Can Takeout Reports inspect a Google Takeout ZIP without extracting it?
Yes. The application reads files directly from ZIP archives. It also supports TGZ archives and previously extracted Takeout directories.
Does Takeout Reports upload Google Takeout data to a server?
According to the developer, no. Processing is local, and the macOS application has no network-access entitlement. It can operate with the Mac offline.
Can it parse Gmail MBOX files?
Takeout Reports analyzes Gmail exports and provides statistics such as message, sender and attachment counts. Detailed mailbox browsing can be handed off to the developer’s separate Mbox Viewer application.
Is Takeout Reports open source?
The available information does not establish Takeout Reports itself as open source. The related Mbox Viewer project is based on mboxShell, an open-source command-line tool, but that should not be interpreted as making Takeout Reports open source.