File to RIPEMD-160.

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 file is read on your machine and hashed there, by the browser's Web Crypto API or a WebAssembly build of RIPEMD-160 loaded on first use; the page makes no request with its bytes. You can load the page, go offline and keep hashing.

Drop the file onto the pane or choose it with the button. It is read into memory and hashed at once, with no size steps and no upload progress because there is no upload. Files up to 1 GB work; a 100 MB file takes well under a second on RIPEMD-160.

Paste the digest the publisher gave you into the Verify field, in hex of either case, with or without spaces, colons or a 0x prefix, or in Base64. The tool says whether it matches the file you dropped. A match means the bytes are exactly the ones that were published.

Hex by default, 40 characters; Base64 and Base64url are one click away and re-encode the same 20 bytes. The download button saves a line in the `digest filename` form that sha256sum-style tools read.

Yes: turn on HMAC and enter the secret, and the file is signed with HMAC-RIPEMD-160 rather than hashed, the same construction a server uses to sign an upload or a webhook payload.

No. The "File to RIPEMD-160" tool is free and opens without a sign-in, an account or an install.

Nothing. The "File to RIPEMD-160" tool 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 RIPEMD-160 hash generator page has the same algorithms and options and opens on the text box. This page opens on the file pane.

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 "File to RIPEMD-160" tool: RIPEMD-160 hash generator, 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 "File to RIPEMD-160" tool 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.