Checksums and CRC can be very quick, but have significant drawbacks. SHA-256 hashes are best, although there are also error-correcting codes used in optical disks.
SHA
What are the performance differences between SHA-256 and 512? What throughput can you expect when checking hashes? And how to correct errors detected?
What are checksums, CRCs and hashes? What is required for a hash to be cryptographic, and how any of these affect your Mac? Some answers and explanations.
More about checking the integrity of files on macOS, with a new version of a free utility, news of the next apps, and error-correcting code perhaps?
To check the integrity of important documents, we’re going to calculate their SHA256 digests. But where should those be stored if HFS+ and APFS don’t have a suitable attribute?
If macOS can’t do it, how should we check the integrity of important files? Use a checksum, or a hash function? And which?
The workhorses of computer security, message digests and security certificates, are in the process of changing. Some disruption will result.
Businesses are often built on trust, and one of the most fundamental elements of trust must be in the accuracy of the data on your Mac. How should you ensure that your files remain true and correct?
The Eclectic Light Company 