How to Verify File Integrity Using the cksum Command in Linux

When you download a massive operating system ISO file or a heavily encrypted database backup from a remote server, internet fluctuations can cause microscopic packet loss. Even if a 10-Gigabyte file is missing a single, microscopic byte of data, the entire file is mathematically corrupted and will violently crash when executed. To mathematically prove that a downloaded file is a 100% perfect, bit-for-bit clone of the original source file, you must use the cksum (Checksum) command.

How the cksum Command Works

The cksum command is a cryptographic verification engine. It does not look at the file’s name, its extension, or its metadata. Instead, it ingests every single raw byte inside the file and runs it through a highly complex mathematical algorithm called a Cyclic Redundancy Check (CRC). This algorithm crunches the raw data and spits out a unique, fixed-length string of numbers—a digital fingerprint.

To calculate the CRC fingerprint for a downloaded file named ubuntu_server.iso, simply type:

cksum ubuntu_server.iso

The terminal will instantly output a string that looks something like this:

3819283719  2048000000 ubuntu_server.iso

This output contains exactly two critical pieces of mathematical data:

1. The Checksum (3819283719): The unique cryptographic fingerprint generated by the CRC algorithm.
2. The Byte Size (2048000000): The exact physical size of the file, counted in raw bytes.

Verifying File Integrity

Because the CRC algorithm is mathematically absolute, if even a single pixel in an image is changed, or a single letter in a text file is capitalized, the algorithm will generate a completely different, wildly unrecognizable checksum number.

To verify that your downloaded file is safe and uncorrupted, you simply compare the checksum.

1. Go to the official website where you downloaded the file. The developer will always publish the official “Master Checksum” directly next to the download button.
2. Run the cksum command on your downloaded file in your Linux terminal.
3. Mathematically compare the two numbers.

If the official website says the checksum should be 3819283719, and your terminal outputs 3819283719, you have absolute mathematical proof that the file is perfect, uncorrupted, and safe to execute. If the numbers differ even slightly, the file is corrupted or has been maliciously tampered with by a hacker, and you must instantly delete it.