Free Hash Generator Online

Compute MD5, SHA-1, SHA-256, SHA-384, SHA-512 and CRC32 of text or files in one call, as hex or base64, with optional HMAC signing.

Free tool: 20 requests per minute.

Result

Press “Run” to see the result.

The Hash API computes checksums and cryptographic digests of a string or a file. By default it returns all supported algorithms at once – MD5, SHA-1, SHA-256, SHA-384, SHA-512 and CRC32 – or only the ones you list in algorithm (comma separated, e.g. sha256,md5).

Send the input as text (query or JSON), as a raw text body, or hash binary data: upload a file in the multipart field file, post the raw bytes, or pass base64 in file_base64. Files can be as large as your plan allows (Free 5 MB, Starter 20 MB, Pro 50 MB). The response also reports the number of bytes hashed.

Set hmac_key to get HMAC signatures instead of plain digests (HMAC-SHA256 is what most webhook providers use), and encoding=base64 for base64 output instead of hex. CRC32 is always returned as 8 hex characters.

Use this in your code

curl -X POST "https://apibox.io.vn/v1/hash" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"text":"hello world"}'

API documentation → Get a free API key

FAQ

How do I compute an HMAC-SHA256 signature?

POST {"text": "payload", "algorithm": "sha256", "hmac_key": "your-secret"}. Add "encoding": "base64" if the provider expects base64 (Shopify, for example) instead of hex (GitHub, Stripe).

Can I hash a file instead of text?

Yes. Upload it as multipart field "file", send the raw bytes as the request body, or pass "file_base64" in JSON. The limit is your plan’s file size (5/20/50 MB).

Is MD5 still safe to use?

Not for passwords or signatures: MD5 and SHA-1 are broken against collisions. They are still fine for non-security checksums and legacy compatibility; use SHA-256 or SHA-512 for anything security related, and a slow KDF such as bcrypt or Argon2 for passwords.