Crypto Tools

Client-side crypto tools, each on its own page, each running entirely in your browser.

Generating versus hashing

These tools split cleanly in two. The password and UUID generators createrandomness, drawing from the operating system's entropy pool through the browser. The hash tools consume data, reducing input of any size to a fixed-length fingerprint that cannot be reversed.

What they share is WebCrypto. Every operation here is a native browser primitive rather than JavaScript arithmetic — which is the only reason a client-side password generator is worth trusting. A generator built on Math.random would look identical and be worthless.

ToolWebCrypto primitiveOutput lengthTypical use
Password Generatorcrypto.getRandomValues8–64 charactersAccount credentials you store in a password manager
Password Strength CheckerWebCrypto / EntropyScore, crack time, breachesAudit password security and brute-force vulnerability
UUID v4 Generatorcrypto.randomUUID36 charactersDatabase keys, message IDs, distributed record identifiers
SHA-256 Hashcrypto.subtle.digest64 hex charactersFile integrity, fingerprints, signatures
SHA-512 Hashcrypto.subtle.digest128 hex charactersThe same, where a longer digest is specified

Frequently asked questions

Do any of these tools send data to a server?

No. All four run entirely in your browser using the native WebCrypto API. Passwords, hashes, and identifiers are generated locally and never transmitted, logged, or stored. The pages keep working with the network disconnected.

What is WebCrypto?

A browser API providing cryptographic primitives — secure random numbers, hashing, signing, and encryption — implemented natively rather than in JavaScript. It is what makes a client-side password generator trustworthy, because the randomness comes from the operating system rather than a script.

Should I hash a password with SHA-256?

No. SHA-2 hashes are built to be fast, which is exactly wrong for password storage — speed helps the attacker. Use a slow, salted, purpose-built algorithm such as bcrypt, scrypt, or Argon2. The hash tools here are for fingerprinting data, not storing credentials.

Which hash length should I pick?

SHA-256 for almost everything: it is universally supported, has no known practical attack, and produces a manageable 64-character digest. Reach for SHA-512 when a specification requires it or you want extra margin.