What we're building.
The Google Photos integration will connect to your Google account through Google's own OAuth — no passwords stored, no app-specific passwords to manage — and write into the library, with named albums and shared albums as optional targets per workflow. From that moment on, Google Photos behaves like any other destination: a target on the workflow card you tick or untick.
Files will be uploaded at the original resolution and quality the source handed over — no silent re-encoding by SyncShot. Google Photos is the destination, not a transcoder.
Why it's worth waiting for.
- Parallel writes
- Google Photos will join the same multi-destination job as your other targets. Read the source once, fan out to Google Photos plus the local SSD plus the NAS plus the bucket — every destination running at once.
- Verified copies
- Every upload to Google Photos will be hash-checked against the source before SyncShot marks the copy complete, the same verification model that already protects copies to drives and S3 today.
- Workflow templates
- Google Photos will be selectable in saved workflows. Your personal-shoot template can land in 'Family'; your travel template can land in a shared album the whole group sees. Set once, picked with a tick.
- Shared album drops
- Write straight into a shared Google Photos album so everyone you've shared it with sees the shoot the moment the upload finishes. The destination IS the share — no second hop, no manual link.
What ships today.
SyncShot already offloads to multiple destinations right now — in parallel, verified, from the same job. If you were hoping Google Photos would be one of them today, the closest shipping target on the same Google account is Google Drive — same login, same cloud, same OAuth flow Google Photos will eventually use, just landing in Drive folders instead of Photos albums. For an everything-bucket option, S3 and S3-compatible buckets are shipping too.
Local drives, NAS shares, FTP, and external SSDs are shipping as well — pick as many as the shoot needs. When Google Photos lands, it joins that list. Until then, your work has a home in a working destination, not a waiting room.
Google Photos, at scale.
The Google Photos API exposes two surfaces SyncShotwill write into: the main library and named albums (personal or shared). Two upload qualities exist — Storage Saver re-encodes to save space; Original quality preserves the bytes the source handed over and counts against Google account storage. SyncShot will use Original quality by default. Re-encoding a client shoot to save a few gigabytes is not the trade you want.
One quirk that catches teams out: shared albums have separate storage quotas from personal libraries — a shared album can fill up while your personal library still has headroom. A tip that keeps things sane at scale: pair Google Photos with S3 or B2 as the actual archive, and let Google Photos be the browse and share surface. The bill stays predictable; the archive lives somewhere its quota is yours.
Tell me when it ships.
When the Google Photos integration ships, we'll email you the day it lands. No marketing, no upsell — just the heads-up, and a download link if you don't already have the app.
Working today — Google Drive (today) sits on the same Google account. Or browse everything SyncShot loves.