Skip to main content
Utilnivo

Developer

Utilnivo

Hash Generator

Generate SHA-256, SHA-384, and SHA-512 hashes.

No registration
  • On your device

Browse more in Developer or all tools.

Private on your device

Your information stays on your device and is not uploaded.

Related tools

Enter text and choose SHA-256, SHA-384, or SHA-512. Hashes use secure random generation on your device and update as you type.

SHA-256 and related digests detect accidental changes—a single character change produces a completely different hash. Use File Checksum when you need a hash of a downloaded binary rather than a text string typed into this tool.

Hashes are one-way for practical purposes but are not password storage. Applications should use bcrypt, scrypt, or Argon2 for user passwords, not SHA-256 alone.

Compare digests case-insensitively when verifying against hex strings published in release notes.

MD5 and SHA-1 remain useful for legacy checksum files but should not be used for new security designs—prefer SHA-256 or SHA-512 for integrity checks today.

HMAC is not the same as a plain hash—do not compare an HMAC-SHA256 output from an API with a raw SHA-256 of the message body.

Uppercase versus lowercase hex is cosmetic—normalize case before comparing a computed digest to a published checksum.

How to use this tool

1. Paste or type the text you want to fingerprint. 2. Select SHA-256, SHA-384, or SHA-512 from the algorithm menu. 3. The hex digest updates automatically as you type—there is no separate run button. 4. Compare the output against a published checksum or expected value. 5. Copy the hash with one click. Processing runs on your device; your text is not uploaded.

Worked example

Example: the word "hello" with SHA-256 produces a 64-character hex digest. Switch to SHA-512 for a 128-character digest when your reference document specifies that algorithm. For hashing files or downloads, use File Checksum instead—this tool hashes text only.

When to use this

  • Verifying a release checksum against a published SHA-256.
  • Creating digests for configuration drift checks.
  • Debugging webhook signature strings in development.
  • Comparing hashed environment variable text across servers.

Common examples

  • GitHub release SHA-256 → hash the exact release tag string and compare against the checksum published on the release page (use File Checksum for the downloaded .zip).
  • Webhook signing secret → SHA-256 of the shared secret for log correlation—not for password storage (use bcrypt or Argon2 in apps).
  • Deployment config snippet → SHA-384 digest to confirm the same environment variable text across staging and production.
  • Config string `prod-v2.3.1` → SHA-256 to compare with CI-published digest.
  • License paragraph text → SHA-384 fingerprint for internal document registry.

Common mistakes

  • Using SHA-256 for password storage instead of bcrypt or Argon2.
  • Hashing text with wrong encoding (UTF-8 vs ASCII).
  • Expecting MD5 support when only SHA-256/384/512 are offered.
  • Comparing hashes without normalizing line endings in input text.

How it works

Enter text and choose SHA-256, SHA-384, or SHA-512. Hashes are generated with secure random generation on your device.

Limitations

Results are based on the inputs you provide and may not cover every edge case. This tool is for general use and is not professional advice.

Privacy and file handling

Your data stays on your device and is not uploaded.

Related Hash Generator workflows

Explore focused guides that reuse this hash generator with different examples and FAQs.

FAQ

Frequently asked questions

Which algorithms are available?

SHA-256, SHA-384, and SHA-512. MD5 and SHA-1 are not offered.

Is my text stored?

No. Everything stays on your device.

Is Hash Generator free to use?

Yes. Utilnivo tools are free to use and do not require an account.

Part of these workflows

This tool is one step in a longer job. Jump straight to your step or open the full workflow guide.

Related pages

Page last reviewed: