Password Encryption Utility

Encrypt or hash any password using MD5, SHA-1, SHA-256, SHA-512 and Bcrypt algorithms. See all five outputs side by side with copy buttons.

5 algorithms in one Instant results Copy each hash

Enter Your Password

About These Algorithms

MD5

Produces a 128-bit (32-char) hash. Cryptographically broken — do not use for security.

SHA-1

Produces a 160-bit (40-char) hash. Deprecated for TLS/certificates but still used in checksums.

SHA-256

Produces a 256-bit (64-char) hash. Part of SHA-2, current standard for integrity checks and signatures.

SHA-512

Produces a 512-bit (128-char) hash. Stronger variant of SHA-2 for higher-security checksums.

Bcrypt

A salted, intentionally slow hashing algorithm designed specifically for password storage — the recommended choice of these five.

Enter PasswordType the password you want to hash

EncryptClick Encrypt to compute all five hash types

View ResultsSee MD5, SHA-1, SHA-256, SHA-512 and Bcrypt hashes side by side

Copy HashClick Copy next to any hash to use it

About Password Encryption Utility

The Password Encryption Utility is a free online tool that encrypts any text string using multiple cryptographic hash algorithms — including MD5, SHA-1, SHA-256, SHA-512 and more. Hashing converts your input into a fixed-length, one-way encrypted string that cannot be reversed to the original text (unlike two-way encryption).

Hashing is used in web development and database management to store passwords securely. Instead of storing a plain-text password, applications store its hash — when a user logs in, the entered password is hashed and compared against the stored hash.

How to Encrypt Text

Enter your text or password in the input field
Select the hashing algorithm(s) you want to use
Click Encrypt
Copy the resulting hash value(s)

Available Algorithms

MD5 — 32-character hash (fast, not recommended for passwords)
SHA-1 — 40-character hash (legacy, avoid for new systems)
SHA-256 — 64-character hash (current standard for many applications)
SHA-512 — 128-character hash (high security)
Bcrypt — salted, intentionally slow hash purpose-built for password storage

Security Advice

For storing user passwords, use bcrypt, scrypt or Argon2 — not MD5 or SHA-1. These older algorithms are too fast and vulnerable to GPU brute-force attacks. Bcrypt (included above) automatically salts its output, so this tool now lets you generate a production-ready password hash directly, alongside the four general-purpose hashes for testing and integrity checks. Free, no login required.

Frequently Asked Questions

What does password encryption mean?

In this context, "encryption" refers to cryptographic hashing — converting a password into a fixed-length string using a one-way algorithm. Unlike true encryption, hashes cannot be reversed. This tool computes MD5, SHA-1, SHA-256, SHA-512, and Bcrypt hash outputs for educational and testing purposes.

Are these hashes safe for storing passwords?

MD5, SHA-1, SHA-256, and SHA-512 are all fast general-purpose hash functions — they are NOT safe for password storage on their own because their speed makes brute-force attacks practical. Bcrypt, included here, is purpose-built for passwords: it is intentionally slow and automatically salted, which is why it's the one recommended for real authentication systems (along with scrypt or Argon2).

When would I use MD5 or SHA-1 then?

MD5 and SHA-1 are still commonly used for non-security purposes like file integrity checksums, cache busting, generating unique identifiers, and comparing data without needing the original. SHA-256/SHA-512 are the modern standard for integrity and digital signatures. They're also used when verifying file downloads where the threat model doesn't involve adversarial attacks.

Why is the Bcrypt hash different every time I encrypt the same password?

Bcrypt automatically generates a random salt and embeds it in the output every time you hash a password — that's a deliberate security feature, not a bug. It means two users with the same password get completely different stored hashes, defeating precomputed rainbow-table attacks. MD5, SHA-1, SHA-256 and SHA-512 above are unsalted, so the same input always gives the same output.

Why does the same password always produce the same hash?

Hash functions are deterministic — the same input always produces the same output. This is by design, as it allows you to verify data without storing the original. The downside is that attackers can precompute hashes for common passwords (rainbow tables). Modern password hashing adds a random "salt" to prevent this.