A cryptographic hash maps input bytes to a fixed-size digest. A small input change should produce a different digest, which makes hashes useful for comparing data and detecting accidental changes. This tool accepts text, encodes it as UTF-8, and calculates a hexadecimal digest using the browser Web Crypto SubtleCrypto digest operation. Hashing is one-way in the sense that the digest is not a reversible encoding; it is not encryption and does not provide a way to retrieve the original phrase from the output. Choose an algorithm that matches the actual verification requirement.
Enter text in the input, select SHA-1, SHA-256, SHA-384, or SHA-512, then click Generate Hash. SHA-256 is selected initially. The action is disabled when the input contains only whitespace, and the Clear control resets both input and output. A result panel names the chosen algorithm and provides a plain-text output file. Changing the selected algorithm does not automatically recompute an existing result; select the algorithm first and run Generate Hash again so the displayed label and digest correspond.
As a checkable example, hash the exact text `hello` with SHA-256. A known digest for those five lowercase ASCII characters is `2cf24dba5fb0a30e26e83b2ac5b9e29e1b161e5c1fa7425e73043362938b9824`. Typing `Hello`, adding a trailing space, or using a different algorithm produces a different digest. This illustrates why byte-for-byte input matters: when comparing digests, confirm capitalization, line endings, spaces, and encoding, not just the visible words in an editor.
The four available choices produce different digest lengths: SHA-1 is 160 bits, SHA-256 is 256 bits, SHA-384 is 384 bits, and SHA-512 is 512 bits. The UI presents output as lowercase hexadecimal characters. SHA-1 is retained as a compatibility option but has known collision weaknesses and should not be selected for new security-sensitive designs. SHA-256 is a common general-purpose choice; use SHA-384 or SHA-512 when a protocol or system explicitly calls for it.
Typical uses include comparing a text payload with a trusted reference, checking that a copied configuration string is unchanged, and learning how algorithm selection changes output size. Checksum Generator also supports file input and adds SHA-384 to its choices, while File Hash Checker computes several digests for a selected file and can compare a supplied expected value. HMAC Generator is the appropriate related choice when a shared secret must authenticate a message; an ordinary hash alone cannot prove who produced the input.
The hash operation uses browser Web Crypto and the component submits no text to a remote hashing endpoint. Still, avoid placing sensitive text in shared screens or saving the output into public logs if the digest itself could reveal information through guessing. A plain hash is not an appropriate way to store passwords: password storage needs a dedicated slow password-hashing scheme with unique salts, neither of which this tool provides. Very long input can be limited by browser memory, and Web Crypto errors appear in the output as an error message.
When validating a download, compare the digest from the file itself against a value obtained through a trusted channel; generating both values from the same untrusted copy proves little. Do not treat matching hashes as a digital signature or identity assertion. The tool hashes a UTF-8 text representation, not an uploaded file's raw bytes. Use File Hash Checker or Checksum Generator for file workflows, and preserve the full hexadecimal string when copying because a missing character makes a digest comparison fail.
Hash reproducibility depends on encoding and exact bytes. This helper converts JavaScript text to UTF-8 before digesting, so Unicode characters become a sequence of bytes rather than one abstract character. Two systems can display visually identical text but hash different byte sequences if normalization or line endings differ. When reproducing a digest from another language, compare the precise encoded payload and avoid adding a newline in a terminal command unless the reference includes one. This is especially important when debugging signed API payloads or configuration values.
The hexadecimal output is convenient for logs and documentation, but it is not a compact, human-readable summary of the original text. Do not use a prefix of a digest unless the protocol explicitly specifies truncation and its security implications. If you need to compare a large set of records, build a tested application workflow rather than manually selecting and copying each output. The browser tool is most helpful for one-off inspection and education, not automated integrity enforcement across a deployment pipeline.
A digest can also be used as a content address in systems that map identical bytes to the same key, but this page does not create such a store or check for existing objects. If the input contains low-entropy secrets, an attacker may try candidate values and compare their hashes, so publicizing the digest can reveal a guess. Treat hash values as potentially sensitive metadata when their input domain is known, and choose a keyed construction where the problem requires authentication rather than a public fingerprint.
A reliable comparison process records both the digest and its algorithm near the source version being checked. If two people get different results, first exchange exact input bytes or a file copy rather than retyping the phrase. Confirm whether the original contained a byte-order mark, newline, or Unicode normalization. These details are often the cause of mismatches, and changing the algorithm will not fix a difference in the actual message.