Generate RIPEMD-160 hash values from text or file input, commonly used in Bitcoin address derivation.
RIPEMD-160 squeezes any input - a phrase, a file, a public key - down to a fixed 40-character hexadecimal digest. Designed in 1996 as a strengthened successor to the original RIPEMD after weaknesses were found in it, the hash is best known today as the second stage of Bitcoin address derivation, where it runs on the SHA-256 hash of a public key. Everything is computed locally in your browser; nothing is uploaded. The thing users most often misread: the result is a hash, not an encryption and not an address - it cannot be reversed, and turning it into a Bitcoin address takes further encoding steps.
A concrete input and expected output from the current implementation.
Input
abc
Expected output
8eb208f7e05d987a9b044a8e98c6b087f15a0bfc
"abc" is a standard test input in hash vector suites, and its RIPEMD-160 digest is the well-established value shown here: any correct implementation of this algorithm must return these exact 40 characters. Forty hex characters are 20 bytes, which is exactly 160 bits - the length the algorithm's name refers to.
RIPEMD-160 is a Merkle-Damgard-style hash that processes the input in 512-bit blocks through two parallel lines of five 32-bit words, then combines the lines at the end. Every input, however long, yields the same 20-byte result, shown as 40 lowercase hex characters. The function is deterministic - identical bytes in, identical digest out - and a single changed bit propagates through the rounds and changes roughly half the output bits.
What gets hashed is the raw byte sequence. Text you type is encoded as bytes (UTF-8 by default), and a file is hashed byte-for-byte as stored, so a trailing newline, a CRLF line ending, or a file re-saved in a different encoding changes the digest even when the text looks identical. Leading and trailing spaces count too. To reproduce a published checksum, the bytes must match exactly.
No. Hashing is one-way: neither the original text nor a public key can be recovered from the 160-bit digest, and addresses are even more lossy because Base58Check drops data. Anyone offering to "unhash" a RIPEMD-160 value into a private key is running a scam - this tool only hashes forward.
Because an address is several steps beyond this tool's output: SHA-256 the public key, RIPEMD-160 that result to get the Hash160, prepend a version byte, append a checksum, then Base58Check-encode. Also confirm you used the same key format (compressed or uncompressed) the wallet did; the two hash differently.
The example and behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.
Generate strong, random passwords with customizable length, character sets, and complexity requirements.
Analyze password strength with entropy scoring, crack-time estimates, and improvement suggestions.
Create cryptographically random strings for API keys, tokens, salts, and unique identifiers.
Create QR codes for URLs, text, Wi-Fi credentials, vCards, and more with customizable size and colors.
Scan and decode QR codes from uploaded images or your device camera to extract embedded data.
Compute MD5, SHA-1, SHA-256, and SHA-512 checksums to verify file integrity and detect tampering.