RIPEMD-160 hash

160 bits, printed as 40 lowercase hex characters, the same length as SHA-1 and a completely different value. The tool has no options, so the digest depends only on the bytes of the file you dropped, and it appears on the line under the title and your file name.

It is half of it. Bitcoin HASH160 is RIPEMD-160 applied to a SHA-256 digest, so you need two passes: hash with SHA-256 first, then feed those raw bytes through this tool. One run of this tool alone is a plain RIPEMD-160 of whatever file you dropped.

It is a cryptographic hash from the 1990s that is still used where formats demand it. Its 160-bit output gives a smaller collision margin than a 256-bit digest simply because it is shorter. Use it to match an existing format such as a Bitcoin address, not as your default pick for something new.

Usually because of what was hashed rather than how. HASH160 takes the raw 32 bytes out of SHA-256, not the 64 character hex text of it, and a file containing hex characters hashes to something entirely different. Check you fed in raw bytes with no trailing newline.

Yes. Each file is hashed separately and returns its own digest, so a batch gives you a list rather than one value. It all runs in this tab through hash-wasm in a Web Worker, with no upload and no account, and it keeps working with the network switched off.