PhotoFixer

How to Move Google Photos to Ente

By Josep Mampel Marques, updated

The way to move Google Photos to Ente is to export a Takeout with only Google Photos, unzip every part into one folder, then use the Ente desktop app: click Upload and choose Google takeout. Ente reads the .json sidecar files and takes the dates, locations and descriptions from them, and it detects album copies so one original is stored. This is Ente's own documented route, so for Ente alone you do not need to fix anything first. A fixed copy on disk is still worth having as a backup that does not depend on any app.

Ente's recommended steps

  1. Export. At takeout.google.com click Deselect all, select only Google Photos, and choose Export once, the .zip type and the largest file size you can handle. Google emails you when it is ready, which Ente says can take hours or days.
  2. Download every part. Ente warns that importing only some of the parts can give those photos the wrong date. A .crdownload file is an unfinished download, not a finished zip.
  3. Unzip into one parent folder. Extract all zips into a single folder and keep Takeout's subfolders intact: Ente uses that layout to match photos with metadata.
  4. Import in the desktop app. Open Ente, click Upload and select Google takeout.

For help with the export itself, see how to download Google Photos with Takeout.

Folder or zip files

Unzipped folderZip files
Ente's adviceRecommendedWorks, but riskier
Metadata matchingUses Takeout's folder layoutMay fail if a photo and its .json are in different zips
AlbumsExisting or new albums; separate or singleCreated automatically from the folder structure

The split between zips is not a bug: see why a Takeout has several zip parts.

Import options and caveats from Ente

When to fix the files first

Ente's help says metadata goes missing mainly when a .json is separated from its photo, and an import never rewrites dates it has already set. If you want a clean copy that works anywhere, run the Takeout through PhotoFixer before importing. It reads all the zip parts in your browser without uploading anything, writes the date, location and description into JPEGs that lack them, sets the creation date on MP4 and MOV videos, gives every file its capture time as the file date and removes duplicate album copies. HEIC is copied unchanged. You can then import the unzipped result into Ente, or keep it as an independent backup.

One caution: Ente's help describes importing the Takeout layout (photos beside their .json files) and does not describe importing a folder of already fixed photos, so try a small subset first and check the dates in the app.

Compared with other routes

Ente's own article on exporting Google Photos covers the Takeout side. If you are weighing self-hosting instead, see Google Photos to Immich.

FAQ

Does Ente read the Google Takeout .json files?

Yes. Ente's migration help says it reads the JSON sidecar files in the Takeout, matches them to photos and videos, and takes dates, locations and descriptions from them.

Should I import the zips or the unzipped folder into Ente?

Ente recommends the unzipped folder. It says that if Google splits a photo and its metadata across different ZIPs the match may fail when importing zips, and that the unzipped folder is the safer choice.

What happens to my duplicate album copies in Ente?

Ente's help says Takeout copies a photo in several albums into each album folder, and that Ente detects these copies and stores one original.

Sources