How to use the MD5 and Base64 commands in Linux?

Two commands cover most checksum and encoding work on Linux: md5sum produces a fixed fingerprint of a file, and base64 converts data into plain ASCII text so it can travel through channels that only accept text. They look similar in a terminal but do opposite jobs. The sections below show the difference through hashes, verified downloads, and decoded Base64 output you can reproduce as-is.

MD5 vs Base64: What Each Command Actually Does

MD5 (Message-Digest algorithm 5) is a hash function. Feed it any input and it returns a 128-bit fingerprint conventionally rendered as 32 hexadecimal characters. Identical content always reproduces that string exactly.

Base64 is not encryption or hashing at all. It is an encoding scheme that represents binary data using 64 ASCII characters, so it is reversible by design.

Anyone with the encoded string can decode it back to the exact original bytes. Safe transport through text-only channels like email bodies and JSON fields is the point, not secrecy.

One honest caveat about MD5: collision attacks against it have been practical since the mid-2000s, so it is retired from security roles like password storage and digital signatures. For accidental-corruption checks on downloaded ISOs and archives, it still works, though SHA-256 (via sha256sum) is the current recommendation for anything an attacker could influence.

Create an MD5 Checksum with md5sum

Both md5sum and base64 are part of GNU coreutils, so they ship with every mainstream distribution and nothing needs installing.

Create a test file and generate its checksum. The hash depends only on the file contents, never the name or timestamp, so renaming a file does not change its MD5 value:

echo "Hi this is a test file from LinuxForDevices" > example.txt
md5sum example.txt

9614a183699d93ca7d0409699f384767  example.txt

The long string on the left is the digest and the filename follows. Running md5sum again on identical content reproduces exactly this line, which is what makes comparison possible across machines.

You can also hash text directly without creating a file. Pass the string with echo and pipe it into md5sum. Use the -n flag on echo to suppress the trailing newline, because that invisible character would otherwise change the hash:

echo -n "LinuxForDevices" | md5sum

68cd249253ae59f05b60af56bdcab1bc  -

The dash at the end means the input came from standard input rather than a named file. If your hash differs from a published value for supposedly identical text, a missing -n is the usual suspect.

Useful md5sum Options

The full option list lives in the manual page, which you can open as described in the man command guide.

Encode and Decode with the base64 Command

The base64 command reads input, encodes or decodes it, and writes the result to standard output or a file. The basic syntax is:

base64 [option] [input_file]

Encoding our example file turns every byte into printable ASCII characters:

base64 example.txt

SGkgdGhpcyBpcyBhIHRlc3QgZmlsZSBmcm9tIExpbnV4Rm9yRGV2aWNlcwo=

Decoding reverses it exactly. The -d flag tells the command to treat its input as Base64 and reconstruct the original bytes:

base64 -d encoded.txt
echo -n "TGludXhGb3JEZXZpY2Vz" | base64 -d

Both forms print the original text unchanged. Because encoding is fully reversible, Base64 provides zero confidentiality.

Never treat an encoded password or API key as hidden. Anyone can decode it with a single command.

Useful base64 Options

The -w 0 option matters more than it looks.

By default the encoder wraps its output every 76 characters, which breaks embedded strings in JSON fields, URLs, and config files. Decode such strings only with wrapping tolerated.

Verify a Downloaded File Against Its Published Checksum

This is the workflow you will actually repeat. Projects publish a checksum file next to their downloads, and verification means comparing your copy against that published value.

1. Save the official checksum line to a file, or generate one locally for this demonstration:

md5sum example.txt > example.md5
cat example.md5

9614a183699d93ca7d0409699f384767  example.txt

2. Verify while the file matches its recorded hash. The -c flag reads the checksum file and recomputes each digest:

md5sum -c example.md5

example.txt: OK

3. Change the file by even one appended line and re-verify. The check now fails loudly instead of passing silently:

printf 'new line\n' >> example.txt
md5sum -c example.md5; echo "exit code: $?"

example.txt: FAILED
md5sum: WARNING: 1 computed checksum did NOT match
exit code: 1

The non-zero exit code matters for scripts. Wrap verification in an if statement or chain it with an AND-list so a corrupted download stops your pipeline before the bad file gets used.

To fetch a checksum over the network alongside your download, pull it with curl or wget first. The verification step here completes that workflow either way.

Why Decoded Base64 Ignores Tampering

The failed md5sum check above exposes the core difference between the two tools. When the file changed, md5sum noticed immediately because it compares content fingerprints.

A saved Base64 copy behaves differently. Decoding it returns the original bytes regardless of what later happened to example.txt, because the decoder processes whatever string you hand it and has no memory of the source file.

In short: Base64 answers “what are these bytes”, md5sum answers “are these bytes the ones I expected”. Choosing between them is choosing between those two questions.

Frequently Asked Questions

Start with md5sum whenever you download system images, archives, or packages, and reach for base64 when a text-only interface demands them. Both ship with GNU coreutils on every mainstream distribution, so nothing needs installing. For broader context on shell work, see the Linux command-line guide and the walkthrough on editing files in Linux.