📁 Multi-Algorithm File Hash Generator

File hash generation calculates deterministic digests from the exact bytes in a selected file. Use it to compare a download against a published SHA-256 or SHA-512 checksum, confirm that two files are byte-for-byte identical, or record an integrity value before moving evidence, backups, or build artifacts.

Practical examples:

• Compare a Linux ISO against a vendor's SHA256SUMS file before installing it.
• Generate MD5 or SHA-1 only when an older mirror, archive, or audit record still publishes those legacy values.
• Use CRC32 or Adler-32 for fast accidental-corruption checks in archive and compression workflows.
• Save the generated hash with a backup manifest so you can detect later byte-level changes.

Supported algorithms:

• SHA-256 and SHA-512 are SHA-2 digests specified by NIST FIPS 180-4 and are the safest defaults for modern file-integrity checks.
• MD5, defined in RFC 1321, and SHA-1 are retained for compatibility but should not be trusted against intentional tampering; see RFC 6151 and the NIST SHA-1 transition plan.
• CRC32 is the cyclic redundancy check used by formats such as GZIP in RFC 1952; Adler-32 is the zlib checksum described in RFC 1950.

Limitations: A checksum only proves that the bytes match a known digest. It does not identify who created the file, and weak algorithms can be forged. For software authenticity, compare the digest from a trusted source or verify the publisher's digital signature.

Privacy and file size: The on-page tool uses your browser's file APIs to hash the selected file locally instead of uploading it through the web UI. Because the browser reads the file bytes before hashing, very large files can be limited by available memory and may take longer to process.