SHA-256 hash
Generate a SHA-256 fingerprint of your text.
Result
Start typing and the result appears here. No button needed.
SHA-256 hash, without the extra steps.
Calculate a SHA-256 digest from the UTF-8 bytes of your text with the browser Web Crypto API. The result is a 64-character hexadecimal fingerprint.
How to use this tool
- 1Type or paste the exact text.
- 2Generate its SHA-256 digest.
- 3Copy the hexadecimal hash.
When SHA-256 hash is the right tool
- A download publishes a checksum you want to verify.
- Two files should be confirmed identical without comparing them by eye.
- A fingerprint is needed for a cache key or deduplication.
- You need to prove a file has not changed since you received it.
What a digest proves
SHA-256 maps any input to a fixed 256-bit value. The same input always produces the same digest, and changing a single byte changes the output completely, so comparing digests is a reliable way to confirm two things are identical. It is one-way: the digest reveals nothing about the input and cannot be reversed. Compare the full string rather than the first few characters.
Not a password hash
SHA-256 is designed to be fast, which is the opposite of what password storage needs. Modern hardware computes billions of SHA-256 digests per second, so a bare digest of a password is weak against brute force. Password storage needs a deliberately slow, salted algorithm such as bcrypt, scrypt, or Argon2. Use SHA-256 for integrity, not for secrets.
A few quick answers.
Type or paste the exact text. Generate its SHA-256 digest. Copy the hexadecimal hash.
Tool inputs are processed in your browser. Crate has no upload endpoint and no accounts. Downloaded site assets and a cookie-free page-view count still require a connection; your files and text are not included in those requests.
Whitespace and line endings affect the result. A plain SHA-256 digest is not a password storage scheme. Web Crypto requires HTTPS or localhost.
No. It is a one-way digest. Identical input always gives identical output, but the digest reveals nothing about what produced it.
No. It is fast by design, which helps brute force. Password storage needs a slow salted algorithm such as bcrypt, scrypt, or Argon2.