CSP Builder
Build and risk-score Content-Security-Policy headers visually.
OpenSHA-1, SHA-256 and SHA-512. - runs entirely in your browser. Free, fast and private.
Hash strings, tokens, or file contents you provide.
Choose SHA-1, SHA-256, SHA-384, or SHA-512.
Web Crypto hashes the input entirely in-browser.
Copy lowercase hex for checksums or integrity checks.
You downloaded a release and the site published a SHA-256. Hash Generator lets you hash the same string or checksum input locally and compare digests without installing OpenSSL for a one-off check.
Reach for it for cache keys, webhook HMAC debugging prep, fixture digests, or quick integrity comparisons on short text. Prefer SHA-256 or SHA-512 for new work. SHA-1 remains available for legacy comparisons only.
Pitfall: hashing a password and calling it "storage." Hashes without salt and a proper KDF are not password storage. Another trap is comparing digests across different encodings (UTF-8 vs UTF-16) and thinking the algorithm failed.
Tip: clear the input after hashing secrets or API keys so they do not linger in the field.
Digests are computed with the Web Crypto API inside this page. Your input string is not sent to OneDevToolkit to be hashed.
Keyboard shortcut
Match a published digest against text you hashed locally.
Produce SHA-256 strings for keys and fixtures without a CLI.
Hash sample bodies while you design signature checks.
Answers for this tool. For site-wide help, open the FAQ hub.
No. Digests are computed with Web Crypto in your browser.
Generators and hashers run locally. Still, never paste production secrets into any site if your security policy forbids it.
Results live in page memory until you leave or clear. Favourites/history do not save password fields unless you explicitly store them in Vault.