Skip to content
UniKit

Hash text

Compute MD5, SHA-1, SHA-256 and SHA-512 digests of any text with synchronous, fully client-side code, shown as both hex and Base64.

Runs in your browserEvery computation happens in your browser — your data never leaves this device.

Bytes: 0
Digest
Hex
Base64

Hashing is one-way: the original text cannot be recovered, and the same input always produces the same digest.

What this tool does

  • Verify a downloaded file: paste the official MD5 or SHA-256 value, hash the text and compare digit by digit — no command-line tooling needed.
  • Compute digests while writing build scripts or cache keys: the same text always yields the same value, which makes it a good file-name or dedupe key.
  • Check whether two pieces of content are byte-identical: Chinese text and emoji easily hide fullwidth spaces or invisible characters, and matching digests prove the bytes match.
  • Compare algorithms side by side: one input yields MD5, SHA-1, SHA-256 and SHA-512 as both hex and Base64, plus the byte length.

Example

Input

Hello, UniKit! 你好,工具站!

Output

SHA-256 hex: 4adb88b65c7e4dbb24805d5c979e28c37a58103bc0eabba8e926361082db35cd
SHA-256 Base64: StuItlx+TbskgF1cl54ow3pYEDvA6ruo6SY2EILbNc0=
Bytes: 42

Text is UTF-8 encoded before hashing, so a Chinese character counts as 3 bytes. For ASCII "abc" the MD5 is 900150983cd24fb0d6963f7d28e17f72 and the SHA-256 is ba7816bf8f01cfea414140de5dae2223b00361a396177a9cb410ff61f20015ad.

Frequently asked questions

Are MD5 and SHA-1 still usable for file verification?

They are fine against accidental corruption but not against tampering: both have known collisions, so an attacker can craft a different file with the same digest. Use SHA-256 or SHA-512 when security matters.

Why do the byte count and character count differ?

Digests operate on bytes, and text is encoded as UTF-8 first: a Chinese character is usually 3 bytes, emoji can be 4, and ASCII stays at 1. So "你好" is 6 bytes rather than 2 characters, and the byte figure on the page is exactly what was hashed.

What is the difference between hex and Base64, and which should I use?

They encode the same bytes differently: hex uses 0-9a-f at two characters per byte, while Base64 is denser at about 1.33 characters per byte. Watch the case when comparing across systems (toggle uppercase hex if needed) and do not strip the trailing = padding from Base64.

Can a digest be reversed back to the original text?

No. Hashing is one-way, and since infinitely many inputs map onto a finite output space, collisions must exist. A digest can only tell you whether the content changed — it cannot restore or encrypt it.

Does hashing make any network requests?

No. All four algorithms are synchronous pure JavaScript implementations running locally in your browser, the page sends no requests, and sensitive text is never uploaded.

Keywords:hashmd5sha1sha256sha512摘要哈希校验digestchecksumbase64

Related tools