Checksum Manifest Verifier

Compare one file with an expected SHA-256 value or verify a bounded checksum manifest.

On-device No sign-up Free to use

Verify checksums controls

  1. 1 Add files
  2. 2 Arrange/Options
  3. 3 Download

Drop your files here

or choose them from your device

Up to 20 files and 40 MiB total. Ambiguous basenames, absolute paths and dot/parent path segments are refused. No files are fetched online.

    ?

    Up to 20 entries and 64 KiB. GNU: digest followed by two spaces and filename. BSD: SHA256 (filename) = digest. Relative folder paths map to selected basenames.

    ?

    64 hexadecimal characters from a trusted download source.

    Result

    Showing an example.

    Compare one file with an expected SHA-256 value or verify a bounded checksum manifest.

    The selected abc.txt is marked match with SHA-256. Adding a newline changes the digest and makes this record fail.

    Loading the tool. Your result will appear here.

    https://usefreetools.net/checksum-manifest-verifier · 20 November 2026

    Was this helpful?

    How to use Checksum Manifest Verifier

    1. Choose Verify a checksum manifest for a GNU/BSD SHA-256 or SHA-512 list, or Compare one file with expected SHA-256 for a single download.
    2. Paste the trusted manifest or the expected 64-character SHA-256 value, then select the local files. Keep their basenames distinct.
    3. Run Verify checksums. Read matches, mismatches, missing entries and extra selected files separately. Extra files are listed but not hashed.
    4. Download the JSON report if needed. A match means the selected bytes agree with the supplied digest; it does not authenticate the checksum source.

    Example: Checksum Manifest Verifier

    Compare one file with an expected SHA-256 value or verify a bounded checksum manifest.

    You add
    Choose abc.txt containing exactly UTF-8 abc with no newline. Manifest: ba7816bf8f01cfea414140de5dae2223b00361a396177a9cb410ff61f20015ad abc.txt
    You get
    The selected abc.txt is marked match with SHA-256. Adding a newline changes the digest and makes this record fail.

    Options

    Verification mode
    Manifest mode compares up to 20 entries with selected files. Single-file mode requires exactly one local file and one expected SHA-256 digest.
    Expected SHA-256 digest
    64 hexadecimal characters from a trusted download source.
    SHA-256 or SHA-512 manifest
    Paste up to 20 GNU or BSD SHA-256/SHA-512 entries within 64 KiB. A GNU record is digest, two spaces and filename; a BSD record is SHA256 (filename) = digest, or SHA512. Relative folders are reduced to case-folded basenames, so they cannot distinguish duplicate names in different directories.
    Local files to verify
    Up to 20 files and 40 MiB total. Ambiguous basenames, absolute paths and dot/parent path segments are refused. No files are fetched online.

    Supported inputs and limits

    • Manifest up to 64 KiB and 20 entries; up to 20 files and 40 MiB total.
    • Supported GNU or BSD SHA-256/SHA-512 records.
    • Basename matching only; ambiguous duplicate names are refused.
    • No downloads, signature verification or proof that an untrusted checksum list is authentic.
    • Single-file mode accepts exactly one file and an expected SHA-256 digest.
    More details

    It does not add legacy MD5 verification or authenticate the supplied checksum source.

    Where your input is processed

    This tool does not upload your inputs. See the limits for anything saved on your device.

    A match depends on trusting the manifest

    The verifier proves that selected bytes agree with the supplied digest. An attacker who replaces both a file and its checksum can still produce a match. This tool does not validate a signature or the publisher’s identity. Obtain a checksum through the appropriate trusted channel for your workflow.

    Basenames do not distinguish duplicate directory copies

    Relative manifest paths are mapped to selected basenames. Two chosen files with the same basename are ambiguous and refused instead of guessed. Absolute and parent-traversal paths are not accepted. Missing entries and extra selections are reported separately; extra files are listed rather than silently included in hash verification.

    Questions about Checksum Manifest Verifier

    Does a matching hash prove the source is safe?

    No. It proves bytes match the supplied checksum. Obtain that checksum from a trusted source.

    Are files downloaded automatically?

    No. Select the files on your device.

    How are names matched?

    By safe basenames. Ambiguous duplicate names are refused.

    Page updated · Project managed by Tony Hines · Report a problem with Checksum Manifest Verifier