Apple and Google have expanded their data portability partnership to allow a direct transfer of your Google Photos library into iCloud Photos — no manual downloading, re-uploading, or third-party tool required. It’s the reciprocal counterpart to an existing iCloud-to-Google-Photos transfer that’s been available since 2024, and it closes a gap that made switching between the two ecosystems needlessly painful for years.
If you’ve been holding off on consolidating your photo library because the migration itself felt like the obstacle, this is the moment that obstacle mostly disappears. It’s also a good prompt to think about what you actually want your “master” photo library to be, rather than just defaulting to wherever your photos happen to already be sitting.
How the Transfer Tool Actually Works
The tool is powered by the Data Transfer Project — an open-source technology stack built specifically to move data directly between major platforms, developed under the Data Transfer Initiative, of which Apple and Google are both signatories. You initiate the transfer from your Google Account’s data export settings, and Apple’s side handles the import into iCloud Photos.
Apple states the transfer carries over each photo or video file along with its associated metadata: filename, description, file type, and location data. You can track the status of an in-progress transfer, or cancel it, from Apple’s Data and Privacy page. The whole process typically takes between three and seven days, depending on library size.
This direct transfer replaces what used to require manually downloading your entire Google Photos library through Google Takeout and re-uploading it to iCloud — a process that was slow, easy to mess up, and prone to losing metadata along the way.
Why This Took So Long to Exist
Photo libraries have historically been one of the stickiest forms of platform lock-in. Unlike a document or a spreadsheet, a photo library accumulates passively over years, gets entangled with a platform’s specific organizational features — albums, face groupings, “memories” reels — and grows large enough that manually moving it somewhere else feels like a project rather than a setting change. That stickiness was, for a long time, good for the platforms holding the library and mildly bad for the user who might otherwise want options.
The Data Transfer Initiative, formed in 2023 with Apple, Google, Meta, and others as founding members, exists specifically to chip away at that dynamic, partly in response to regulatory pressure — the EU’s Digital Markets Act and similar data-portability rules elsewhere have pushed large platforms toward making this kind of transfer technically possible, not just promised. The first version of this transfer (iCloud to Google Photos) shipped in 2024; the reciprocal direction took roughly two more years to arrive, which says something about how much lower a priority reciprocity is than the regulatory minimum a platform is required to meet.
A Step-by-Step Walkthrough
1. Start from your Google Account’s data transfer settings, where the option to transfer your Google Photos library to iCloud Photos now appears alongside other export and portability options.
2. Sign in to confirm the destination iCloud account, since the transfer needs to authenticate on both sides — your Google account as the source, and the iCloud account you’re sending the library to.
3. Review the transfer scope before confirming. Some implementations let you select specific albums or date ranges rather than transferring the entire library; check whether that option is available if you only want to move part of your collection.
4. Confirm and wait. The transfer runs in the background over the stated three-to-seven-day window — there’s no need to keep the app open or the device active for the duration.
5. Track or cancel from Apple’s Data and Privacy page, which shows live status and gives you a way to stop the transfer if you change your mind partway through.
What Actually Moves — and What’s Worth Double-Checking
Core files and basic metadata transfer reliably. The photo or video itself, along with filename, file type, and location data where present, is part of the documented transfer scope.
Organizational structure is the part to verify, not assume. Albums, shared album memberships, comments on shared photos, and any edits made through Google-specific tools don’t necessarily carry the same fidelity across to iCloud’s organizational model, since the two platforms structure photo libraries differently. If you’ve built out carefully organized albums in Google Photos, check what actually landed on the iCloud side after the transfer completes, rather than assuming a one-to-one match.
Duplicate handling deserves a look if you’ve used both services before. If you’ve ever had iCloud Photos and Google Photos both partially syncing your camera roll — a common situation for anyone who’s switched phones or used both ecosystems casually — the transfer may introduce duplicates that are worth a manual pass to clean up.
A Pre-Transfer Checklist
1. Confirm you have enough iCloud storage headroom before starting. A failed or partial transfer due to insufficient destination storage is an easy, avoidable problem — check your iCloud storage tier against your Google Photos library size before you begin, and upgrade beforehand if needed.
2. Don’t delete anything from Google Photos until you’ve verified the transfer on the other end. Keep your source library intact until you’ve confirmed photo counts, spot-checked a few albums, and are confident the migration completed cleanly. Transfers of this kind are not designed to be reversible in the sense of pulling content back automatically if something goes wrong.
3. Spot-check albums and shared content specifically, since that’s the part most likely to need manual cleanup, rather than the photos themselves.
4. Check for duplicates if you’ve previously used both services. A quick manual sort after the transfer completes is faster than trying to prevent every duplicate from occurring during the migration itself.
If You’ve Used Both Services for Years
A specific situation is worth calling out separately: people who’ve owned both an Android and an iPhone at different points, or who’ve kept both apps installed “just in case,” often have overlapping partial libraries on each platform already. For this group, the transfer tool isn’t a clean migration from one empty destination — it’s a merge between two libraries that already have years of overlapping content.
In that case, expect a larger duplicate-cleanup task than the general case, and budget extra time for it after the transfer completes. Several third-party duplicate-detection tools exist for exactly this scenario, and running one after the transfer — rather than trying to manually compare two multi-thousand-photo libraries — is the more realistic approach.
The Bigger Question a Migration Like This Should Raise
It’s worth being clear-eyed about what this transfer tool actually accomplishes: it makes switching between two ecosystems that both run AI features over your photo library easier. That’s a genuine convenience win — reduced lock-in is good for users regardless of which platform they end up on — but it isn’t, by itself, a privacy upgrade. Both Google Photos and iCloud Photos process your library for their own AI-driven features (search, face recognition, “memories” surfacing) unless you specifically opt out where that’s possible, and migrating from one to the other doesn’t change that dynamic — it just changes which company is doing it.
If part of your motivation for moving is wanting more control over where your photos live and what’s done with them, a transfer between two large ecosystem platforms is a good moment to also make a third move: exporting a copy to storage that isn’t trying to be an AI feature platform at all.
What Reciprocity Actually Signals
It’s worth naming the irony in this announcement: a transfer tool that makes it easier to leave Google Photos is something Google had every business incentive to delay, and one that makes it easier to leave iCloud is something Apple had the same incentive to delay. That both companies built and shipped the reciprocal version anyway is less a sign of newfound generosity than a sign of how much regulatory and competitive pressure has shifted the cost-benefit calculation on data portability over the past few years.
That’s a genuinely good development for users regardless of motive. But it’s also worth remembering that the underlying incentive to keep your library on one platform hasn’t disappeared — it’s just been forced to compete with a now-easier exit option. Don’t mistake “switching is now easy” for “the platform wants you to feel free to leave.” The tool exists because portability rules and reciprocity commitments required it to, not because lock-in stopped being valuable to either company.
Where a Neutral Copy Actually Helps
A migration like this is, practically, the easiest moment to also establish an independent backup — you’ve already got your library in a transferable, organized state, which is exactly the condition that makes a parallel export low-effort.
daftei is built to be that neutral copy: a dedicated storage app, not a photo-AI platform, available on iOS, Android, and the web, with 5 GB free and unlimited storage on Pro. Files are encrypted in transit with TLS 1.3 and at rest with AES-256, and daftei never trains AI on your content and never sells your data — so the photos you store there aren’t subject to whichever platform’s AI roadmap happens to change next. Whichever ecosystem you land in after this transfer, having a copy somewhere that isn’t trying to do anything with your photos beyond storing them is a reasonable insurance policy against the next migration you might someday want to make.