SHA-256 of abc
Input
abcExample output
ba7816bf8f01cfea414140de5dae2223b00361a396177a9cb410ff61f20015adHash Generator
Security & Hashing100% Client-SideReady
TEXT
0 lines0 chars
0 B / 9.54 MB
Read-only
0 lines0 chars
0 B
About this tool, examples & FAQ
Hash exact text bytes with MD5, SHA-1, SHA-256, SHA-384, or SHA-512 entirely in your browser, and compare every digest side by side with the all-hashes report.
Key facts
| Accepted input | Text input hashed as exact UTF-8 bytes |
|---|---|
| Algorithms | SHA-256, SHA-512, SHA-384, SHA-1, and MD5, or all five at once |
| Output encoding | Hexadecimal or Base64, with an uppercase option for hex; uppercase applies to hex only and is ignored for Base64 |
| Max input size | 10 MB |
| Execution deadline | 3 s |
| Processing location | Browser-only: pasted input is not uploaded |
How to use
- Paste or type the text to hash into the input editor.
- Pick an algorithm: SHA-256, SHA-512, SHA-384, SHA-1, MD5, or All Hashes.
- Choose the digest encoding: hexadecimal or Base64, with optional uppercase hex.
- Click 'Run' to compute the digest locally in your browser.
- Copy the digest, or send it to another tool for comparison.
Examples
SHA-256 of empty string
Input
(empty input)Example output
e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855Edge cases
Empty string
Hashing empty input succeeds and returns the published empty-string digest for the chosen algorithm; whitespace is hashed literally.
Newline and case sensitivity
Exact bytes are hashed, so a trailing newline, extra space, or case change produces a completely different digest.
Legacy algorithm warnings
Single MD5 or SHA-1 runs carry a DEPRECATED_ALGORITHM warning; the all-hashes report carries one combined legacy warning.
How it works
- Encodes the input to exact UTF-8 bytes.
- Computes the digest with the selected algorithm using the bundled hash library.
- Renders the digest as lowercase or uppercase hex, or as Base64.
- Executes inside a Web Worker bounded by the tool deadline.
Related workflows
Base64 Encoder / Decoder
Encode UTF-8 text to standard or URL-safe Base64 and decode Base64 back to text.
UUID / GUID Generator
Generate cryptographically secure RFC 4122 Version 4 UUIDs in bulk with custom casing, hyphens, and wrapper formatting.
Text Diff / Compare
Compare two text files, code snippets, or configuration payloads line-by-line, word-by-word, or as a unified patch.
JSON Formatter
Prettify, indent, and format JSON strings with customizable indentation and key sorting.
Frequently asked questions
Why does adding a newline change the hash?
The tool hashes exact UTF-8 bytes, so every byte matters: a trailing newline, an extra space, or a case change is different input and therefore produces a different digest. Copy the text exactly when comparing digests.
Can a hash be decoded back to the original text?
No. Hashing is one-way: the digest cannot be reversed into the input. The only way to check a guess is to hash the candidate text and compare digests. Do not confuse hashing with Base64-style encoding, which is reversible.
What does collision resistance mean?
Collision resistance means it is infeasible to find two different inputs with the same digest. SHA-256, SHA-384, and SHA-512 are designed for this; MD5 and SHA-1 have demonstrated collisions and must not be relied on where an attacker could craft inputs.
Why do MD5 and SHA-1 show a warning?
Both are cryptographically weak and collision-prone, so single-algorithm runs emit a DEPRECATED_ALGORITHM warning. Use SHA-256 or SHA-512 for security purposes, and reserve MD5 or SHA-1 for legacy checksums where collisions are not a threat.
Can I use these digests to store passwords?
No. Password storage needs a dedicated password-hashing function with a salt and a work factor. This tool only computes plain digests of text, which is a different requirement from password hashing.
References
- noble-hashes — hash implementation used by the tool — SHA-2, SHA-1, and MD5 digest algorithms executed locally