LOCAL INTEGRITY TOOL / FILE TO SHA-2

Checksum File Generator

Calculate a SHA-256, SHA-384, or SHA-512 fingerprint and download a standard hash line beside the original filename.

Processed in this browserOne file up to 100 MB. Web Crypto reads the complete file into browser memory for this release.

Step 1 / source

Choose the source

1 file - 100 MB

Drop one file here

Choose the exact file whose integrity fingerprint you want to publish or compare.

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. Web Crypto reads the complete file into browser memory for this release.

Plain-language method

What a checksum proves

Web Crypto reads the complete byte sequence and calculates one deterministic SHA-2 digest. The same bytes with the same algorithm produce the same digest; a one-byte change should produce a different result.

01
Choose a valid source
Use the final file you intend to distribute. Renaming alone does not change its checksum, but editing or re-saving usually does.
02
Review the conversion choices
Choose the algorithm expected by the recipient. SHA-256 is common and is not interchangeable with SHA-384 or SHA-512.
03
Inspect the separate result
The text download contains the lowercase digest, an asterisk, and the original filename in a common verification-line format.

Useful when

Practical jobs this tool handles

Publish a download fingerprint beside a release.
Compare copies transferred between devices.
Record evidence that an archived file has not changed.

Before converting

Make the checksum trustworthy

Name the algorithm wherever you publish the value.
Distribute the checksum through a trusted channel.
Regenerate it after any edit, export, or recompression.

Know the boundary

Integrity is not authenticity by itself

A checksum detects byte differences only when the expected value is trusted. An attacker who can replace both file and checksum can make them agree.

Quick answers

Questions before you convert

The digest is exact and algorithm-specific.

Does renaming change the checksum?

No. The digest uses file bytes, not the filename.

Which algorithm should I choose?

Use SHA-256 unless a system or recipient explicitly requires SHA-384 or SHA-512.

Why is the output one line?

The digest-plus-filename format works with many checksum verification workflows.