SHA256 Online · Terms

Terms

Scope and limits of local text hashing and file checksum comparison.

Scope and limits

Scope

Effective 19 October 2026. This tool computes fingerprints and compares values. It does not authenticate publishers, detect malware, recover files, crack passwords or decrypt hashes. A match depends on a trusted expected value and the same algorithm.

MD5 and SHA1 are legacy algorithms with broken collision resistance. CRC32 is an accidental-error checksum, not a cryptographic hash. HMAC is offered only for the cryptographic algorithms.

The limit is 2 GiB per file, 100 files per batch, 1 MiB per manifest and 8 MiB decoded text. Device resources can impose lower practical limits. Physical iOS and Android limits have not been established by desktop viewport testing.

The tool is provided as-is. You retain responsibility for files, reference values and decisions. No account, subscription, payment or file license is requested or granted.

Practical questions

What does a checksum match promise?

Only equality between the calculated digest and the reference supplied for that algorithm. It does not guarantee safety, ownership or authenticity.

Is the tool provided with a warranty?

The tool is provided as-is. You remain responsible for choosing trusted references and for decisions based on results.

What are the maximum input sizes?

Up to 100 files, 2 GiB each; manifests up to 1 MiB; text up to 8 MiB decoded bytes. Devices may have lower practical limits.

Are physical phone limits guaranteed?

No. Desktop browser viewport tests do not establish the practical limits of physical iOS or Android devices.

Does using the tool grant a license to a file?

No. The tool asks for no file license and grants none. Your rights to selected content are separate from calculating its checksum.

Can hashes recover a lost password or decrypt a document?

No. These tools calculate fingerprints. They do not crack passwords, recover files or decrypt hashes.

Are MD5, SHA1 and CRC32 suitable for new security systems?

MD5 and SHA1 have broken collision resistance. CRC32 is not cryptographic. Their compatibility tools do not make them suitable for new security designs.

Are there account or payment obligations?

There is no sign-in, account, subscription or payment flow in this tool.