TIGER Hash Calculator

Tiger digests for compatibility checks

A hash function maps input text to a fixed-length digest. This Tiger page calculates a digest from typed text and lets you choose one of six labels: Tiger128,3; Tiger160,3; Tiger192,3; Tiger128,4; Tiger160,4; or Tiger192,4. The first number names the output length in bits; the final number selects the configured round variant. The original Tiger design describes a three-pass core and a 192-bit result. Shorter output lengths and the four-round options are distinct compatibility selections supported by this tool.

A digest is not encrypted text and cannot be decoded back into the input. It is useful when two parties already agree on the algorithm and exact input representation, for example while reproducing a legacy value. The result is shown in lowercase and uppercase hexadecimal, plus a Base64-form output. Confirm the receiving system’s expected encoding before comparing the Base64 field.

Text must match byte for byte for a comparison to be meaningful. Spaces, line endings, Unicode representation, and capitalization are part of the input. A visually identical string can therefore produce a different digest if its encoded bytes differ.

Reproduce a known Tiger value

1. Confirm the full variant name

   Ask whether the expected value is Tiger128, Tiger160, or Tiger192 and whether it uses 3 or 4 rounds. “Tiger” alone may be ambiguous.

2. Enter the exact text

   Paste only the characters being hashed. Check for leading or trailing spaces, newline characters, and the agreed text encoding.

3. Calculate and compare

   Select the same variant, generate the digest, and compare like-for-like output encodings. Hexadecimal letter case can be normalized before comparison.

If two outputs differ, first verify the variant and input bytes. Do not assume a digest mismatch means the source file or account was tampered with until the complete comparison process is checked.

Questions about Tiger output

Use an older hash only when a format requires it

Tiger output is appropriate here for compatibility, comparison, or learning. Do not choose it for new password storage, authentication, or a security protocol without a current expert review and an algorithm specified for that purpose.

• A matching digest is not proof of who created the text; the expected digest must come through a trusted channel.
• This page hashes text rather than uploaded files, and Tiger calculations are sent to a service for processing. Do not enter sensitive text.
• Base64 output can have different conventions depending on whether the encoded input is the digest bytes or a displayed text representation. Verify the required format before using it in an interface or protocol.