How to use this tool
- Paste text or choose a small local file.
- Select SHA-256, SHA-384, SHA-512, or SHA-1.
- Choose hex or Base64 output and copy the generated digest.
Encoding / Security Utility
Hash Generator
Generate SHA-256, SHA-384, SHA-512, or SHA-1 hashes for text and small files directly in your browser. Use it for checksum comparison, API examples, release notes, and local integrity checks without sending the input to a server.
Generate hash
The file is read by the browser on this page. Large files can use memory, so keep this for small assets, checksums, and test files.
Hash output
Algorithm: SHA-256
Bytes: 0
Source: waiting
Waiting for input.
Real examples
- Checksum: hash a downloaded config snippet and compare it with a published SHA-256.
- API docs: create a stable hash for example payloads without exposing real secrets.
- Release notes: calculate a local file digest before publishing an asset.
Common use cases
- Compare whether two strings or files produce the same digest.
- Create SHA-256 examples for integration tests and documentation.
- Generate copy-ready hashes for local debugging notes.
Sample input/output
Input: WebUtilsLab
SHA-256 hex:
fc82abbc8b51e75a41e557b5edfb0fa58c8f6d8b20ac7b8a47ca26c72f63e197
Common errors and fixes
| Issue | Why it happens | How to fix it |
|---|---|---|
| Hash does not match a server value | The input has different whitespace, newline style, encoding, or hidden characters. | Copy the exact original bytes or compare file hashes instead of retyped text. |
| SHA-1 appears in old examples | SHA-1 is a legacy algorithm still found in old systems and docs. | Prefer SHA-256 or stronger for new checksum examples. |
| File hashing feels slow | The browser reads the whole selected file before hashing. | Use this page for small files. Use command-line tools for very large artifacts. |
Edge cases table
| Edge case | Expected behavior |
|---|---|
| Empty text | The tool hashes the empty string if you run it with no text selected. |
| Unicode input | Text is encoded as UTF-8 before hashing, matching common web API workflows. |
| Base64 output | The digest bytes are encoded as Base64. This is not the same as hashing the Base64 text. |
Related workflow
Decode a JWT with the JWT Decoder, format its payload with the JSON Formatter, then generate a SHA-256 checksum here for documentation or fixture comparison. Use the Base64 Encoder / Decoder when you need encoding, not hashing.
Does this tool upload my input?
No. Text and selected files are processed locally in your browser. WebUtilsLab does not save or upload what you paste or choose.
Is hashing the same as encryption?
No. A hash is one-way and designed for comparison. Encryption is reversible when you have the correct key.
Should I use SHA-1?
Use SHA-1 only for legacy comparison. Prefer SHA-256, SHA-384, or SHA-512 for new checksum examples.