Hashing

SHA-256 Generator

Generate SHA-256 hex digests locally with browser crypto. Hashing is one-way and is not encryption.

How this tool works

SHA-256 produces a fixed-length digest from input text.

It is useful for checksums and integrity comparisons, but password storage requires dedicated password hashing algorithms and salts.

Examples

• Hash a sample payload for a test assertion.
• Compare two pieces of text by checking their SHA-256 digests.
• Hash the UTF-8 text abc and compare it with a published SHA-256 test vector.

Common use cases

Hashing is not encryption

SHA-256 creates a fixed-length digest from input text. It is useful for comparisons and integrity workflows, but it is not reversible encryption.

The tool uses crypto.subtle.digest in the browser. That is appropriate for local digest generation, but password storage requires dedicated password hashing algorithms rather than a plain SHA-256 hash.

Good SHA-256 uses

• Comparing sample payloads in tests.
• Creating a digest for non-secret content.
• Checking whether two text values produce the same digest.
• Documenting expected hash output for a fixture.

Invalid or unsafe assumption

Mistakes to avoid

• Calling hashing encryption.
• Comparing hashes produced from different byte encodings.
• Using an untrusted checksum as proof of publisher identity.

Limits of this workflow

SHA-256 detects byte changes but does not identify who produced a file.

Ordinary SHA-256 is intentionally fast and unsuitable for direct password storage.

Local-processing and privacy boundary

Text is encoded as UTF-8 and hashed locally with Web Crypto; no digest input is uploaded.

Practical workflow

• Identify the exact bytes and algorithm.
• Generate the lowercase or uppercase hexadecimal digest.
• Compare normalized hexadecimal values.
• Authenticate the expected digest through a trusted channel when identity matters.

Related guides

Official references

• NIST FIPS 180-4: Secure Hash Standard

FAQ

Related tools