What it picks up.
Whatever the card holds — SyncShot reads it as a volume, not as a brand. The camera that wrote it doesn't need a driver here; the filesystem is the contract. Every file macOS sees, SyncShot can copy.
- Whatever's on the card
- SyncShot reads the card as a mounted volume and copies every file the filesystem exposes — regardless of camera brand, codec, container, or format.
- Folder structure
- Preserved as-is — DCIM/100CANON, MISC/, PRIVATE/, the lot — or remapped via workflow path templates if your archive wants a different shape.
- Hidden files
- System files, AVCHD streams, Sony XAVC sidecars, anything the camera tucks away — included if present, copied alongside the obvious ones.
- Metadata
- Every file's modification time, EXIF, sidecar XMP — 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
Mount the card
Slot it in a reader — single or multi-slot. SyncShot sees the card the moment macOS does. Multiple cards at once if your reader has the slots for it.
- 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 work with CFexpress and CFast?
Yes — anything the Mac mounts as a volume. SD, SDXC, CFexpress Type A and Type B, CFast 2.0, microSD in an adapter. SyncShot doesn't care about the card format, only that macOS sees it.
- 02
Can I read two cards at once?
Yes. Drop each card into a reader — or a multi-slot reader — and list each as a source. SyncShot reads them in parallel and writes to every destination at once.
- 03
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 each card once and feeds every destination in parallel.
- 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 if a card has bad sectors?
SyncShot reads what it can and flags what it can't, in the job report, by file. It doesn't pretend to recover damaged data — that's what a recovery tool is for — but it tells you exactly which files survived the copy and which need a second look.
Also offloading from GoPro, DJI, or iPhone? Browse everything SyncShot loves.