We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
RIPEMD Hash Generator
Was this tool helpful to use?
Your feedback helps us make it better
Generate RIPEMD-128, RIPEMD-160, RIPEMD-256, and RIPEMD-320 hashes online. Supports text, Hex, and Base64 inputs.
Overview
Understand what the tool solves, how it works, and the boundaries of its data.
This page calculates one algorithm, RIPEMD-160, from text input. A hash digest is a fixed-size result used to compare or identify input; it is not ciphertext and there is no decryption step. RIPEMD-160 produces 160 bits, or 20 bytes. The page presents the same digest as lowercase hexadecimal, uppercase hexadecimal, or Base64 text.
Hex letter case changes only how the same bytes are written. Base64 is another text encoding of those digest bytes, not another hash variant. The original RIPEMD-160 paper describes the algorithm and its 160-bit output.
Guide
Follow the workflow and verify inputs and outputs with practical examples.
Type or paste the content to hash. An empty input does not produce a digest. Spaces, punctuation, line breaks, and letter case are part of the text, so preserve them when matching a result from another system.
The page recalculates as the input changes. The three output representations appear together; compare the one required by your protocol or the other system.
Copy lowercase hex, uppercase hex, or Base64 as required. Keep the algorithm and exact input alongside a saved digest so a later comparison uses the same rules.
Use cases
See how the tool fits into real work and everyday tasks.
When a legacy format or system specifically calls for RIPEMD-160, calculate the text digest and compare it with the expected value using the agreed output encoding.
When two systems report different digests, compare the exact text first, including whitespace and line endings, then confirm both use RIPEMD-160 and the same text encoding assumptions.
For a learning exercise, change one character or add a space and observe that the result changes. This illustrates a hash’s dependence on its input; it does not measure password strength.
Q&A
Find concise answers to common questions and confusing cases.
No. A digest is not an encrypted copy of the input and this page has no inverse operation. Keep the original text if it must be recovered.
The algorithm outputs 160 bits, equal to 20 bytes. Two hexadecimal characters represent each byte, giving 40 hex characters. Uppercase and lowercase show the same value.
No. It calculates RIPEMD-160 only. If a protocol specifies a different variant, use an implementation that matches that exact variant.
No. It is a text representation of the same digest bytes. It can be decoded back to those bytes, but that does not recover the original text.
Notes
Review scope, result limitations, and important precautions before use.
This page provides no random salt, configurable work factor, or password-specific hashing scheme. NIST guidance describes password verifiers using a suitable salted password-hashing scheme with a cost factor. Do not use a RIPEMD-160 text digest as a substitute for that password-storage process.
For an integrity comparison, matching digests alone do not prove who supplied the data, whether a source is trusted, or whether a transaction is authorized. Confirm the algorithm and exact input on both sides.
Related
Discover related tools, collections, and available API capabilities.