RIPEMD-160 hash generator.

RIPEMD-160 is a 160-bit hash designed in 1996 by Hans Dobbertin, Antoon Bosselaers and Bart Preneel at KU Leuven as a European alternative to the NSA-designed SHA-1. It runs two parallel lines of MD4-style rounds and combines them, and it is standardised in ISO/IEC 10118-3.

Bitcoin addresses. A legacy or SegWit address is derived from HASH160, the RIPEMD-160 of the SHA-256 of the public key: SHA-256 for strength, RIPEMD-160 to shorten it to 20 bytes. Litecoin and most Bitcoin forks do the same, and PGP once listed it as an option.

No practical attack exists on the full function; published collisions reach fewer than half its 80 steps. But 160 bits means 80-bit collision resistance, which is below today's margin, so it is not recommended for new designs. Inside Bitcoin it sits behind SHA-256, which is why the combination holds.

The same length, a different design, and a different story: SHA-1 has a public collision since 2017 and RIPEMD-160 does not. Both share the 80-bit collision bound and both should be left for compatibility, not chosen for anything new. RIPEMD-160 is about half the speed of SHA-1.

Nothing leaves your browser. The hash is computed on your machine, by the browser's Web Crypto API or a WebAssembly build of the algorithm loaded on first use, and the page makes no request with your input. You can load the page, go offline and keep hashing.

Drop the file onto the input or choose it with the button, and the tool reads it in your browser and hashes the bytes. Files up to 1 GB work; past that the browser would need the whole file in memory, so the tool declines. Paste the published digest into the Verify field to compare.

Hex is the common form: 40 characters from 0 to 9 and a to f, the same value in upper or lower case. Base64 writes the same 20 bytes in fewer characters, and Base64url swaps + and / for - and _ with no padding. Switch the output and the digest is re-encoded, not recomputed.

Text is hashed as UTF-8 bytes, which is what every language and command line does by default. A trailing newline changes the digest, so `echo -n` or this tool's input, with no newline added, matches a command-line tool run on a file without one.

Turn on HMAC and enter the secret: the tool computes HMAC-RIPEMD-160 over the input with that key, the standard RFC 2104 construction, so the value matches what a server-side HMAC library produces. The key is hashed as UTF-8 text.

No. The RIPEMD-160 hash generator is free and opens without a sign-in, an account or an install.

Nothing. The RIPEMD-160 hash generator holds your input in the page's memory, so closing or reloading the tab clears it, and it saves nothing in this browser.

The toolbar switches to MD4, MD5, and SHA-1 without leaving the page. Each one reads the same input, so you can compare digests side by side.

RIPEMD-160 is computed by a WebAssembly build from the hash-wasm library, which the page loads the first time you hash something and reuses after that.

Yes: the File to RIPEMD-160 page has the same algorithms and options and opens on the file pane. Files are read in your browser and never uploaded.

Not on its own. RIPEMD-160 is built to be fast, and fast hashes are cheap for an attacker to guess against. Passwords need a salted, deliberately slow hash: use Argon2id, Argon2d, and bcrypt from the hash generators, which draw a fresh random salt each time.

Closest to the RIPEMD-160 hash generator: File to RIPEMD-160, SHA-256 hash generator, Double SHA-256 hash generator, SHA-1 hash generator. Each opens on its own page, free and in the browser.

The RIPEMD-160 hash generator is one of 64 in its group. The group's page, /tools/hash, lists them all.

The tool is free. Its interface is built from shadcn.io's own components (Button, Input, Slider and the rest of the registry under /ui), which come in React, Vue, Svelte and Solid. Pro adds the blocks and templates for the product around it.