What it picks up.
Every photo, every clip, every screen recording — anything the Pixel treats as a captured file. SyncShot reads the phone once and copies what it finds, regardless of format or which Google Photos folder the gallery has filed it in.
- Photos
- Everything the camera shoots — JPEG, HEIC, RAW (DNG) when the Pro mode is on — pulled at full resolution. The computational output the Pixel is known for is just a JPEG or HEIC on disk; SyncShot moves it like any other file.
- Video
- Standard 4K, slow-motion, time-lapse, the cinematic clips from newer Pixels. Long takes copy in a single pass with progress you can watch.
- Captures
- Screen recordings, screenshots, downloaded media, Magic Eraser edits saved back to the gallery — copied alongside the rest, treated as Pixel media like any other file.
- Metadata
- Timestamps, location, orientation, and the technical EXIF data the camera wrote — preserved as the file moves from phone to destination.
Where it sends.
One source, many destinations — and SyncShotreads the Pixel once, then fans the same files out to every place you chose. Pick one. Pick five. The phone doesn't wake up for each one.
- Internal disk
- Your Mac's own drive. The fastest target — usually first in the chain so the slower destinations can feed from it in the background.
- External drives
- USB-C and Thunderbolt SSDs, spinning HDDs, anything macOS mounts. Multiple drives at once if your shoot demands it.
- Network storage
- Synology, QNAP, TrueNAS, plain SMB shares. SyncShot writes over the network without blocking the local copy or slowing the phone read.
- Cloud
- S3 and S3-compatible buckets (Wasabi, R2, MinIO), Google Drive, Dropbox, Azure Blob. Same job, different destination — uploaded in parallel.
How it works.
- 01
Connect the phone
Cable in. Trust the Mac if it asks, and set the USB mode to file transfer when the Pixel prompts. SyncShot sees it as a source the moment macOS does — no driver, no companion app.
- 02
Choose destinations
Pick every place this shoot belongs. Save the set as a workflow if you'll use it again — next time it's one click.
- 03
Hit start
SyncShot reads the Pixel once and writes to every destination in parallel. The fastest disk finishes first; cloud uploads keep going in the background.
- 04
Trust the report
Every byte is hash-checked end to end. When the job finishes you get a report — what was copied, where it landed, every verification mark. The byte that left the phone is the byte that arrived.
Common questions.
- 01
Does SyncShot work with every Pixel?
If macOS mounts your Pixel — through Android File Transfer, Finder, or any MTP-aware tool — SyncShot can read it. Pixel 6 and newer are the well-trodden path; older Pixels work the same way if they still mount.
- 02
Can it copy to my external drive and my NAS at the same time?
Yes. Pick as many destinations as you want — internal disk, external SSD, NAS, S3-compatible bucket, Google Drive — and SyncShot reads the Pixel once and feeds every destination in parallel.
- 03
What happens to the originals on the phone after a copy?
By default the originals stay on the Pixel — SyncShot is built to copy, not move. If a workflow does call for clearing the source after a verified copy, that's a conscious choice you make per workflow, never a surprise.
- 04
How do I know the copy is intact?
Every copy is hash-verified end to end. If a destination wrote something other than what the Pixel handed over, SyncShot flags it and retries — and the job report tells you exactly what landed where.
- 05
Does it understand Google Photos backup?
Google Photos is a destination too (coming soon). SyncShot offloads the raw files off the phone the moment macOS sees it; cloud sync runs alongside, doing its own thing. The two don't fight — you get a local archive, a NAS copy, an S3 copy, and the Google Photos library, in parallel.
Also offloading from Samsung Galaxy, other Androids, or iPhone? Browse everything SyncShot loves.