← Tools

Hash Generator

Generate SHA-256, SHA-384, and SHA-512 hashes locally in your browser.

SHA-256
SHA-384
SHA-512
100% Client-side. No Server Uploads.
Note: these are general-purpose hash functions for file integrity and checksums. Do not use them to store passwords — use a dedicated password-hashing algorithm like bcrypt, scrypt, or Argon2 instead.

Need a strong password instead? Try our Password Generator

What is a SHA hash?

SHA-256, SHA-384, and SHA-512 belong to the SHA-2 family of cryptographic hash functions, standardized by NIST (FIPS 180-4). Each takes any input — text, a file's contents, anything — and produces a fixed-length "digest" that looks like random characters. The same input always produces the same hash, but there's no way to reverse a hash back into the original input. That makes hashes useful for verifying a file hasn't been altered (checksums), confirming data integrity, and as a building block in digital signatures and systems like Git and Bitcoin.

SHA-256 vs SHA-384 vs SHA-512: which should I use?

SHA-256256 bits (64 hex characters)The most widely used and compatible default — this is what most checksums, APIs, and file-verification tools expect.
SHA-384384 bits (96 hex characters)A truncated variant of SHA-512, sometimes required by specific compliance or protocol standards.
SHA-512512 bits (128 hex characters)A larger security margin than SHA-256, and often faster on 64-bit systems — a good choice when you specifically need SHA-2's strongest option.

Is it safe to hash sensitive data with this tool?

Yes — hashing happens entirely in your browser using the Web Crypto API. Nothing you type is ever uploaded, logged, or stored on a server.

What is SHA-256 used for?

Verifying downloaded files haven't been corrupted or tampered with, confirming data integrity, digital signatures, and as a core building block in systems like Git and Bitcoin. It is not, by itself, a good way to store passwords — use bcrypt, scrypt, or Argon2 for that.

Can I get the original text back from a hash?

No. Hashing is one-way by design — there is no way to reverse a SHA-256/384/512 hash back into the input that produced it.

What's the difference between SHA-256, SHA-384, and SHA-512?

They all belong to the same SHA-2 family and use the same underlying design — the main difference is output length and speed. SHA-256 produces a 256-bit hash and is the most widely used default. SHA-512 produces a 512-bit hash, offers a larger security margin, and is often faster on 64-bit systems. SHA-384 is a truncated version of SHA-512's internal computation, producing a 384-bit hash — it's mainly used where a specific standard or protocol requires that exact length. For most everyday uses (checksums, file verification), SHA-256 is sufficient; choose SHA-512 if you specifically want SHA-2's strongest option.

Is SHA-512 more secure than SHA-256 or SHA-384?

In terms of theoretical security margin, yes. For an n-bit hash, generic collision resistance is roughly 2^(n/2) — about 2¹²⁸ for SHA-256, 2¹⁹² for SHA-384, and 2²⁵⁶ for SHA-512, so SHA-512 has the largest margin. In practice this rarely matters: 2¹²⁸ is already far beyond any feasible computation, and there are no known practical attacks against any SHA-2 variant. SHA-256 remains the right default for most everyday use; pick SHA-512 if you specifically want the extra theoretical margin or a protocol requires it.