SyncShot

What gets written.

Whatever the source handed over — uploaded into Drive exactly as it arrived. SyncShot treats Drive like any other destination: files are originals, folder layout is yours to define, the verification is non-negotiable.

Originals
Files arrive byte-for-byte intact — no recompression, no name mangling, no quiet conversion to a Google-native format. What came in is what lives in Drive.
Folder structure
Source structure preserved as the folder layout by default — or apply a workflow path template (something like /YYYY/MM-shoot-name/) so Drive grows the way your archive expects.
Metadata
EXIF and file times preserved on the upload where the destination supports it. The provenance survives the cloud hop.
Job report
Alongside the upload (or in a side log, your choice) SyncShot writes a job report — what landed in which folder, when, and which verification check it passed.

What it pairs with.

Drive is the shared destination — the one the editor, the client, the rest of the team can actually reach. Your Drive is one of many destinations, and SyncShot writes to it in parallel with the local disk and the archive, so the share-with-humans copy is ready when the local copy is.

Shared editorial
Footage hand-off to the cutter, photos hand-off to the retoucher — landing in the shared folder the moment they come off the card, not after a manual upload at the end of the day.
Client review folders
A delivery folder per shoot, structured the way the client expects, ready to be shared once the job report says every file is verified.
Lightweight backup
Not the archive — but a fast off-machine copy of the day's work, sitting in your account, reachable from anywhere if the studio Mac suddenly isn't.
Team handoff
An assistant offloads on-site, Drive receives it, the studio pulls it down. SyncShot is the part that puts the files where the team can find them.

How it works.

  1. 01

    Connect Google Drive

    OAuth handshake once — sign in to the account, grant SyncShot write access to the folders you choose. The token lives in the macOS Keychain from there.

  2. 02

    Choose destinations

    Pick the Drive folder — and every other place this shoot belongs. Save the set as a workflow if you'll use it again; next time it's one click.

  3. 03

    Hit start

    SyncShot reads the source once and writes to every destination in parallel. The local drive finishes first; the Drive uploads keep going in the background.

  4. 04

    Trust the report

    Every byte is hash-checked end to end. When the job finishes you get a report — what landed in Drive, every verification mark. The byte that left the source is the byte in your account.

Google Drive specifics.

OAuth once and Drive lists everywhere you can write: personal My Drive, every Workspace domain you belong to, every Shared Drive your account can reach. Uploads run through Google's resumable-session URI — Drive hands back a session ID up front, chunks stream against it, and a mid-flight disconnect resumes at the last acknowledged chunk. No re-sending gigabytes because the studio wifi blinked.

Two quotas worth watching: personal Drive tops out at 5 TB for a single file, and Workspace throttles uploads per user per day at roughly 750 GB. A wedding shoot that ran long will spill into tomorrow's quota — that's Google, not the app. A tip: create a dedicated Workspace folder per shoot. Drive's search stays fast when a single folder stays under a hundred thousand items.

Common questions.

  1. 01

    Does it work with my personal Google account and a Workspace account?

    Both. Connect personal, connect Workspace, connect more than one of each — every account shows up as a separate destination, and you pick which folders inside each one receive the upload.

  2. 02

    Can it write into a Shared Drive?

    Yes — if your account has write access to the Shared Drive, it lists in SyncShot as a destination just like a folder in My Drive. Pick the team folder, the job lands inside it.

  3. 03

    Can I write to Google Drive and other destinations at once?

    Yes. Drive is one of many — list a local disk, a NAS, an S3 bucket, and Google Drive together, and SyncShot writes to each in parallel from a single read of the source.

  4. 04

    Will it verify the upload?

    Yes — hash-verified end to end like every SyncShot copy. The byte that left the source is the byte that lives in Drive, and the job report tells you exactly which files passed.

  5. 05

    Where do credentials live?

    Locally, in the macOS Keychain — the OAuth token from your one-time sign-in. SyncShot uses it to upload to your Drive; the connection is between your Mac and Google, nothing in between.

  6. 06

    What happens if a big upload disconnects halfway?

    SyncShot uses Google's resumable-upload session URI — the upload registers with Drive up front, then streams in chunks. When the network drops, the session ID is replayed and the transfer picks up at the last chunk boundary Google acknowledged. A 40 GB master that got most of the way over cellular finishes on wifi without re-sending what already landed. The rest of the job's destinations keep going through the outage untouched.

Also writing to S3, NAS, or external drives? Browse everything SyncShot loves.