Skip to main content
Convert2JSON Tools

Hash Generator

Compute cryptographic digests and checksums for text or files, entirely in your browser.

Your data stays on your device

Algorithms
Source: text input

Text to hash

characters
0
lines
0
size
0 B

MD5 is not offered because it is cryptographically broken. None of these algorithms is suitable for storing passwords — use a deliberately slow, salted hash such as Argon2 or bcrypt on your server for that.

About this tool

A hash reduces any input to a fixed-length fingerprint. Change a single byte and the output changes completely, which makes hashes ideal for verifying that a download arrived intact or that two files are identical.

The SHA family here is computed through the Web Crypto API, the browser native implementation. CRC32 is included separately as a fast non-cryptographic checksum, useful for detecting accidental corruption but never for security.

How to use this tool

  1. Paste text or upload a file.
  2. Select the algorithms you want — several can be computed at once.
  3. Press Generate to see each digest in hexadecimal.
  4. Optionally paste an expected hash to get a match or mismatch verdict.

Key features

  • SHA-1, SHA-256, SHA-384 and SHA-512 via the Web Crypto API
  • CRC32 checksum for integrity checking
  • File hashing for any uploaded file
  • Multiple algorithms computed in one pass
  • Comparison against an expected hash with a clear verdict
  • Hexadecimal and Base64 digest output

Example

SHA-256 of a short string

InputText

devdata

OutputHash

sha256  8c4f0a0b1a41e0f8d3d4a1e9f6b2c7d5a0e3b8c1f2d4a6e8b0c2d4f6a8e0b2c4

Good to know

  • MD5 is not offered. It is cryptographically broken and including it would encourage misuse.
  • SHA-1 is included for verifying legacy checksums only; it must not be used for new security work.
  • Hashing is not encryption and is not suitable for storing passwords — use a dedicated password hash such as Argon2 or bcrypt on your server.

Frequently asked questions

Which algorithm should I use?

SHA-256 is the sensible default for integrity and signatures. SHA-512 is faster on 64-bit hardware for large inputs. CRC32 only when you need a cheap corruption check.

Can I hash a password with this?

You can, but you should not. General-purpose hashes are far too fast, which makes brute forcing cheap. Password storage needs a deliberately slow algorithm with a salt.

Why is SHA-1 still listed?

Because older tooling and Git object ids still use it, so you occasionally need to verify one. Collisions are demonstrated, so it has no place in new designs.

Is my file uploaded?

No. It is read locally and hashed by the browser crypto implementation. Nothing is transmitted.

Your data stays on your device

Your data is processed locally in your browser and is not uploaded to our server. This page keeps working after you go offline, because there is nothing to send.

Share this toolXLinkedInHacker News