Hash GeneratorText, file, checksum verification
en

AppHelp

Generate and verify text or file hashes

Paste text or drop a file to compute five common digests at once, switch between HEX and Base64, or compare an expected checksum without uploading your content.

15 UTF-8 bytes

Digest results

All algorithms at once

MD5Legacy
SHA-1Legacy
SHA-256
SHA-384
SHA-512
Security note: MD5 and SHA-1 are included for compatibility checks only. Use Argon2id, scrypt, bcrypt, or another dedicated password hashing function for stored passwords.

Common tasks

  • hash generator online
  • sha256 generator
  • file hash calculator
  • checksum verifier
  • md5 generator
  • sha1 generator
  • sha384 generator
  • sha512 generator
  • base64 hash generator
  • verify sha256 checksum
  • text hash generator
  • browser local hash tool

Quick answer

Enter text, choose a local file, or open Verify mode. The tool computes MD5, SHA-1, SHA-256, SHA-384, and SHA-512 together and returns HEX or Base64 without uploading the input.

How to use

  1. 1. Choose Text, File, or VerifyUse Text for pasted UTF-8 content, File for a local file up to 50 MB, or Verify to compare text against an expected checksum.
  2. 2. Provide the inputType or paste text, or drag and drop a file. Digests update automatically in the browser.
  3. 3. Choose HEX or Base64Switch the result encoding, optionally uppercase HEX, then copy one digest or all five.
  4. 4. Verify a checksumSelect the algorithm and paste an expected hexadecimal or Base64 digest to see a match or mismatch result.

Examples

SHA-256 of hello

Input
hello
Output
2cf24dba5fb0a30e26e83b2ac5b9e29e1b161e5c1fa7425e73043362938b9824

The input is encoded as UTF-8 before hashing.

MD5 of an empty string

Input
Output
d41d8cd98f00b204e9800998ecf8427e
MD5 is shown for compatibility, not modern security.
Verify a downloaded file
Input
Local file plus a publisher-provided SHA-256 checksum
Output
Digest matches or Digest does not match
A match confirms byte equality with the published digest, not publisher trust.
Common use cases
  • Compare a downloaded file with a published checksum
  • Generate SHA-256 or SHA-512 content fingerprints
  • Debug UTF-8, HEX, and Base64 hashing pipelines
  • Check legacy MD5 or SHA-1 values for compatibility
  • Verify text against a known digest without uploading it
Edge cases
  • Text is encoded as UTF-8, so a different character encoding produces a different digest.
  • File hashing reads the whole file into browser memory and is limited here to 50 MB.
  • MD5 and SHA-1 are collision-broken and should not protect passwords or security-sensitive signatures.
  • A checksum match proves the bytes match the expected digest, not that the source is trustworthy.
Features
  • MD5, SHA-1, SHA-256, SHA-384, and SHA-512
  • UTF-8 text hashing with live updates
  • Local file hashing up to 50 MB
  • Hexadecimal and Base64 output
  • Uppercase hexadecimal option
  • Expected checksum verification
  • Per-digest and copy-all actions
  • Explicit MD5 and SHA-1 legacy warnings
Related tools
HMAC GeneratorAdd a secret key when message authenticity matters.Base64 Encoder and DecoderInspect or transform Base64 data without hashing it.UUID GeneratorGenerate random or time-ordered identifiers rather than deterministic digests.
Frequently asked questions
Which hash algorithms are supported?
The tool computes MD5, SHA-1, SHA-256, SHA-384, and SHA-512 for every input. SHA algorithms use Web Crypto and MD5 uses a local implementation.
Can I hash a file without uploading it?
Yes. Choose or drop a file up to 50 MB. The browser reads and hashes it locally; AppHelp does not receive the file.
How does checksum verification work?
The tool hashes your text with the selected algorithm and compares it with an expected HEX or Base64 digest after normalizing whitespace and HEX letter case.
Should I use MD5 or SHA-1 for passwords?
No. MD5 and SHA-1 are legacy digest algorithms. Stored passwords need a slow, salted password hashing function such as Argon2id, scrypt, or bcrypt.
What is the difference between HEX and Base64 output?
They encode the same digest bytes. HEX is longer and human-friendly for checksums; Base64 is shorter and common in APIs and integrity attributes.