English

Hash Generator

Generate SHA-1, SHA-256, SHA-384 and SHA-512 hashes of local text or files.

Processed locally in your browser. Your input is not uploaded.

More tools you might find useful.

Base64 Encoder & Decoder Encode or decode Base64 text locally.
HTML Entity Encoder & Decoder Encode HTML special characters or decode named and numeric entities into plain text.
Regex Tester Test JavaScript regular expressions and inspect matches, captures and positions.
Text to Slug Turn a heading or phrase into a lowercase, hyphen-separated URL slug with sensible Unicode handling.
CSV ↔ JSON Converter Convert CSV with headers to JSON or flat JSON objects to properly escaped CSV.
Color Converter Convert HEX, RGB and HSL colors with normalized values and a local preview.
JSON Formatter Format, validate and minify JSON data.
JSON ↔ YAML Converter Convert JSON to readable YAML or YAML to formatted JSON locally, with safe parsing and clear errors.
JWT Decoder Decode JWT headers and payloads directly in your browser.
Number Base Converter Convert large integers between binary, octal, decimal and hexadecimal without precision loss.

How to use Hash Generator

Generate hexadecimal digests using your browser’s native Web Crypto API. Text is encoded as UTF-8, with line breaks preserved. Files stay on your device.

Details and limits

SHA-1 is legacy and is not recommended for security-sensitive use. Hashing is not encryption. File input is limited to 20 MiB because Web Crypto requires the complete buffer in memory. Text is limited to 1,000,000 characters; HTTPS is required.

Practical example

A hash changes when input bytes change, including line breaks or spaces. Use it to compare content; hashing is not reversible encryption.

SHA-256 of abc, with no newline, is ba7816bf8f01cfea414140de5dae2223b00361a396177a9cb410ff61f20015ad. Adding a newline produces a different digest.

Frequently asked questions

Why do the text and file hashes differ for the same visible words?

A file may contain a byte-order mark or different line endings. Hashing compares bytes, so invisible differences change the digest.

Can a matching hash prove who created a file?

No. A digest can help compare contents, but it does not identify an author. You need a trusted reference or a separate signature mechanism.

Why do SHA-256 and SHA-512 produce different-length results?

The algorithms have different digest sizes. Compare a result only with a reference generated using the same algorithm.