SHA-256
—SHA-2 checksum
One source. Three useful SHA-2 fingerprints.
Hash text or one local file and get SHA-256, SHA-384, and SHA-512 together without re-entering the source.
Web CryptoFile stays local32 MiB file limit
Hash generator workspace
Source
Web Crypto's digest API is not streaming, so the file path is deliberately bounded instead of promising arbitrary-size hashing.
Text source
0 / 100,000 UTF-16 units · 0 UTF-8 bytes
Local file
Maximum 32 MiB
Checksums
Lowercase hexadecimal
SHA-384
—SHA-512
—Quick feedback
Did this result work for you?
One tap is enough. You can ignore this and keep working.
Thanks — that helps us improve.
Checksum use
SHA-2 fingerprints are useful for comparing content and checking whether bytes changed. Matching hashes do not by themselves prove who created or distributed a file.
Not password storage
Fast raw SHA-256/384/512 hashes are not password-storage schemes. Password storage requires a deliberately slow, salted password KDF designed for that job.
Why the file limit?
The browser's standard SubtleCrypto.digest() consumes the input as a complete buffer. BeanNest caps files at 32 MiB rather than pretending this dependency-free route streams huge files.