Hash Generator

Overview

Computes MD5, SHA-1, SHA-256, and SHA-512 digests of your text as you type, entirely in the browser — plus drag-and-drop file hashing for the SHA family — with every digest rendered as lowercase hex and its own copy button.

How It Works

Paste a string and all four digests update immediately: the SHA family comes from the browser's native Web Crypto engine, MD5 from a bundled RFC 1321 implementation. Each algorithm row has Copy and Download controls (downloads are saved as CruxDev-hash-<algorithm>.txt) that stay disabled unless the row holds a real hex digest, so an error message can never be copied as a hash. Drop or browse to a file and the SHA-1/SHA-256/SHA-512 digests are computed locally — the filename and size are shown, and a toast confirms nothing was uploaded. The text box hashes the exact UTF-8 bytes, including line breaks, so a trailing newline changes every digest.

Step-by-Step Usage Guide

1. Paste your string, token, or config value into the input editor.
2. Watch all four digests (MD5, SHA-1, SHA-256, SHA-512) compute live.
3. Optionally drop a file onto the file area for SHA-family file hashing.
4. Copy or download the digest you need.

Technical Specifications & Standards

The SHA digests call crypto.subtle.digest(), which runs on the operating system's native crypto routines — fast enough for large files and impossible to get subtly wrong the way a hand-rolled implementation can. Web Crypto deliberately omits MD5, so MD5 is computed by a bundled implementation of RFC 1321 over UTF-8 input. Digests are always lowercase hex, the conventional representation for checksums and content identifiers.

Targeted Use Cases

• Comparing a computed SHA-256 against the digest a software release page publishes, by eye, to verify a download.
• Generating content identifiers and cache keys from exact strings.
• Producing the hash half of a signature scheme during development.
• Computing legacy MD5 checksums for old pipelines that still expect them.

Notes & Gotchas

• The algorithm set is MD5, SHA-1, SHA-256, and SHA-512 — there is no SHA-384, and digests are hex-only (no base64 encoding of the output).
• File hashing covers the SHA family only; MD5 is text-only because the file path relies on Web Crypto, which has no MD5. File hashing and the SHA text digests need a secure context (HTTPS or localhost); outside one the SHA rows show an Unavailable message, while MD5 still works everywhere.
• MD5 and SHA-1 are cryptographically broken for security purposes. Use them for legacy checksums only — never for passwords, signatures, or certificates.
• There is no compare-with-expected field: match your digest against the published one by eye, and remember a hash proves the bytes match, not that the bytes are trustworthy.

Frequently Asked Questions