MD5 / SHA Hash Generator

Tool guide

What is MD5 / SHA Hash Generator?

Hash Generator produces MD5, SHA-1, SHA-256, and SHA-512 digests for UTF-8 text or local files. It is useful for checking downloads, transfers, and build artifacts. Files are read locally in bounded chunks and output is lowercase hexadecimal. MD5 and SHA-1 remain for compatibility only and are not suitable for passwords or secure signatures. Common workflows include the following. Compare a downloaded file with a published SHA-256 checksum. Check whether two text inputs produce the same digest. Create repeatable checksums for build artifacts or test fixtures. The page also documents input boundaries, output behavior, and practical cautions so you can review the result before putting it into an application, configuration, test, or production workflow.

When to use it

Compare a downloaded file with a published SHA-256 checksum.
Check whether two text inputs produce the same digest.
Create repeatable checksums for build artifacts or test fixtures.

How to use it

Choose a hash algorithm.
Enter UTF-8 text or select one local file.
Calculate and copy the hexadecimal digest.
Load one of the realistic examples first to verify the selected options and processing direction before replacing it with your own data.
Review the output, status message, and documented limits; copy, download, or continue only after the result matches your expectation.

Runnable examples

The “Example 1” and “Example 2” buttons load the matching inputs. They cover different structures, directions, or boundaries and can be run directly in the workspace.

Example 1

JSONLane release 1.5
branch=develop
tools=20
checks=unit,e2e,build

Example 2

{"artifact":"out.zip","version":"2026.08.09","environment":"production-candidate"}

Input rules

Text is hashed as UTF-8 bytes.
Files must stay within the size limit shown on the page.
Do not substitute a plain hash for password hashing, key derivation, or digital signatures.
Text input is counted before processing and is limited to 1,000,000 characters on this page; file modes apply the separate file limit shown in the workspace.
MD5 and SHA-1 are collision-broken and unsuitable for security decisions.

Output rules

Output is the lowercase hexadecimal digest for the selected algorithm.
Identical bytes and algorithms produce identical results.
A changed algorithm, encoding, or single byte produces a different digest.
Output reflects only the current input, direction, and options; rerun after changing a mode or value instead of treating an earlier result as current.
Plain hashes are unsuitable for password storage; use Argon2 or scrypt.

Limitations and cautions

MD5 and SHA-1 are collision-broken and unsuitable for security decisions.
Plain hashes are unsuitable for password storage; use Argon2 or scrypt.
Files above the displayed limit are rejected.

How your data is handled

Text and files are read and hashed locally. File contents are not uploaded and no copy is retained by the page.

FAQ

Which algorithm should I use?

Prefer SHA-256 or SHA-512 for integrity checks. MD5 and SHA-1 are kept only for compatibility.

Can this hash large files?

Files are read in chunks with an explicit size limit, reducing peak memory use.

Is a selected file uploaded?

No. The browser reads and hashes it locally.

Why can apparently identical text produce another hash?

Encoding, line endings, BOMs, case, and invisible spaces all change the byte sequence. Text mode consistently uses UTF-8.

Is the whole file loaded into memory?

No. Files within the stated limit are read in chunks and fed incrementally into the hash state.

Can a plain hash securely store a password?

No. Passwords need a salted, deliberately expensive password hash such as Argon2 or scrypt.