What it picks up.
Everything the DJI device writes to its card or internal storage — video at every flavour of resolution and codec, photo sequences, telemetry sidecars. SyncShot reads the volume and copies what it finds, in the same order the drone or gimbal laid it down.
- Video
- 4K, 5.1K, H.264 and H.265 / HEVC, D-Log and D-Cinelike profiles, slow-motion. Long takes copy in a single pass with progress you can watch.
- Photo
- JPEG single shots, DNG raw sequences from hyperlapse and AEB, burst frames — pulled at full resolution as the camera wrote them, no thumbnails standing in.
- Telemetry
- Flight log files (.DAT, .TXT, .FPV) and the sidecars the device drops next to the footage — copied alongside in case your edit or your post-flight tool wants them later.
- Metadata
- Timestamps, GPS, camera body, lens and gimbal info — preserved end to end as the file moves from drone to destination.
Where it sends.
One source, many destinations — and SyncShotreads the card or drone once, then fans the same files out to every place you chose. Pick one. Pick five. The source 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 or connect the drone
Either the SD or internal storage, or the drone itself by cable. SyncShot reads either 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 source 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 drone is the byte that arrived.
Common questions.
- 01
Does it work with the Mavic 3, Air 3, Avata, and Mini?
Any DJI device that macOS sees — as a storage volume, a card in a reader, or the drone connected by cable. SyncShot reads it like any other source. No DJI account, no FlyApp, no phone in the middle.
- 02
Will it copy flight logs?
Yes. Whatever the device writes to the card — telemetry sidecars (.DAT, .TXT, .FPV), flight log files, the rest — comes along with the footage to every destination. SyncShot doesn't parse or interpret them, just preserves them exactly as the drone wrote them.
- 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 the card or drone 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 source 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 drone or card after a copy?
By default the originals stay put — 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 GoPro, SD card, or iPhone? Browse everything SyncShot loves.