Web Tools DocGuides

How to use Hash Verifier

Get the best out of Hash Verifier: every option explained, a worked example, and what to check when the output is not what you expected.

Updated July 31, 2026

What it does

Generate a digest from text and compare it against an expected checksum. It runs entirely in your browser — your input never leaves your device.

Options

Every setting this tool exposes, straight from the code that validates it.

OptionTypeDefaultWhat it does
texttextText to hash. Required.
algorithmone of: md5, sha1, sha256, sha384, sha512sha256Which algorithm to use. Different algorithms produce different, incompatible output. Defaults to sha256.
expectedtextOptional expected hash to compare against.

Worked example

Run these settings on the tool page:

  • text: hello
  • algorithm: sha256

You get:

Algorithm: SHA256
Actual: 2cf24dba5fb0a30e26e83b2ac5b9e29e1b161e5c1fa7425e73043362938b9824
Expected: not provided
Match: Not checked

Getting the result you want

Most of the control here is in the options above. If the output is not what you expected, the setting to check first is algorithm and expected — those change the shape of the output rather than the input it accepts.

Troubleshooting

  • Nothing happens / the output stays empty. text is required — the tool waits until you provide it.
  • It is slow on very large input. Everything runs in your browser, so speed depends on your device. Very large inputs are best split up, or run through the API where the work happens on our servers.

Automating it

The same logic is available as a REST endpoint, so you can run it from a script, a CI job or your own app.

Bash
curl "https://api.toolsxpo.com/v1/hash-verifier" \
  -H "Authorization: Bearer $TOOLSXPO_KEY"

It costs 1 credit per successful call. See the full endpoint reference, or try it in the playground.

Tools covered here

Hash Verifier

Security

security

Related