← All sync guides

Sync guide

Move Google Photos to Proton Drive Without Unzipping Takeout

Copy a Google Photos Takeout export into Proton Drive straight from the .zip files โ€” no unzipping, no second copy on your disk, and each photo dated by when it was taken. Compared honestly with Proton's own Google Photos import.

Cloud transfer Local data path rclone GUI
Overview

Proton Drive can import Google Photos by itself, but only after you unzip every Takeout part, which means finding free disk space for a second copy of your whole library. This guide compares Proton's built-in import with OurClone, which reads the .zip parts where they are and copies the photos into a Proton Drive folder sorted by year, each file dated by the capture time Google recorded.

Proton's Import Fills the Timeline, OurClone Fills a Folder

Proton Drive has two places a photo can live. The Photos section is a timeline with albums, filled by Proton's photo uploads and its Google Photos import. My files is ordinary folder storage, and a picture copied into a folder there stays in that folder; it doesn't appear in the Photos timeline. Which place you want decides which route fits.

  • ๐Ÿ–ผ๏ธ You want to scroll your photos in Proton Photos โ€” Use Proton's own import (Method 1). It is the only way into the timeline from a Takeout export.
  • ๐Ÿ—„๏ธ You want the whole library archived in Proton Drive โ€” Use OurClone (Method 2). It copies straight from the downloaded .zip files into a folder you choose, so you never need room for an unzipped copy.

Both start from the same thing: a Google Takeout export of Google Photos. Neither route touches your Google account, so you can try one and still use the other.

The Hidden Cost of Unzipping: Disk Space

Takeout delivers a large library as numbered .zip parts, anywhere from 1 GB to 50 GB each depending on the size you picked. Proton's import reads folders, not .zip files, so its instructions start with unzipping every part. While you do that, your computer holds the archives and the extracted copy.

Bar chart: moving a 300 GB Google Photos export with Proton's import needs about 600 GB of free disk space for the .zip parts plus the unzipped copy; OurClone needs only the 300 GB of .zip parts

On a laptop with a 512 GB drive, that difference decides whether the move happens at all. Working one part at a time keeps the peak lower, but every part then becomes its own round of unzipping, importing and deleting.

The Two Routes Side by Side

Proton's Google Photos importOurClone
Where the photos end upProton Photos (timeline; albums with the Windows app)A folder in My files, sorted into year folders
Unzip firstYes, every partNo, the .zip parts are read in place
Free disk space during the move.zip parts plus the unzipped copy.zip parts only
On a MacWeb app (drag the unzipped folders in); the desktop import is documented for WindowsMac and Windows apps
Google albumsWindows app creates albums from the foldersOptional: copy album folders as well (they hold second copies)
Capture dates from Google's JSONNot described in Proton's documentationUsed as each file's modification time; the photo files themselves are unchanged
DuplicatesWindows app skips duplicatesEach photo stored once; running the copy again uploads only what's missing

Method 1: Proton's Built-in Google Photos Import

The steps below follow Proton's support article.

Diagram of Proton's Google Photos import: download every Takeout .zip part, unzip all of them into Takeout folders, then import through the Proton Drive web app's Photos tab or the Windows app's Import from Google Photos

A diagram of the steps in Proton's support article; Proton's own screens look different.

  1. ๐Ÿ“ฆ Export Google Photos โ€” At Takeout, select only Google Photos, keep the .zip file type, create the export and download every part from the email Google sends (the links last a week).
  2. ๐Ÿ—œ๏ธ Unzip every part โ€” Proton recommends tidying the extracted photos into year folders first, because Takeout can spread one year across several parts.
  3. โฌ†๏ธ Import โ€” In the web app, drag the unzipped folders into the Photos tab and they appear in the timeline. In the Windows app, choose Import from Google Photos under Photos import and select each folder; it builds albums from the folder structure and skips files it already has. Files that aren't photos or videos, such as Google's JSON files, are ignored.

Unzipping is where it gets fiddly. Every part contains its own top-level Takeout folder, so on a Mac three parts become Takeout, Takeout 2 and Takeout 3, and the same year can turn up in more than one of them.

Finder showing three Takeout .zip parts unzipped into Takeout, Takeout 2 and Takeout 3, with Photos from 2020 appearing in two different parts

In the web app the import happens on the Photos page, not in My files: drag the unzipped folders onto it, or use Upload photos. There is no separate Google Photos button on the web; that option lives in the Windows app.

The Photos page in the Proton Drive web app with Photos and Albums tabs, an Upload photos button and an Upload button on the empty timeline

Proton's announcement listed the desktop import for macOS as coming soon, so on a Mac check whether your Proton Drive app offers it before planning around the web app.

Method 2: Copy the Takeout .zip Files to Proton Drive with OurClone

