UTF-8 text includes spaces and line endings
Text mode encodes the editor value as UTF-8. A final newline, tab, non-breaking space, different Unicode character, or case change produces a different digest.
Free online developer utility · no registration or login
Free Hash Generator Online
Use this hash generator to create a SHA digest from exact UTF-8 text or one local file. Choose SHA-256, SHA-384, SHA-512, or legacy SHA-1, then compare, copy, or download the result as hex or Base64 without sending the source to an external hashing service.
- Text or one local file
- SHA-256, SHA-384, SHA-512, SHA-1
- Expected digest comparison
- Copy or TXT download
Hash and checksum workspace
Generate and compare a SHA digest
Hash exact text or one local file, then compare the complete result with an optional trusted digest. Source bytes stay in this browser page.
Source
Hash result
Generate a digest to review and use the complete value.
No digest generated yet
The full hash, source byte count, digest size, output representation, and optional match status will appear here.
How to generate and verify a hash
Keep the source, algorithm, representation, and expected value aligned before treating two digests as comparable.
- Step 1
Choose text or one local file
Enter the exact UTF-8 text or choose one local file up to 50 MB. Spaces, line endings, and every file byte affect the result.
- Step 2
Select the exact SHA algorithm and format
Use SHA-256 by default unless your protocol or trusted reference specifies SHA-384, SHA-512, or legacy SHA-1. Match hex or Base64 to the expected value.
- Step 3
Generate, compare, copy, or download
Paste an optional expected digest for an automatic full-value comparison, generate the hash, review the source facts, then copy or download the complete result.
Common hashing and checksum tasks
Use the digest as an exact byte fingerprint, then interpret a match only within the trust boundary of the expected value.
- Calculate and verify a SHA-256 checksum for a downloaded file
- Hash an exact UTF-8 payload for a test fixture
- Compare lowercase hex, uppercase hex, and Base64 representations
- Check a legacy SHA-1 reference without using it for a new security design
Hash the exact input bytes
Hash functions operate on bytes, not on how content looks on screen. Small invisible differences explain many checksum mismatches.
File checksums use the original bytes
File mode reads the selected file as bytes rather than converting it to visible text. Re-saving, repacking, recompressing, or changing metadata can change those bytes.
Hex and Base64 display the same digest differently
Select the representation used by the trusted reference. Lowercase and uppercase hex contain the same digest value, while Base64 uses a shorter encoded alphabet.
Choose a SHA algorithm
Use the algorithm required by the protocol, release page, or existing dataset. A digest from one SHA variant cannot be compared with another.
Use SHA-256 as the common default
SHA-256 returns a 256-bit digest, shown as 64 hexadecimal characters. It is widely used for file checksums and content fingerprints.
Use SHA-384 or SHA-512 when specified
These algorithms produce longer digests. A longer output is not a reason to substitute one when a system explicitly requires SHA-256 or another exact algorithm.
Treat SHA-1 as a legacy compatibility option
SHA-1 remains visible in old checksum lists and protocols, but known collision weaknesses make it unsuitable for new collision-sensitive security designs.
Verify a checksum without overstating it
A digest is useful evidence only when the expected value, source, and intended security property are understood.
Compare the entire trusted checksum
Match every character against a value obtained from a trusted source. The built-in comparison removes manual scanning but cannot judge whether the reference itself is trustworthy.
A match does not prove publisher identity or file safety
If an attacker can replace both a file and its displayed checksum, a plain hash does not prove who published it. A match also is not a malware scan.
Use HMAC, signatures, or password hashing for different jobs
Use HMAC or a digital signature when authenticity is required. Password storage needs a salted, deliberately expensive password-hashing or key-derivation scheme.
Hash Generator FAQ
Direct answers about SHA variants, exact bytes, checksum comparison, local file handling, and what an unkeyed digest cannot prove.
What is a hash generator?
A hash generator applies a deterministic hash function to exact input bytes and returns a fixed-length digest. The same bytes and algorithm produce the same digest; changing even one byte changes the result.
Which hash algorithms are supported?
This page uses the browser Web Crypto API for SHA-256, SHA-384, SHA-512, and SHA-1. SHA-256 is the default. SHA-1 is included only for comparison with legacy values and should not be chosen for new collision-sensitive designs.
Can I generate a SHA-256 checksum for a file?
Yes. Choose Local file, select one file up to 50 MB, keep SHA-256 selected, and generate the digest. The page reads the original file bytes in this browser tab.
How do I compare an expected checksum?
Paste the complete trusted digest into the optional Expected digest field before or after generating. The page ignores surrounding whitespace and hexadecimal letter case, then shows Match or Mismatch for the selected algorithm and representation.
Why does my hash differ from another result?
Confirm the algorithm, exact bytes, text encoding, line endings, leading or trailing spaces, and output representation. Hashing visible hexadecimal characters is different from decoding those characters into bytes first.
What is the difference between hex and Base64 output?
Hex and Base64 represent the same digest bytes with different alphabets and lengths. Uppercase and lowercase hexadecimal are equivalent values; Base64 is a different textual representation and must be compared with another Base64 value.
Can a hash be decrypted?
A cryptographic hash is not encryption and has no decryption key. Weak or predictable inputs can sometimes be guessed and re-hashed, so a digest should not be treated as reversible protection.
Should I use SHA-256 to store passwords?
No. Password storage should use a dedicated salted, deliberately expensive password-hashing or key-derivation function selected for your platform, not a fast general-purpose SHA digest.
Does a matching checksum prove a file is safe?
No. A match confirms that the calculated bytes match the expected digest. It does not scan for malware or prove publisher identity unless the expected value came through a separate trusted or authenticated channel.
Are my text and files uploaded?
The hashing workflow reads pasted text and selected file bytes in this browser tab and does not send the source to an external hashing service. File size is capped at 50 MB because the browser digest API reads the complete input into memory.
Related developer tools
Generate identifiers, encode bytes, format JSON, or inspect a token payload in the next browser-local workflow.
UG Developer
UUID Generator
Generate one random UUID v4 or a batch of up to 100 in your browser. Choose canonical, uppercase, GUID-braced, or compact display, then copy individual values or export the full list as TXT, CSV, or JSON with no registration or login.
Open tool BE Developer
Base64 Encoder & Decoder
Encode or decode UTF-8 and URL-safe Base64 text online. Paste a value, copy the result, or download it from your browser without registration or login.
Open tool JF Developer
JSON Formatter & Validator
Paste JSON or open a file to format, validate, beautify, or minify it. Choose indentation, review parser errors, and copy or download the result in your browser with no login.
Open tool JD Developer
JWT Decoder
Inspect JWT headers, payloads, claims, expiry times, and signature segments in your browser. Decode locally with no login; this tool does not verify signatures.
Open tool