Google Takeout is the primary tool for users who want to regain control over their digital memories. Whether the goal is to switch to a different cloud provider, create a physical backup on an external hard drive, or simply reduce the amount of storage used in a Google account, understanding the mechanics of this tool is essential. It is important to clarify at the outset that Google Takeout creates a copy of your data; it does not move or delete the original files from your Google Photos library.

The process of exporting tens of thousands of images is more complex than a simple "download all" button. From managing split ZIP files to handling the notorious JSON sidecar files that store your metadata, a successful export requires a structured approach.

How to Set Up a Google Photos Export via Takeout

Initiating an export is a multi-step process that begins at the official Google Takeout interface. While the tool is designed to be comprehensive, selecting the wrong options during setup can lead to broken downloads or missing albums.

Step 1: Selecting the Data Source

Upon visiting the Takeout website, the first thing most users notice is the sheer number of Google services selected by default. To focus exclusively on photos, users must first click "Deselect all" at the top of the list. After scrolling down to find Google Photos, check the corresponding box.

Within the Google Photos section, there is an option labeled "All photo albums included." This is a critical junction. By default, Google includes every auto-generated "Photos from [Year]" folder and every custom album created by the user. If the goal is a complete backup, leaving this as is remains the best choice. However, if space is limited on the local machine, clicking this button allows for the selection of specific years or specific curated albums.

Step 2: Choosing the Frequency and Destination

After clicking "Next step," the system offers choices for how the data should be delivered.

  • Delivery Method: The most common choice is "Send download link via email." Once Google finishes preparing the archive, an email arrives with links to the files. Other options include adding the archive directly to Google Drive, Dropbox, OneDrive, or Box. Note that adding to Google Drive still consumes storage space until the archive is downloaded and deleted.
  • Frequency: For a one-time migration, "Export once" is the correct selection. For users who want an ongoing backup strategy, "Export every 2 months for 1 year" automates the process, though it does not perform incremental backups—it re-exports the entire library each time.

Step 3: Determining File Type and Size

Google allows for the selection of the archive format and the maximum size of individual files.

  • File Type: The .zip format is the standard for most users because it is natively supported by Windows and macOS. The .tgz format is an alternative typically preferred by Linux users or those comfortable with advanced compression tools.
  • Archive Size: This is a major pain point for large libraries. Options range from 1GB to 50GB. If a library is 100GB and the user selects 2GB, Google will generate 50 separate ZIP files. Selecting 50GB results in fewer files but requires a very stable internet connection. In practice, 10GB or 50GB segments are often more manageable for modern broadband speeds, provided the browser's download manager can handle large streams.

The Metadata Challenge: Understanding JSON Sidecar Files

The most frequent complaint after using Google Takeout is that the exported photos appear to have lost their "Date Taken" or "Location" information. When viewing these photos in a standard file explorer, the "Date Created" often reflects the day the ZIP file was downloaded, rather than the day the child took their first steps or the family went on vacation.

What is a Google Takeout JSON file?

When Google exports a photo, it often strips specific metadata from the image header and places it into a separate text file with a .json extension. For every IMG_1234.jpg, there is a corresponding IMG_1234.jpg.json.

This JSON file contains:

  • The original "Photo Taken Time."
  • Descriptions or captions added within the Google Photos app.
  • Geographical location tags (GPS coordinates).
  • Adjusted timestamps if the user manually changed the date within Google’s interface.

Standard photo viewers and operating systems do not automatically read these JSON files. They look only at the EXIF data embedded within the image file itself. If the EXIF data was stripped or was never there to begin with (as is common with photos saved from social media), the image appears "date-less."

How to fix Google Photos metadata after export?

To restore the metadata, the information in the JSON files must be "merged" back into the JPG or MP4 files. This is not something that can be done manually for thousands of photos. Users typically rely on third-party metadata fixers.

In our testing, these tools look for a JSON file with a matching name, extract the "Timestamp" field, and write it into the image's EXIF header. Without this step, migrating to a new service like Apple Photos or a self-hosted solution like Immich will result in a disorganized mess of photos sorted by the download date.

Structural Realities of the Exported Folders

Once the ZIP files are extracted, the folder structure can be confusing. Google organizes the export based on the albums defined in the library.

  1. Yearly Folders: If photos were not part of a specific album, Google places them in folders like "Photos from 2022."
  2. Album Folders: Custom-named albums will have their own dedicated folders.
  3. Duplication: A significant issue in Google Takeout is file duplication. If a single photo exists in three different albums, it will be exported three times—once in each album folder. This can cause the total size of the export to be much larger than the "storage used" reported in the Google account.
  4. Shared Content: Only photos that have been explicitly "Saved to Library" from shared albums will appear in a Takeout export. If a user can see a photo in their feed because a partner shared it, but they haven't clicked the "Save" icon, that photo will be missing from the export.