OurClone opens the export as a read-only storage called Google Photos (Takeout), reading photos out of the .zip parts as they're needed and pairing each one with its JSON file. You need OurClone v1.5.0 or later on Mac or Windows (download page). The free plan allows two storages, which is exactly what this takes: the export and Proton Drive.

  • ๐Ÿ“ฆ Step 1: Export Google Photos as .zip โ€” Same as above: Takeout, Google Photos only, file type .zip (the .tgz option can't be read). Larger parts mean fewer downloads. Put every part in one folder you won't reorganize, because OurClone reads them from there.
  • ๐Ÿ—‚๏ธ Step 2: Add the Export โ€” In the Add tab choose Google Photos (Takeout) and drop all the parts into the dialog. Each archive is checked before anything is added: incomplete downloads are flagged, a missing part number is pointed out, and the total shows photos, videos and albums with duplicates counted once. Click Add Remote.
  • The Add Google Photos (Takeout) dialog in OurClone with three .zip parts checked and a total of 2,431 photos, 118 videos and 23 albums
  • ๐Ÿ” Step 3: Connect Proton Drive โ€” Back in Add, pick Proton Drive and sign in with your Proton email and password. If your account uses two-factor authentication, enter the current code in the 2fa field. Click Confirm.
  • The Authorize Access to your Proton Drive dialog in OurClone with Remote Name, Email, Password and an optional 2fa field
  • ๐ŸŽ›๏ธ Step 4: Choose Library as the Source โ€” Open Migrate. On the source side pick the Takeout storage and select Library: it holds every photo and video exactly once, in year folders. On the destination side pick Proton Drive and a folder (you can create one in the picker). Keep Copy selected and click Start Transfer.
  • OurClone Migrate page copying google-photos:/Library to proton:/Google Photos with Copy selected

    Copying the export's top level would also upload the Albums folder, where every album holds second copies of photos already in Library.

  • ๐Ÿ“ˆ Step 5: Let It Run โ€” The Task panel shows progress until the job reads Completed. Proton Drive encrypts each file on your computer before upload, so expect a large library to take hours; keep OurClone open and the computer awake. If a run stops halfway, click Run again and only the files that aren't in Proton Drive yet are uploaded.
  • The OurClone Task Center showing the copy from google-photos:/Library to proton:/Google Photos completed, 2,549 of 2,549 items

Avoid Sync for this job. Sync makes the destination match the source exactly, so anything else you later put in that Proton Drive folder would be deleted on the next run. Move isn't offered because the export is read-only.

What You'll Find in Proton Drive Afterwards

  • ๐Ÿ“… Year folders โ€” 2017, 2018 and so on, by the capture year in your time zone. Items Google had no date for are filed by Google's own year folder, or under Unknown if there is none.
  • ๐Ÿ•’ Capture time as the file date โ€” Each file is uploaded with its modification time set to the capture time from Google's JSON, including dates you corrected in Google Photos; items without one get the export time. The photo files are copied byte for byte, so the EXIF inside them is not rewritten.
  • ๐Ÿงพ No JSON clutter โ€” Google's metadata files stay behind, and photos Google marked as in the trash are left out.
  • ๐ŸŽž๏ธ Every format as-is โ€” Unlike an import into a photo app, nothing is skipped for its format: HEIC, RAW, MKV or AVI files are copied like any other file. A Live Photo arrives as its two halves, the image and the short video, side by side.
  • ๐Ÿ’ฌ No captions โ€” Google's photo descriptions live in the JSON and aren't carried over.

Want your albums too? Run a second Copy with a single album under Albums as the source and its own destination folder. Each album folder stores another copy of its photos, so pick the ones that matter rather than the whole Albums folder if your Proton storage is tight.

If Something Goes Wrong

  • ๐Ÿค– "Proton needs to verify you're human" โ€” Proton sometimes asks for a CAPTCHA when a new app signs in. That's not a wrong password. Sign in to Proton once in your browser, come back and click Confirm again, and don't retry over and over, because Proton then blocks sign-ins for longer.
  • ๐Ÿข Uploads are slow โ€” Encryption on your computer plus Proton's upload pace make this slower than copying to a plain cloud. OurClone connects through rclone's Proton Drive backend, which rclone itself still labels beta; start with one year folder to see the speed you get.
  • ๐Ÿ’พ Proton storage fills up โ€” Uploads start failing once the account is full, and the Task panel lists the files that didn't make it. Free up space or upgrade, then click Run again; files already uploaded are skipped.
  • ๐Ÿงฉ A part is missing โ€” Download it, add it from the Takeout storage's Archives button in Manage, and run the copy again.
  • ๐Ÿ“ The .zip files were moved โ€” The storage reads them from where they were when you added them. Move them back, or remove the storage and add it again from the new location.

Quick Answers

Will these photos show up in Proton Photos?

No. They're files in a My files folder. If you want them in the timeline, use Proton's import for that part of the library.

Do I need to keep the .zip files after the copy?

Only until you've checked the result in Proton Drive. After that you can delete them, or keep them as an offline copy. The Takeout storage in OurClone stops working once they're gone.

Can I send the same export somewhere else as well?

Yes. The Takeout storage works as a source for any storage OurClone connects to, such as pCloud, a NAS over SFTP or SMB, or an external drive. On a Mac it can also import into the Photos app with albums and Live Photos restored.

Does OurClone see my Google password or my Proton files?

It never signs in to Google; it only reads the .zip files you downloaded. Your Proton sign-in is used on your computer to reach your own Drive, and the copy runs from your computer straight to Proton.

Summary

Use Proton's own import if you want your photos in the Proton Photos timeline and can spare the disk space to unzip the export. Use OurClone to archive the library into a Proton Drive folder straight from the .zip files: nothing is extracted, each photo is stored once in a year folder, and its file date is the capture time from Google's JSON. Nothing changes in your Google account either way.

Try OurClone free

Connect your clouds, transfer across them, mount remotes as local folders, and create encrypted restic backups from one desktop app.

The macOS download is for Apple Silicon (M1 or later). Using an Intel Mac? Download the Intel version

See Free vs Pro plans →