One bucket, every job.
Cloud destinations have a reputation for being a second tool — drag files into the desktop app, wait for sync, check the web view later. SyncShot reads Drive as a destination directly, in the same job as the local copies. Source read once, Drive written in parallel, verified the same way.
- A Google account with Drive access
- Personal Drive, Workspace, or a shared drive — any account that can write where you want the files to land. Authorize once during setup; tokens refresh quietly after that.
- A real connection
- Upload speed is the floor of cloud destinations. SyncShot doesn't slow the local copies waiting on Drive — the local destinations finish at full speed and Drive keeps uploading in the background.
- Headroom in Drive
- Roughly: total source size, plus a little. SyncShot warns ahead of the upload if the destination is going to run out before the job finishes.
- A target folder picked
- Default is a SyncShot/ folder created at the root. Any folder you have edit access to works — personal, shared, Workspace shared drive.
Step by step.
- 01
Open SyncShot and add Google Drive
Destinations → Add → Google Drive. The connect button opens the browser to Google's sign-in. Pick the account that owns the Drive folder you want to write to.
- 02
Approve the SyncShot OAuth scopes
Google shows the access screen — SyncShot asks for permission to create and write to its own folder, not to read every file in your Drive. Approve. The browser hands the token back to SyncShot and the destination is ready.
- 03
Pick the target folder
Either a folder SyncShot creates (default: SyncShot/) or any folder you have edit access to. Shared drives are listed alongside personal Drive. SyncShot remembers the choice; it doesn't reprompt for the next job.
- 04
Choose the organize-by layout
None / Date (YYYY/MM/DD) / Month (YYYY/MM) / Device / Type. The same options as a local destination. Date is the most common for shoots; Device is the most common for archival workflows.
- 05
Add Drive as a destination on the job
Pair it with whatever else is on the job — Mac, external SSD, NAS. The source is read once; Drive gets its copy in parallel with everything else. No re-reading the card to upload.
- 06
Start the job, leave it running
Drive uploads are throughput-bound on the connection, not on SyncShot. Cellular tethering is fine, fast home connections are fine, the studio gigabit is best. SyncShot resumes from the last verified chunk if the connection drops.
- 07
Verify, then trust the report
Every uploaded file is checksum-confirmed against the server's response — same BLAKE3 as the local destinations. Green report = the bytes Google holds match the bytes the source had.
After it's done.
Drive holds the verified copy. The report shows which file went where, what its hash was, and the Drive ID it landed under. If anything failed, it's named — and the next run picks up from the last verified chunk.
- Open the job report
- Every file, every destination including Drive, every hash result. Local finishes first, Drive when the upload completes. Filter for anything not green.
- Save Drive on the workflow
- Once it's authorized, Drive stays on the workflow until removed. Every future job using that workflow uploads to the same target folder.
- Disconnect when done
- If the account ever needs to be detached, Destinations → Google Drive → Disconnect revokes the SyncShot token in one step.
Self-hosted bucket instead? See out to S3. Want to lock the source-and-destinations as a one-click run? Saved workflows. More guides at the user guide hub.