What it picks up.
Everything the GoPro writes to the card — video, stills, companion files, telemetry. SyncShot reads the card as a volume and copies what it finds, in the same order the camera wrote it.
- Video
- 4K60, 5.3K, slow-motion, the long chaptered takes. A continuous clip recorded as GH010001.MP4 → GH020001.MP4 arrives intact, in order, exactly as the camera laid it down.
- Photo
- Time Warp, Burst, Night photos, single frames — copied at full resolution as the GoPro wrote them, no re-encoding, no thumbnails standing in.
- Companion files
- LRV low-res proxies, THM thumbnails, GPMF telemetry sidecars — copied alongside the source footage in case your edit or your analysis tool wants them later.
- Metadata
- Capture date, time, GPS, camera body, lens setting — preserved end to end as the file moves from card to destination.
Where it sends.
One source, many destinations — and SyncShotreads the card once, then fans the same files out to every place you chose. Pick one. Pick five. The card doesn't get read again 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 card 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 GoPro or mount the cards
Cable in, or SD cards into a reader — single or multi-slot. SyncShot lists each as a source the moment macOS sees it, 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 each card 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 card is the byte that arrived.
Common questions.
- 01
Does it understand GoPro chaptering?
Long takes that span GH010001.MP4, GH020001.MP4, GH030001.MP4 — the chapter files for one continuous clip — copy in order. SyncShot preserves them as the camera wrote them, so your editor sees them the same way Premiere or Resolve does.
- 02
Can I offload from two GoPro cards at once?
Yes. Drop each card into a reader and list each as a source. SyncShot reads them in parallel and writes to every destination at once — two cards, four drives, one NAS, no babysitting.
- 03
What about footage on the GoPro's internal storage?
Connect the camera as a source. If macOS sees the GoPro — as a storage device or via the GoPro mount — SyncShot reads it like any other volume. No companion app, no phone in the middle.
- 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 card handed over, SyncShot flags it and retries — and the job report tells you exactly what landed where.
- 05
What happens to the originals on the card after a copy?
By default the originals stay on the card — 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.
Also offloading from DJI, SD card, or iPhone? Browse everything SyncShot loves.