Every time a website offers a "SHA-256 checksum" beside a download, it is offering you a fingerprint: a fixed-length string of characters computed from the file, which changes completely if even one byte of the file changes. That fingerprint is a hash, and hashing is one of the quiet foundations of digital trust — used to verify downloads, check that data was not corrupted in transit, store passwords safely and sign documents. This guide explains hashing in plain English, compares the three algorithms you will meet most often — MD5, SHA-1 and SHA-256 — and shows how to generate and use hashes yourself, privately, in your browser.

What a hash function does

A cryptographic hash function takes input of any length — a word, a file, an entire disk image — and produces a fixed-length output: 32 hex characters for MD5, 40 for SHA-1, 64 for SHA-256. Three properties make it useful. It is deterministic: the same input always gives the same hash, so two people hashing the same file must get identical results. It is one-way: you cannot reconstruct the input from the hash. And it shows the avalanche effect: change one letter and roughly half the output characters change, so tampering is obvious at a glance. Hash the word "ToolMater" and then "Toolmater" and the SHA-256 results share almost nothing — try it in the tool below and see.

MD5 vs SHA-1 vs SHA-256

MD5 (1992) is fast and still everywhere as a casual checksum — and it is broken for security: researchers can craft two different files with the same MD5. Use it to spot accidental corruption, never to prove authenticity against an attacker. SHA-1 (1995) survived longer but fell to a demonstrated collision in 2017; browsers no longer trust it for certificates. It lingers in legacy systems and Git's object store. SHA-256 (2001), from the SHA-2 family, has no known practical attacks and is the modern default — Bitcoin mining, TLS certificates, software signing and download verification all rely on it. The rule of thumb: SHA-256 for anything new, the others only to match checksums someone else published.

How to generate a hash online

  1. Open the free Hash Generator on ToolMater.
  2. Type or paste the text you want to fingerprint.
  3. Read the MD5, SHA-1 and SHA-256 values that appear instantly as you type.
  4. Click Copy beside the hash you need.
  5. Compare it with the expected value — a single different character means different data.

A worked example: verifying a download

You download an installer, and the publisher's page lists its SHA-256. After downloading, you hash the file (with your operating system's built-in tool — certutil -hashfile on Windows, shasum -a 256 on macOS and Linux) and compare. If the two 64-character strings match exactly, the file is bit-for-bit what the publisher released: no corruption, no silent modification in transit. If they differ at all — even in one character — delete and re-download, and be suspicious if a retry still mismatches. For text data such as API signatures, tokens and test vectors, the online generator below does the same job without a terminal. Notice the privacy point: many hash websites send your text to their server. This one computes SHA hashes with your browser's own Web Crypto API and MD5 locally, so a sensitive string never leaves your machine — a detail that matters when the text is a password-like secret you are testing.

Hashing and passwords: an important nuance

Never store passwords as plain MD5 or SHA

Fast hashes are the wrong tool for passwords precisely because they are fast — attackers can try billions of guesses per second. Real systems use slow, salted password hashes such as bcrypt or Argon2. Knowing this distinction is the difference between using hashes and misusing them.

Salts defeat rainbow tables

Because hashing is deterministic, attackers precompute hashes of common passwords ("rainbow tables"). A unique random salt per user makes those tables useless. Generate strong random material for such jobs with a proper password generator.

Hash Generator (MD5 / SHA-256) — Frequently Asked Questions

Can I decrypt a hash to get the original text back?

No — hashing is not encryption, and there is nothing to decrypt. The only "reversal" is guessing inputs and hashing them until one matches, which is why short, common inputs are weak and long random ones are safe.

Why do hashes of the same file match everywhere?

Because the algorithms are public standards. Any correct implementation, on any device, produces the identical fingerprint for the identical bytes — that universality is what makes checksums portable.

What hash should I publish for my own files?

SHA-256. It is universally supported, trusted by browsers and operating systems, and costs nothing extra over the weaker options.

Hash Generator (MD5 / SHA-256) — Conclusion

A hash turns any data into a fingerprint you can compare at a glance: same fingerprint, same data. Learn the three big algorithms, default to SHA-256, and generate hashes in the tool below — privately, instantly and free.