Text & code / MULTIVERTO
Calculate the SHA-256 digest of UTF-8 text in your browser. A hash is one-way and cannot be decoded.
Apply each text tool to the previous result.
01 / Guide
SHA-256 produces a 256-bit digest, shown as 64 hexadecimal characters. It is not reversible encryption.
SHA-256 is useful for checksums and fingerprints. For passwords, use a dedicated salted password hash such as Argon2 or bcrypt instead.
02 / Example
hello2cf24dba5fb0a30e26e83b2ac5b9e29e1b161e5c1fa7425e73043362938b982403 / Guide
SHA-256 produces 256 bits, displayed here as 64 hexadecimal characters. Use it to fingerprint a short piece of text or compare a known value with a trusted published checksum. Type the exact string, including any spaces or final newline, then compare every character of the digest. The text hello and Hello produce different results; adding a trailing space changes it again. The tool hashes UTF-8 bytes, so visually similar Unicode strings can differ if their byte representations differ.
For file integrity, this text field is only suitable when you know the exact text bytes being hashed. Pasting the rendered contents of a file can change line endings or character encoding; a file checksum tool is more appropriate for arbitrary files. A matching SHA-256 value supports a comparison only when the expected value came from a trusted source. It does not authenticate the author or protect a password. Use a salted password-specific algorithm for password storage, not a raw SHA-256 digest.
A cryptographic hash turns input bytes into a fixed-length digest. For the same bytes and algorithm, the digest is deterministic; changing even one byte will ordinarily produce a very different result. This converter first writes the entered text as UTF-8 bytes, then uses the browser’s cryptographic implementation and displays the digest in hexadecimal. Line breaks, spaces, letter case and Unicode normalization can all affect the byte sequence. When comparing two digests, make sure the source bytes and algorithm really match.
A digest can help check whether data changed if you compare it against a trusted expected value. It does not by itself prove who created data, and an attacker who can replace both a file and its published digest can defeat that check. Hashing is not encryption: there is no key and no decoding operation to recover the original input. A fast general-purpose SHA digest is also unsuitable on its own for password storage. Password systems need a dedicated salted, deliberately expensive method such as Argon2 or bcrypt.
Enter the exact text whose SHA-256 digest you need and compare the 64-character output with an independently trusted value. This calculation runs in the browser through its cryptographic API; the text is not uploaded to a hashing service. If the API is unavailable in the current browser context, the tool reports that limitation. Do not delete a final space or newline simply to make two values match. A discrepancy can reveal a difference in bytes, algorithm choice or character encoding rather than a calculation error.
For a reproducible comparison, record whether the source text included line endings and whether it had been normalized before hashing. Copying visible text from a document can change hidden characters, so work from the same original source whenever possible. Compare the complete digest, not just the first few characters. If the expected checksum is published beside an untrusted download, seek a trusted channel for it; a matching value that an attacker supplied along with altered data does not establish authenticity.