Technical Limitations and Reliability Issues

Using Google Takeout is not always a smooth experience, especially for users with terabytes of data. There are several technical hurdles to anticipate.

Download Time and Expiration

Google does not generate the archive instantly. Depending on the size of the library, it can take anywhere from a few hours to several days. Once the archive is ready, the download links are typically only valid for seven days. If a user misses this window, they must restart the entire export process from scratch.

Browser Interruptions

Downloading a 50GB file through a standard web browser is risky. If the internet connection flickers, the browser may fail to resume the download, leading to a corrupted file. For very large exports, using a dedicated download manager that supports "resume" functionality is highly recommended.

Extraction Errors

Occasionally, users report "Compressed Folder is Invalid" errors when trying to open the ZIP files. This usually happens when one part of a multi-part ZIP archive is missing or hasn't finished downloading. It is vital to ensure every numbered part of the export is present in the same local folder before attempting extraction.

Alternatives to Local Downloading

For those who find the ZIP/JSON process too technical, Google has introduced "Direct Transfer" options. This allows users to move their library directly to services like Apple iCloud, Microsoft OneDrive, or Flickr without downloading anything to a personal computer.

Moving Google Photos to Apple iCloud

This is an official integration. After selecting iCloud as the destination in Takeout, the user signs into their Apple ID and authorizes the transfer.

Observations from the direct transfer process:

  • Live Photos: Sometimes, the video component of a Live Photo does not sync perfectly, resulting in a static image in iCloud.
  • Storage Requirements: The destination (iCloud) must have enough empty space to accommodate the entire Google library before the transfer begins.
  • Speed: While the user doesn't have to stay online, the "Cloud-to-Cloud" transfer can still take days to complete in the background.

Google Takeout is Not a Data Recovery Tool

A common misconception is that Google Takeout can be used to recover photos that were accidentally deleted. It is important to emphasize that Takeout only exports data that currently exists in the account at the time the export is initiated.

If a photo was deleted and the 60-day trash window has passed, the photo is permanently removed from Google’s servers. Google Takeout cannot "go back in time" to retrieve these items. It is a tool for portability and backup of existing data, not a forensic recovery utility.

Managing Local Storage After Export

Before initiating a large export, users must ensure they have enough local storage. A 200GB Google Photos library might require 300GB to 400GB of local space during the process:

  1. Space for the downloaded ZIP files.
  2. Space for the extracted photos and JSON files.
  3. Space for the final "fixed" versions of the photos if using a metadata merger tool.

Once the metadata is fixed and the integrity of the photos is verified, the original ZIP files and the JSON sidecar files can be safely deleted to reclaim space.

Conclusion

Google Takeout is a powerful, though unpolished, tool for data sovereignty. It provides the necessary files to move away from the Google ecosystem or create a redundant backup, but it requires users to handle the "last mile" of data management—specifically the merging of JSON metadata and the organization of duplicated files.

By choosing larger archive sizes (to minimize the number of files) and using dedicated metadata tools to fix timestamps, users can successfully transition their memories to a new home without losing the chronological order that makes a photo library valuable.

FAQ

How long does Google Takeout take?

For small libraries (under 10GB), it usually takes 2 to 5 hours. For libraries exceeding 500GB, it can take 2 to 3 days for Google to prepare the download links.

Does Google Takeout delete my photos?

No. Google Takeout only creates a copy. Your original photos remain in Google Photos until you manually delete them to free up storage space.

Why are there so many JSON files in my Google Takeout?

Google uses these files to store metadata that isn't always embedded in the image, such as captions, tags, and location edits made within the Google Photos app.

Which is better, ZIP or TGZ?

ZIP is better for most users because it is easily opened on Windows and Mac without extra software. TGZ is optimized for Linux and can sometimes be slightly smaller in size.

Can I choose to only export specific people?

No. Google Takeout allows selection by "Album" or "Year," but it does not currently support exporting based on "People" or "Faces" identified by AI.

What happens if a download fails midway?

If the download link is still valid (usually for 7 days), you can simply restart the download for that specific part. If the link has expired, you must request a new export.

Is there a limit to how many times I can use Google Takeout?

Google limits the number of exports you can request per day and per week, though these limits are typically high enough that they do not affect individual users performing a standard backup.