Back Up Google Photos to pCloud Without Takeout
· 4 min read · Updated

This move comes up more than any other: a Google Photos library out of Google and into a pCloud lifetime plan. The transfer is what breaks, and it breaks at the same steps almost every time.
The manual route starts with Google Takeout. You request an export and wait hours, sometimes days, for a pile of zip files. Each item arrives next to a JSON sidecar that holds Google's metadata, and you extract the zips. For the minority of files that need it, you merge that sidecar back into the files with an EXIF tool. Then you upload the result to pCloud, and when the upload breaks partway, you work out what happened and try again.
For a big library that takes days, which is why so many pCloud lifetime plans sit mostly empty.
Takeout does not break dates for most photos. Files uploaded at original quality keep their own EXIF, including the capture date, and a plain copy preserves it. The JSON sidecar is extra.
The metadata fix applies only to a subset: photos edited in Google Photos, which download as re-encoded files, and files that never had an embedded capture date, such as screenshots, downloaded images and forwards[1]. For those, the reliable date lives in Google's JSON. Most libraries are mostly original files, so the fix is a minority concern. The guide to downloading Google Photos without JSON files lists those cases and what to check after a download.
So a transfer tool should pass each file through unchanged. The date embedded in the file then arrives with it, and there is no merge step. Blober works that way: it reads each file as Google serves it and writes it to pCloud without stripping anything.
rclone used to list and download a Google Photos library. Google changed its API policy in March 2025, and since then rclone can only download photos it uploaded itself[2], which leaves an existing library out of reach. Transfer services that run on your behalf face the same limit, or they meter how much data you can move per month.
For a library you built through the Google Photos app or the web, a direct path to pCloud needs a tool that reads Google Photos the way the service exposes it and supports pCloud on the other side.
Blober is a desktop app for Mac, Windows and Linux with a Google Photos provider and a pCloud provider, so the Takeout step drops out of the job. It reads the library through the Google Photos provider and writes each photo and video to pCloud unchanged, with no Takeout archive, zip extraction or sidecar step. If the connection drops, the transfer resumes on its own, and files already copied stay done. A path template can also sort the photos into date folders, one per day (YYYY-MM-DD), instead of one flat folder.
If your pCloud account is on the EU data center, Blober picks that up during authorization and uses it for the transfer. There is nothing to configure.
To start, connect Google Photos and pCloud, then create a workflow with Google Photos as the source and pCloud as the destination. Select the whole library or the photos you want, pick the pCloud folder, and run it.
For the general case of downloading Google Photos without Takeout, see how to backup Google Photos without Google Takeout.
Will the photo dates survive the move? For files with an embedded date, yes. Blober passes each file through unchanged, so the capture date in the file comes along. It does not strip or rewrite anything.
Do I still need exiftool or a script? Not with Blober. The metadata fix only matters for edited photos and files without an embedded date, a minority in most libraries. Blober transfers each file as it is, so files that already carry their date need nothing extra.
What happens if my connection drops halfway? Blober keeps per-file progress. When you resume the task, the files that already transferred stay done and the rest continue.
Does this work with a pCloud lifetime plan? Yes. Blober connects to the account the same way regardless of how you pay for it.
My pCloud account is on the EU servers. Do I need to do anything? No. Blober finds your account's data center when you authorize.
Do I need to create my own pCloud app? No. Blober pre-fills its pCloud app keys, so you authorize in seconds without creating an app or waiting for a review. If you prefer your own app, the pCloud guide covers that too.
I still want to use Takeout as a fallback. Does that work? It works, but you are back to the manual route: batches, zip extraction, and a metadata fix for the files that need one.