How to Merge Google Photos from Two Accounts Using Partner Sharing (Correctly)

You have two Google accounts, and both are full of photos — an old account from a previous phone, a new one you use now. Google offers no “merge accounts” button, but Partner Sharing comes remarkably close, provided you set up the one option everyone misses: auto-save on the receiving side.

Done wrong, Partner Sharing just lets one account view the other’s photos, and the day the old account is deleted, the “merged” library vanishes with it. Done right, the photos are copied into the second account permanently. The difference is a single setting, applied in the right order.

Quick Answer

From the OLD account, share your library with the NEW account via Partner Sharing (Settings, Sharing, Partner Sharing), choosing all photos from the earliest date. Then, in the NEW account, open the sharing settings and turn on Auto-save for the partner’s photos, set to save everything. The new account then copies every shared photo into its own library, where it stays even if the old account is later deleted. Allow days for a large library to copy, and verify counts before touching the old account.

How Partner Sharing Actually Works

Partner Sharing is designed for couples: one partner sees the other’s photos in their own library view. Crucially, viewed photos are not owned copies — they still live in the sharing account. The auto-save feature changes that: with auto-save on, every photo shared with you is also saved into your library as your own copy. That copy counts against your storage (with a nuance covered below) and survives independently. Google explains the mechanics in Google Photos Help, and the details matter, so the sequence below follows them precisely.

Set It Up in the Right Order

1. In the OLD account: open Google Photos, go to Settings, Sharing, Partner Sharing, and invite the NEW account. When asked which photos to share, choose “All photos” and the earliest start date offered — a start date set to the partnership’s beginning would exclude your older history, which is precisely the stuff you are merging.
2. In the NEW account: accept the invitation. The old account’s photos now appear in your library view, mixed with your own.
3. Immediately turn on auto-save in the NEW account: Settings, Sharing, Partner Sharing, then the option to save your partner’s photos — select all photos (you can include or exclude photos of specific people; for a merge, include everyone).
4. Wait. Auto-save works through the backlog progressively. A library of tens of thousands can take days, processing in the background. Leave both accounts alone; do not delete anything on either side during this period.
5. Verify the merge: compare the total photo counts. The new account’s library should approach the sum of both accounts (minus genuine overlaps). Search for specific old photos by date — scroll to your earliest years and confirm they are present, and open a few at full size.
6. Only after verification, decide the old account’s fate. Keeping it dormant for a few weeks costs nothing and is the safest option of all.

Storage and Other Fine Print

Saved partner photos generally count toward the receiving account’s storage quota, except photos shared in “Original quality” arrangements between certain Pixel-era accounts historically had exceptions — check your storage page after the merge rather than assuming. Make sure the new account has enough quota (a Google One plan if needed) before starting, or auto-save will stall when the account fills. Also know the limits: you can have only one partner at a time, some content (such as photos from other people shared onward, or certain motion-photo companions) may not copy perfectly, and albums are not transferred as albums — the photos arrive, the organisation does not. If the merged result contains doubles where both accounts held the same shots, our guide to removing thousands of duplicate photos after merging libraries covers the cleanup.

The Alternative: Google Takeout

For a colder, more archival merge, export the old account entirely with Google Takeout, download the archives, and upload the photos into the new account. Takeout preserves original files and sidecar metadata, but uploads can scramble dates if the metadata handling goes wrong, and very large libraries mean very large downloads. Partner Sharing with auto-save is gentler and keeps everything inside Google Photos; Takeout is the better choice when you also want an offline archive of the old account — which, honestly, is worth having regardless.

Common Mistakes to Avoid

• Forgetting auto-save. Sharing without auto-save is a window, not a copy. Deleting the old account then deletes everything you thought you merged.
• Setting a recent start date. Partner Sharing can be limited to photos from a chosen date. For a merge you want the earliest possible date and all photos, or your oldest years stay behind.
• Deleting the old account during the copy. Auto-save needs the source alive. Wait for verification, then wait a little longer.
• Running out of storage mid-merge. The receiving account fills, saving stops, and the failure is quiet. Check quota before you start and monitor during.
• Expecting albums to transfer. Photos merge; album organisation does not. Rebuild key albums in the new account after the merge settles.

What Does Not Come Across (and How to Handle It)

Partner Sharing moves photos and videos; it does not move the scaffolding around them. Albums you built in the old account do not appear in the new one — the photos inside them arrive, unalbumed, so rebuild your essential albums afterwards while the old account is still available as a reference for what belonged together. Favourites flags, archive choices and edits generally travel with the photos themselves better than the organisation does, but spot-check a few edited favourites rather than assuming. Face groups retrain in the new account over a few days; the people labels reappear, occasionally needing a merge nudge where the same person was recognised as two. The Locked Folder, by design, never shares and never copies — its contents move only by manual download and re-upload, which is exactly the friction a private folder is supposed to create. Finally, anything other people shared with the old account belongs to them; it was never the old account’s to give, and it will not transfer.

During the waiting days, resist tidying either account. Deleting apparent duplicates while auto-save is still working through the backlog can remove items whose copies have not landed yet. Let the counts stabilise across two separate checks a few days apart; a merge declared finished too early is the usual prologue to a missing year discovered later.

Conclusion

Partner Sharing plus auto-save is a genuine merge in everything but name: invite from the old account, save everything on the new account, give it days, and verify before deleting anything. Set the start date to the beginning, keep the storage quota healthy, and your two libraries become one — permanently, not just viewable.

Frequently Asked Questions

Will the merged photos survive if I delete the old account?

Yes — but only the ones auto-save copied into the new account before deletion. That is why verifying the save completed (counts, spot-checks of your oldest photos) must happen before the old account is touched.

Do saved partner photos count against my storage?

Generally yes, they become your copies and consume your quota. Check the new account’s storage page after merging; upgrade to a Google One plan if the combined library needs it.

How long does the merge take?

Sharing itself is instant; the auto-save copy of a large backlog runs in the background over hours to days depending on library size. There is no progress bar — verify by counts and date spot-checks over several days.

Can I merge three accounts this way?

Only one partner at a time is allowed. Merge account B into A first, end that partnership, then partner A with C and repeat the auto-save process into A.

What if both accounts already have some of the same photos?

Google Photos often recognises exact duplicates and avoids doubling them, but it is not guaranteed. A post-merge duplicate cleanup pass is the reliable answer.