Remote destinations
Offloading straight to a NAS
A local drive and the NAS, written in the same pass from a single read of the card, with every file read back and checked at both ends.
Why the two-step version is worse
The usual workflow is to offload to a local drive, then copy that folder to the NAS afterwards, usually with the Finder. That second copy is the weak link: it happens later, often unattended, and typically with no verification at all. The carefully checked local copy gets duplicated by a process that checks nothing.
Doing both in one pass means the card is read once, both destinations receive the same verified bytes, and one report covers both.
How it works
- Add the NAS as an SFTP destination Host, user, key or password, and a path. It sits alongside your local destinations in the same job.
- The card is read once and streamed to the local drive and the NAS at the same time. The network transfer does not wait for the local copy to finish.
- Both destinations are verified by read-back and the report records the outcome for each file on each destination separately.
The honest part: verifying over a network is slow
Read-back verification means pulling every byte back across the link. On gigabit ethernet with a busy NAS, that can take longer than the copy did, and over Wi-Fi it can be genuinely impractical.
What we will not do is quietly skip it to look fast. If you choose to verify a remote destination differently, that is an explicit choice you make, and it is recorded in the report — so anyone reading that report later knows exactly what was and was not checked. Silent downgrades are how people end up trusting a copy nobody verified.
SFTP now, other transports later
| Transport | Status | Notes |
|---|---|---|
| SFTP | Pro, in 1.0 | Covers essentially every NAS: Synology, QNAP, TrueNAS, unRAID, or a Linux box with an SSH server. |
| SMB / AFP shares | Already works | A mounted share is just a folder to macOS, so it can be a normal local destination. Verification applies as usual. |
| S3, Backblaze B2 | Roadmap | Deliberately not in 1.0. We would rather ship one remote transport that verifies properly than three that half work. |
What we cannot tell you yet
We have not published throughput figures for network destinations, because we have not measured them on hardware we would be willing to describe. Every number on the benchmark page was measured with source and destinations on local hardware, and extrapolating from those to your NAS would be exactly the kind of claim this site refuses to make.
When there are measurements, they will appear with the switch, the cabling and the NAS model written next to them.