What it picks up.

Every frame OM System writes to the card — stills, the stacks from computational modes, clips, the sidecars alongside. SyncShot reads the card once and copies what it finds, regardless of body or capture mode.

RAW files
ORF from every OM System and Olympus generation, pulled at full resolution. Single shots, high-res composites, focus-stacked sequences — copied as the camera wrote them.
Compressed
JPEG and HEIF at every quality setting. Whatever the body produced sits on the card; whatever sits on the card lands at the destination.
Video
From the hybrid bodies that record — H.264 and H.265, the long takes the OM-1 line is built for. Sidecar audio copies alongside.
Metadata
Timestamps, lens identification, computational-mode tags, the technical EXIF the camera embedded. Preserved 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 spin up 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.

  1. 01

    Mount the card

    Card into the reader, or the body connected over USB. SyncShot sees the source the moment macOS does — no driver, no companion app.

  2. 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.

  3. 03

    Hit start

    SyncShot reads the card once and writes to every destination in parallel. The fastest disk finishes first; cloud 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 was copied, where it landed, every verification mark. The byte that left the card is the byte that arrived.

OM System, up close.

OM-1, OM-1 Mark II, and OM-5 anchor the current line — weather sealing that lets you use them as intended, plus computational modes rare on any other mount. Stills come out as ORF or JPEG; video runs H.264 across the board, no proprietary raw wrapper on the video side. Live ND, Handheld Hi-Res, and Focus Bracketing all resolve to a single ORF in-camera — SyncShot copies them like any other frame.

Both card slots on the OM-1 are SD, UHS-II throughout — no CFexpress tier to plan around. Tip: Handheld Hi-Res writes 50–80 MB ORFs that stack up on a long day faster than you expect. Budget your NAS and cloud destinations accordingly, and keep an eye on card fill during the shoot rather than at the end of it.

Common questions.

  1. 01

    Does SyncShot work with every OM System camera?

    If the card or the camera shows up in macOS — Image Capture, Finder, a card reader — SyncShot reads it. The OM-series bodies, PEN line, Tough TG compacts, and the older Olympus generations too. No driver, no companion app.

  2. 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 card once and feeds every destination in parallel.

  3. 03

    What happens to the card after a copy?

    By default the card is read-only — SyncShot is built to copy, not move. Formatting is something you do in-camera when you're ready, never something the offload tool decides for you.

  4. 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.

  5. 05

    Do computational modes leave stacks SyncShot has to reassemble?

    No. Live ND, Handheld Hi-Res, and Focus Bracketing all resolve in-camera to a single ORF — the stack is already collapsed by the time it hits the card. SyncShot copies the resulting frame like any other, byte-for-byte with BLAKE3 verification. There's no hidden JPEG stack to worry about, no in-camera artifacts SyncShot needs to compensate for on the way out.

Also offloading from Panasonic, Fujifilm, or Pentax? Browse everything SyncShot loves.