Free Online Hash Generator (MD5, SHA-1, SHA-256)

Generate MD5, SHA-1, and SHA-256 hashes from text or files directly in your browser. File mode reads data incrementally instead of loading the entire file into memory.

Text Input

UTF-8 encoding · no BOM · no trimming

0 characters 0 B UTF-8

Browsers normalize textarea line breaks to LF. Choose CRLF if you need Windows-style text bytes for comparison with another tool.

Hash Algorithms

Select one or more digests to calculate in the same pass.

Security note: MD5 and SHA-1 are broken for collision resistance. Keep them for compatibility and legacy checksums, not for new security-sensitive designs. Raw hashes are also not suitable password-storage schemes.

Hashing happens locally in this browser. No text or file data is uploaded to Flipper File or sent to a third-party service.

Online Hash Generator for MD5, SHA-1, and SHA-256

This hash generator creates MD5, SHA-1, and SHA-256 digests from text or files directly in your browser. It can be used to compare checksums, confirm that a downloaded file has not changed, or generate legacy and modern hash values without sending the source data to a server.

How to Generate a Hash

  1. Choose Hash Text or Hash File.
  2. Enter text or select the file you want to hash.
  3. Select MD5, SHA-1, SHA-256, or any combination of the three.
  4. Click Generate Hashes.
  5. Copy an individual digest, copy all results, or download them as a text file.

MD5

MD5 produces a 128-bit digest, normally displayed as 32 hexadecimal characters. It remains common in old checksum catalogs and compatibility workflows, but it should not be used where collision resistance is a security requirement.

SHA-1

SHA-1 produces a 160-bit digest, normally displayed as 40 hexadecimal characters. Like MD5, SHA-1 is retained mainly for legacy compatibility and existing checksum systems rather than new cryptographic designs.

SHA-256

SHA-256 produces a 256-bit digest displayed as 64 hexadecimal characters. It is the recommended option in this tool for ordinary file-integrity checks and new checksum workflows that do not require a keyed authentication code.

File Hashing Uses the Exact File Bytes

File mode reads the file as binary data and feeds the exact bytes into the selected hash algorithms. It does not decode the file as text or normalize line endings. This is the preferred mode when you need to compare a checksum published for a file.

Text Hashes and Line Endings

Text mode encodes the textarea value as UTF-8 without a byte-order mark. Browser textareas represent line breaks as LF. If you need to reproduce a checksum from Windows-style text, the CRLF option converts LF line breaks to CRLF before UTF-8 encoding. Leading spaces, trailing spaces, and other characters are not trimmed.

Why Two Hashes Can Differ

A one-byte difference produces a different digest. Common causes include CRLF versus LF line endings, a UTF-8 BOM, trailing spaces, different character encodings, or hashing displayed text instead of the original file bytes.

Hashing Is Not Encryption

A cryptographic hash is a one-way digest, not encrypted data. There is no decryption key that restores the original input. For message authentication, use an HMAC. For password storage, use a dedicated password-hashing function with salts and appropriate work factors rather than raw MD5, SHA-1, or SHA-256.

Private Browser-Side Processing

The implementations on this page run entirely in JavaScript in the browser. Files are processed incrementally in chunks, which avoids loading a large file into one giant in-memory buffer. No external hashing library, CDN asset, or conversion API is required.

Our Full Dev Tool Library

Flipper File