DoItAl

Data utility

Hash & File Checksum Generator

Hash UTF-8 text or local files with SHA-256, SHA-384, SHA-512, SHA-1 or MD5. Compare expected hex checksums using a bounded local worker and clear legacy-algorithm guidance.

Browser-local • No upload

Loading tool controls…

Local tool controls

SHA-256 or stronger is the normal choice. MD5 and SHA-1 are legacy compatibility checksums: do not use them for modern signatures or collision-resistant security. Raw hashes, including SHA-256, are not suitable password storage.

Text is encoded as UTF-8 exactly as held by the text field; casing, spaces and newlines affect its digest. Limit: 250,000 code units / 1 MiB UTF-8. Files use their original bytes. Worker execution stops after 15 seconds and is cancelled when input changes. Checksum equality confirms matching digest values, not the source’s authenticity.

What this tool does

Computes SHA-256, SHA-384, SHA-512, SHA-1 or MD5 for UTF-8 text and local files, and compares a pasted expected hexadecimal checksum.

How to use it

  1. Choose text or a local file and a hash algorithm; use SHA-256 or stronger for normal checksum work.
  2. Generate in the local worker, inspect the input byte count and copy the hexadecimal result.
  3. Paste an expected checksum and verify it; casing and whitespace are ignored, while invalid length or characters are explained.

Worked example

UTF-8 ‘abc’ has SHA-256 ba7816bf8f01cfea414140de5dae2223b00361a396177a9cb410ff61f20015ad. Paste that value, including uppercase or spaced hex, to get MATCH. Adding a newline to the text changes the digest; a different valid digest gives DOES NOT MATCH.

Processing and explanation

The worker encodes text as UTF-8 or reads original file bytes. Native Web Crypto implements the SHA algorithms; a small RFC 1321 implementation supplies MD5 for legacy compatibility. Hashes are fixed-size digests, not reversible encodings or encryption. Expected checksums are normalized for hex casing/whitespace and compared with the computed value.

Limits and common mistakes

Files up to 20 MiB, rejected before reading; text up to 250,000 code units / 1 MiB UTF-8. Web Crypto digests require whole input buffers, so this is bounded whole-file processing, not streaming. A local worker keeps the UI responsive and stops after 15 seconds or when input changes. Whitespace, case and text-field line endings affect bytes. MD5/SHA-1 are legacy algorithms unsuitable for modern signatures or collision-resistant security. Raw SHA is also unsuitable password storage. A matching checksum does not authenticate the source that supplied it.

Privacy and your input

Files, filenames, source text, expected hashes and generated checksums stay in tab/worker memory and are excluded from network requests, analytics and storage. Selecting an oversized file does not read its bytes. Clearing inputs or leaving the page cancels the worker.

Frequently asked questions

Why did the same-looking text produce another hash?
Encoding, Unicode sequences, spaces and newlines can differ. Text mode hashes the field’s UTF-8 bytes; file mode hashes the file’s original bytes.
Is MD5 safe for a security signature?
No. MD5 and SHA-1 are included for legacy published checksum compatibility, not modern collision-resistant security.
Does MATCH prove a download is trusted?
It confirms equal checksum values. Trust still depends on obtaining the expected checksum from a reliable source.

Material content update: