Your operating system does nothing to verify your files were copied correctly. Here's what you're missing.
Both Windows and macOS perform zero verification when you copy files. They read and write. There's no proof that what landed on disk is actually intact.
| Protection | Manual Copy Windows / macOS Finder |
Synclio |
|---|---|---|
| File exists at destination | Maybe | ✓ |
| File content identical (byte-for-byte) | ✗ | ✓ |
| All files accounted for | ✗ | ✓ |
| Corrupt or truncated file detection | ✗ | ✓ |
| memory card health check on insertion & during use | ✗ | ✓ |
| File is actually readable after transfer | ✗ | ✓ |
| Timestamp preserved and verified | ✗ | ✓ |
| Detailed transfer log for every session | ✗ | ✓ |
Hardware CRC protects data in transit over the USB/SD bus, but neither Windows nor macOS re-reads or checksums the data that actually landed on your drive.
Degraded flash cells can serve up corrupted data without throwing any error. Your OS will happily write that corrupted data to your drive and report success.
Windows uses CopyFileEx and macOS Finder both stop at writing the bytes. Neither one reads the file back or computes a checksum to confirm what was written is what was intended.
The moment you insert a memory card, Synclio runs a filesystem health check. If the card shows signs of corruption, you're warned before a single byte is transferred. That includes a RAW filesystem, unreadable sectors, or OS-level read errors. The monitor keeps running in the background the entire time the card is in use, so problems that develop mid-session don't go unnoticed.
A wedding, a news event, a once-in-a-lifetime shot. You can't reshoot it. Synclio runs hash verification after every transfer so you have mathematical proof the copy is perfect before you format the card.