Google Takeout and Google Location History

Published on June 18, 2026

Contact Mark CV Download

Google Takeout export for Location History returns only “Encrypted Backups”

Some people try to export years of Google Maps Timeline or Location History with Google Takeout and get a surprise. The export finishes, but the downloaded ZIP is tiny and contains no location files.

Instead, it may include only a short text file that says, “You have encrypted Timeline backups stored on Google servers.” This often shows up after your Timeline has moved from account storage to device storage, so Takeout no longer returns the multi-year history you expected. For attorneys working with GPS and cellular data analysis in litigation, I can help them understand the Timeline’s data and explain it in simple language.

To understand why this happens, it helps to know what changed in how Google stores Timeline data. Google’s official Timeline documentation outlines these changes and how they affect data exports.

Why Takeout no longer includes Timeline records after “Timeline on your device” migration

Timeline used to live in your Google account, which made it easy for Takeout to export it. In that older setup, Takeout could include files like Records.json and folders like Semantic Location History because Google stored those records on its servers under your account.

With “Timeline on your device,” Google can migrate that same history to a specific phone.

After migration, the main Timeline dataset becomes device-resident, meaning it is no longer part of the account-level dataset that Takeout exports. Takeout still runs, but it may have no Timeline records to package, so you receive only a message that encrypted backups exist on Google servers rather than the Timeline itself.

Once you see how the older exports were structured, the gap in a post-migration Takeout export makes more sense.

Records vs Semantic Location History

Historically, Takeout produced two different kinds of Location History artifacts, and they served different purposes. Records.json contained raw location points: timestamped latitude and longitude coordinates, plus fields like accuracy and device details. As described in how GPS records function in court cases, analysts often treat this as the closest thing to a sensor-style track log, since it is a long series of points that you can plot or summarize.

Semantic Location History came as monthly JSON files that grouped and interpreted those raw points into higher-level events. These files commonly included activitySegment entries that describe travel between places and placeVisit entries that describe stops, sometimes with names, addresses, and confidence values.

This semantic layer matters because it reflects Google’s interpretation and any user-facing “Timeline” edits that change how a day looks in the app.

Google has not consistently provided clear public documentation for these files, so third-party projects have built schemas and field references to explain the structure and meaning of the exported JSON.

If Takeout no longer gives you these artifacts after migration, you need a different way to get the underlying device Timeline data.

Mechanism for getting raw Timeline data on the new device-based Timeline

If your Timeline lives on your phone, the practical replacement for Takeout is the device export feature.

On Android, the export control sits in system settings rather than inside the Google Maps app. You can find it at Android Settings > Location > Location Services > Timeline > Export Timeline.

The export produces a JSON file that represents your Timeline history from the device. From there, you can load it into your own tools to visualize it on a map or to convert it into a table for analysis.

The exact fields may differ from older Takeout files, but you still get a usable record of where the device says you went. Once you have both the account-era concepts and the device export, you can think about what each source means for analysis and integrity checks.

Account Takeout vs semantic edits vs device export

When you work with Timeline data, it helps to separate raw points from interpreted events.

When edits are made through the Timeline user interface, those changes are reflected in the semantic interpretation layer, the placeVisit and activitySegment entries. The raw point history (Records.json) represents the device’s location samples independently of edits. Understanding the differences between cellular and GPS data helps clarify why the two datasets can show different narratives of the same time period.

That split matters because a cleaned-up Timeline view can look consistent while the raw points still show a different pattern of movement.

When comparing datasets, discrepancies can appear in several forms: confidence or accuracy values in semantic entries that differ from what raw points suggest; timestamp resolution that varies between the two sources; or activity classifications in semantic data that don’t align with the raw point pattern. Documenting these differences helps establish what each dataset represents.

When both raw and semantic data are available, comparing them can reveal where the two sources diverge in their description of location and timing. This comparison helps identify technical differences between device-reported movement and Google’s interpreted events.

After migration to device-based Timeline, Takeout may omit the usable location history and leave only the encrypted-backup note, so a Takeout-only workflow can miss the dataset you need. In that situation, you often need the device export for completeness, and then you can decide what comparisons remain possible given the formats you have.

That leads to a simple decision about which export path fits your current Timeline storage state.

Choose your export path

The choice of export method depends on the current storage state of the Timeline. If Timeline remains account-based, Google Takeout‘s Location History export can provide Records.json and monthly Semantic Location History files. For detailed guidance, see Google’s Takeout help documentation. If Timeline has migrated to device storage and Takeout returns only the “Encrypted Backups” notice, the device export method at Android Settings > Location > Location Services > Timeline > Export Timeline becomes the available source.

After exporting, the next step depends on the intended use case.

If you want a map, you can load the JSON into a visualization tool.

If you want a spreadsheet, you can convert the JSON to CSV.

If you want to compare datasets, you can compare raw-style location points against semantic-style interpreted events when you have both. Understanding how GPS receiver accuracy affects location evidence is essential when evaluating these comparisons. You can also use third-party format references to understand the fields in whichever artifact you obtained.

Contact Mark CV Download