DevCoreTools
Security & Crypto

Hash Generator

Generate common text and file hashes in your browser using MD5, SHA-1, SHA-256, SHA-384, and SHA-512.

Text to hash

Text is encoded as UTF-8 before hashing.

Processed locally in your browser. Your input is processed in your browser and is not uploaded or sent to a server. Avoid pasting production secrets, access tokens, private keys, passwords, or sensitive customer data unless you understand the risk.
0 charactersUTF-8 input
Algorithms
Hash letter case

Hashes are not encryption. MD5 and SHA-1 are weak for security and should only be used for legacy checksums or non-security comparisons. Prefer SHA-256 or SHA-512 for modern checksum use.

Hash results

Generate one or more checksums.

Enter text or select a file, choose algorithms, then generate hashes.

SHA-256 is selected by default for modern checksum use.

Paste an expected checksum to compare it with the generated results.

What is a hash generator?

A hash generator converts text or file bytes into a fixed-length digest. The same input and algorithm produce the same checksum, making hashes useful for integrity checks and comparisons.

Text hashes vs file checksums

Text mode hashes the UTF-8 bytes of what you enter. File mode hashes the original file bytes, so it can verify downloads without turning binary content into a large visible string.

MD5 vs SHA-1 vs SHA-256 vs SHA-512

MD5 and SHA-1 remain common in legacy checksum lists but have known collision weaknesses. SHA-256, SHA-384, and SHA-512 are SHA-2 algorithms suited to modern integrity checks.

Hashing vs encryption

Encryption is designed to be reversed with a key. Hashing is one-way and produces a digest for comparison, but it does not hide data or replace secure password storage systems.

Common checksum use cases

  • Verify downloaded files against a publisher checksum
  • Compare build artifacts and release packages
  • Detect accidental content changes
  • Generate identifiers for non-secret content comparison

Security notes for MD5 and SHA-1

Do not rely on MD5 or SHA-1 against intentional tampering. Use them only where compatibility requires an existing legacy checksum. Prefer a publisher-provided SHA-256 or SHA-512 value.

Keep working

UUID GeneratorGenerate standards-compliant UUID values in useful formats and batches.Password GeneratorGenerate secure random passwords locally with configurable length and character rules.HMAC GeneratorGenerate and verify keyed HMAC signatures locally with common SHA algorithms.Base64 Encoder/DecoderEncode and decode Base64 and Base64URL text in your browser.JWT DecoderDecode JWT headers, payloads, claims, and timestamps locally.
URL Encoder/DecoderComing soon
Encode and decode URL components and query-string values.
HTML Entity Encoder/DecoderEncode and decode HTML entities, symbols, and special characters locally.

Frequently asked questions

Does this Hash Generator upload my text or files?

No. Hashing runs locally in your browser, and input, filenames, file contents, hashes, and expected checksums are not sent through analytics.

What is the difference between hashing and encryption?

Hashing produces a one-way digest for comparison. Encryption protects data with a key and is intended to be reversible by an authorized party.

Which hash algorithm should I use?

Use SHA-256 for most modern checksum verification. Use SHA-512 when a source specifically publishes or requires it.

Are MD5 and SHA-1 secure?

No. Both have practical collision weaknesses and should be limited to legacy, non-security checksum compatibility.

Can I verify a downloaded file checksum?

Yes. Select File checksum mode, choose the publisher's algorithm, select the file, and paste the expected checksum to compare.

Can hashes be reversed?

A cryptographic hash is not designed to be reversed. Weak or predictable original values may still be guessed and checked against a hash.