RIPEMD-160 Hash Generator
Generate a RIPEMD-160 hash from text or a file, entirely in your browser.
How the RIPEMD-160 Hash Generator works
RIPEMD-160 is a 160-bit cryptographic hash function developed in the mid-1990s at KU Leuven as an open, European alternative to the NSA-designed SHA family. It processes input in 512-bit blocks through two parallel lines of computation whose results are combined at each step, producing a 40-character hexadecimal digest. It's slower and less studied than SHA-256, so it isn't recommended for new security-critical designs, but it remains relevant because Bitcoin and most other cryptocurrencies use RIPEMD160(SHA256(publicKey)) to derive shorter wallet addresses from public keys.
This tool computes the digest with the crypto-js library, entirely inside your browser — your text or file never leaves your device. Type text, drop in a file to hash its raw bytes instead, toggle uppercase output, or paste a known hash into the verify field to check for a match.
Built and maintained by Meet Shah · Last updated
What this tool is used for
- Reproducing the second hashing step in a Bitcoin address derivation to check your own implementation.
- Verifying a legacy artefact whose checksum was published as RIPEMD-160.
- Producing a 160-bit digest from a design lineage independent of the NSA-designed families.
- Working through a cryptocurrency exercise where the hash pipeline matters.
- Comparing 160-bit alternatives for a historical write-up.
Frequently Asked Questions
- Where is RIPEMD-160 actually used?
- Overwhelmingly in Bitcoin. An address is derived with RIPEMD160(SHA256(pubkey)) — the HASH160 step — which shortens the key to 20 bytes. Outside cryptocurrency it is rare in modern systems.
- Why did Bitcoin combine it with SHA-256?
- To get a 160-bit identifier (short enough for a compact address) while not relying on any single hash family. Nesting two independently designed functions means a break in one does not immediately yield an address collision.
- Who designed it, and why does that matter?
- An open European academic project (Dobbertin, Bosselaers and Preneel, 1996), not a national standards body. That independent provenance is precisely why some designers chose it during the period when NIST's process was under scrutiny.
- Is it broken?
- The 160-bit version has no practical collision attack, though its 128-bit predecessor RIPEMD does. Its 160-bit digest gives only ~80-bit collision resistance, which is below the modern comfort threshold — adequate inside HASH160, not a choice for new designs.
- How is it built?
- Two parallel 80-round lines whose results are combined at the end — a structure unlike both MD5 and SHA-2. That parallel design is what gave it a better security margin than the MD-family hashes of its era.
Common errors and gotchas
- Using it alone where Bitcoin uses it after SHA-256. The pipeline order is part of the construction, not decoration.
- Assuming a 160-bit digest gives 160 bits of collision resistance. The birthday bound halves it, as with any hash.
- Choosing it for new work on the strength of its independent design, when SHA-256 has far more scrutiny and support.
- Confusing it with the original RIPEMD, which is broken, or with RIPEMD-128, which is too short.
- Reading a 40-hex-character digest as SHA-1 by default. Both are 160 bits.