LOCAL INTEGRITY TOOL / SHA-2 MATCH

Checksum Verifier

Calculate a file fingerprint and compare it exactly with a trusted SHA-256, SHA-384, or SHA-512 checksum.

Processed in this browserOne file up to 100 MB plus one complete hexadecimal checksum. The algorithm and digest length must agree.

Step 1 / source

Choose the source

1 file - 100 MB

Drop one file here

Choose the downloaded file you need to compare with a checksum from a trusted source.

Browse filesChecking publication status...

No file upload

This operation runs with browser APIs. Nirmion receives catalogue requests, not the selected source bytes.

Original stays unchanged

The converter creates a separately named output. It never writes back into the source file.

Bounded work

One file up to 100 MB plus one complete hexadecimal checksum. The algorithm and digest length must agree.

Plain-language method

How exact verification works

Nirmion calculates the selected SHA-2 digest from every file byte, normalizes the expected hexadecimal checksum to lowercase, then compares the two complete values without fuzzy matching.

01
Choose a valid source
Choose the file you actually received, not a similarly named copy. Obtain the expected checksum through a trusted channel.
02
Review the conversion choices
Match the algorithm label exactly. SHA-256 has 64 hex characters, SHA-384 has 96, and SHA-512 has 128.
03
Inspect the separate result
The page shows both complete values and offers a text verification report. A mismatch never replaces or deletes the file.

WORKED EXAMPLE / REVIEW BEFORE RELYING

Checksum Verifier: a small review pass

Use a short, non-sensitive sample first. This example shows the checkpoints to apply before moving an authorised dataset into the destination workflow.

FILE
Source
Choose sample.checksum verifier with a header and two representative, non-sensitive records.
Review the conversion choices
Keep the documented defaults, convert once, and compare the preview or result count with the Checksum Verifier sample.
CHECK
Result
Open the separate CHECK download and verify two records, field names, nulls, encoding, and destination compatibility.

Useful when

Practical jobs this tool handles

Verify a downloaded installer against its publisher value.
Check a backup after transfer.
Confirm that a shared archive matches an agreed fingerprint.

Before converting

React correctly to a mismatch

Confirm the selected algorithm and full expected value.
Download the source again from the official location.
Do not run a security-sensitive file until the mismatch is explained.

Know the boundary

Trust the source of the expected value

A matching digest confirms byte equality with the supplied value. It does not identify who created the file or whether that expected value is legitimate.

Quick answers

Questions before you convert

A checksum match is binary, not a quality score.

Can I paste a checksum file line?

Yes. The first whitespace-separated value is used, so a trailing filename is allowed.

Does uppercase hexadecimal work?

Yes. Hexadecimal letter case is normalized before exact comparison.

What should I do after NO MATCH?

Recheck the algorithm and expected value, then obtain a fresh file from the trusted publisher.