Method · updated September 2026

How we measure

Every number on the home page was measured on our own devices. Here is how each one was measured, and how to check it yourself.

What we measured

22 GB · 184 files · 0 failures

One cable session, August 2026: Samsung Galaxy S25 Ultra → Mac with the Mac app’s cable mode, over a USB 2 cable (a charging cable), at about 28 MB/s, roughly 13 minutes. Every file was checked for its exact size against the phone and 3 were compared byte for byte: 0 failures. On the cable, the fingerprint check (SHA-256) runs when the phone has the sha256sum tool; otherwise the check is the exact size.

806 MB in 46 s

One real video from a Galaxy S25 Ultra to a Mac over home Wi-Fi, August 2026: the app logged 46.1 s (about 17.5 MB/s), and that time includes computing the file’s SHA-256 fingerprint.

Up to 49.7 MB/s over Wi-Fi

September 2026, a 191 MB file on home Wi-Fi: Mac → iPhone at 49.7 MB/s and iPhone → Mac at 38.9 MB/s, measured on the wire (the time the bytes spent crossing the network).

Every pair of devices, both directions

September 2026, our own devices on one home Wi-Fi: Android ↔ Windows, Android ↔ Mac, iPhone ↔ Windows, iPhone ↔ Mac, Mac ↔ Windows and phone to phone (Android ↔ iPhone, by QR code) — 16 of 16 pairs. We recorded whether the file arrived and passed the fingerprint check, not the speed: every pair completed and verified. On iPhone the app has to stay open while receiving.

What we do not claim

We publish no timings for other apps or for the cloud: we have not measured them side by side, so we do not put them on a chart. We have not measured a USB 3 cable yet either, so we publish no number for it. Your numbers will differ with your network and devices.

The method, in plain terms

  1. Over Wi-Fi, the sender computes the SHA-256 fingerprint of the file before sending.
  2. The receiver writes the file as a temporary part, then computes its own SHA-256 of what landed on disk, not of the stream.
  3. Only if both fingerprints match does the file get its final name. Otherwise it is discarded and the app shows the failure.
  4. On the Mac’s Android cable mode, the Mac compares the exact size and, when the phone has sha256sum, the SHA-256 too; a file that fails is deleted and listed as a failure.

Reproduce it

Install ZiggSend on your computer, send a large file from your phone and watch it finish: a file that fails the check never gets its final name, and the app tells you. Then check it yourself: the phone’s History shows the first 8 characters of the original’s SHA-256, and shasum -a 256 (Mac) or certutil -hashfile … SHA256 (Windows) gives you the copy’s. Back to the home page