Hash Generator

Generate MD5, SHA-1, and SHA-256 hashes from text or a file instantly in your browser. Verify a downloaded file's integrity, produce a Subresource Integrity (SRI) hash for a script tag, or confirm a checksum matches in CI, with no upload required.

MD5

—

SHA-1

—

SHA-256

—

Usage examples

Verifying a downloaded file's integrity

Compare the hash published on a download page against the hash of the file you received, to confirm it wasn't corrupted or tampered with.

Generating a SHA-256 hash of a password or secret

Quickly compute the SHA-256 hash of a password or token you need to store in code or a config file.

Quickly checking if two files have identical content

Compare the hashes of two files to confirm they're byte-for-byte identical without having to open and compare them manually.

Generating a cache-busting key for a static asset

Hash the contents of a CSS or JS bundle with SHA-256 and use the first several characters of the digest as a content hash in the filename, so browsers only re-fetch the file when its contents actually change.

Producing a Subresource Integrity (SRI) hash for a script tag

Compute the SHA-256 hash of a third-party script you're loading from a CDN so you can paste the digest into an integrity attribute and let the browser refuse to run the file if it's ever tampered with.

Spot-checking a Git blob or commit-adjacent content hash

Paste the exact text content you expect into the tool and compare the resulting SHA-1 hash against a known value, as a quick sanity check when you suspect a file was modified outside of version control.

Confirming a config value matches what's expected in CI

Hash an environment variable value or small config snippet locally and compare it against a hash stored in your pipeline, without ever having to paste the actual secret into a log or ticket.

Quick reference

MD5

TextMD5
"" (empty string)d41d8cd98f00b204e9800998ecf8427e
"a"0cc175b9c0f1b6a831c399e269772661
"abc"900150983cd24fb0d6963f7d28e17f72
"hello"5d41402abc4b2a76b9719d911017c592
"hello world"5eb63bbbe01eeed093cb22bb8f5acdc3
"Hello World"b10a8db164e0754105b7a99be72e3fe5
"test"098f6bcd4621d373cade4e832627b4f6
"password"5f4dcc3b5aa765d61d8327deb882cf99
"123456"e10adc3949ba59abbe56e057f20f883e
"admin"21232f297a57a5a743894a0e4a801fc3
"The quick brown fox jumps over the lazy dog"9e107d9d372bb6826bd81d3542a419d6

SHA-1

TextSHA-1
"" (empty string)da39a3ee5e6b4b0d3255bfef95601890afd80709
"a"86f7e437faa5a7fce15d1ddcb9eaeaea377667b8
"abc"a9993e364706816aba3e25717850c26c9cd0d89d
"hello"aaf4c61ddcc5e8a2dabede0f3b482cd9aea9434d
"hello world"2aae6c35c94fcfb415dbe95f408b9ce91ee846ed
"Hello World"0a4d55a8d778e5022fab701977c5d840bbc486d0
"test"a94a8fe5ccb19ba61c4c0873d391e987982fbbd3
"password"5baa61e4c9b93f3f0682250b6cf8331b7ee68fd8
"123456"7c4a8d09ca3762af61e59520943dc26494f8941b
"admin"d033e22ae348aeb5660fc2140aec35850c4da997
"The quick brown fox jumps over the lazy dog"2fd4e1c67a2d28fced849ee1bb76e7391b93eb12

SHA-256

TextSHA-256
"" (empty string)e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
"a"ca978112ca1bbdcafac231b39a23dc4da786eff8147c4e72b9807785afee48bb
"abc"ba7816bf8f01cfea414140de5dae2223b00361a396177a9cb410ff61f20015ad
"hello"2cf24dba5fb0a30e26e83b2ac5b9e29e1b161e5c1fa7425e73043362938b9824
"hello world"b94d27b9934d3e08a52e52d7da7dabfac484efe37a5380ee9088f7ace2efcde9
"Hello World"a591a6d40bf420404a011733cfb7b190d62c65bf0bcda32b57b277d9ad9f146e
"test"9f86d081884c7d659a2feaa0c55ad015a3bf4f1b2b0b822cd15d6c15b0f00a08
"password"5e884898da28047151d0e56f8dc6292773603d0d6aabbdd62a11ef721d1542d8
"123456"8d969eef6ecad3c29a3a629280e686cf0c3f5d5a86aff3ca12020c923adc6c92
"admin"8c6976e5b5410415bde908bd4dee15dfb167a9c873fc4bb8a81f6f2ab448a918
"The quick brown fox jumps over the lazy dog"d7a8fbb307d7809469ca9abcb0082e4f8d5651e46d3cdb762d02d0bf37c9e592

Frequently asked questions

Is my text or file sent to a server?

No. All hashing happens entirely in your browser, and what you enter is never sent to a server.

Is MD5 a secure hashing algorithm?

No. MD5 has known security weaknesses and isn't recommended for security purposes like storing passwords. Use it only for lightweight purposes like checking file integrity, and use SHA-256 wherever security matters.

Can this handle large files?

Yes. Computation may take a bit longer depending on file size, but it will hash anything your browser is able to load.

Should I use uppercase or lowercase?

The hash value is the same either way, case doesn't change it. Pick whichever matches the convention used by the tool or document you're comparing against.

Why is SHA-1 also considered broken if it's newer than MD5?

SHA-1 was designed to fix MD5's weaknesses, but practical collision attacks were demonstrated against it as well. It's still common in legacy systems like older Git internals, but for anything security-sensitive — signatures, certificates, integrity guarantees against a motivated attacker — SHA-256 or a SHA-2/SHA-3 family algorithm is the safer choice.

Can I use SHA-256 to hash and store user passwords?

No, not safely on its own. A generic hash function like SHA-256 is fast and deterministic, which is exactly what makes it a poor fit for passwords: an attacker with a stolen hash can try billions of guesses per second, and identical passwords always produce identical hashes, which leaks information. Password storage needs a dedicated, intentionally slow algorithm with built-in salting, such as bcrypt, scrypt, or Argon2.

Is hashing the same thing as encryption or encoding?

No, they're different operations. Encoding (like Base64) is fully reversible and isn't meant to hide anything. Encryption is reversible if you have the right key. Hashing is one-way by design — there's no key or process that turns a hash digest back into the original input, which is exactly why it's useful for verifying integrity without exposing the original content.

Why do two completely different inputs sometimes get compared by their hashes instead of their raw content?

Because comparing fixed-length hash digests is much faster and easier than comparing potentially huge files byte by byte, and a well-designed hash function makes it computationally infeasible for two different inputs to produce the same output by accident. That said, this relies on the algorithm being collision-resistant, which is precisely why MD5 and SHA-1 are discouraged for anything where someone might deliberately try to engineer a collision.

Will the same input always produce the same hash here?

Yes, for a given algorithm, the same exact bytes always produce the same digest — that's what makes hashing deterministic and useful for integrity checks. Keep in mind that even a single changed character, extra space, or different line-ending style (CRLF vs LF) will produce a completely different hash.