Checksum Manifest Verifier

Match manifest filenames to selected files and validate MD5, SHA-1, SHA-256, SHA-384, SHA-512, or CRC32 entries locally.

Checksum manifestLocal files to match by filename

0Matches

0Mismatches

0Missing files

0Invalid lines

Paste a manifest and choose filesSupported digest lengths map to CRC32, MD5, SHA-1, SHA-256, SHA-384, or SHA-512.

Selected text and files are processed locally. Hashes and checksums detect matching bytes; they do not prove that a file is trustworthy unless the expected digest came from a trusted source.

Manifest parser & verification coverage audit

Audit the manifest itself before matching local files. Detect digest lengths, malformed rows, duplicate paths and mixed algorithms so missing files and bad syntax do not collapse into one generic failure.

Extra-file policyFilename matching

—Parsed entries

—Malformed rows

—Algorithms seen

—Duplicate paths

Ready.

Manifest item	Detected algorithm	Parse status	Verification consequence

A parsed manifest can still fail verification because a listed file is missing or a digest differs; syntax evidence is kept separate from content-match evidence.

Integrity and authenticity are different jobs

connects text/file digests, checksum verification and HMAC workflows. Hashes compare exact bytes; HMAC additionally depends on a shared secret key.

Password-storage boundary

Fast hashes such as SHA-256, SHA-1 and MD5 are not password-storage schemes. Production password storage should use a purpose-built slow password hashing/KDF design with salts and reviewed parameters; legacy algorithms remain here only for compatibility and checksum workflows.