Using MD5 or SHA-1 for security
MD5 and SHA-1 are broken for collision resistance; keep them for legacy checksums and compatibility checks, not security decisions.
Generate MD5, SHA-1, SHA-256, and SHA-512 hashes from text with instant, in-browser results. Use it for checksums, fingerprints, webhook debugging, and integrity checks. For password storage, use bcrypt, scrypt, or Argon2 instead.
Continue with a related workflow or open the next tool that usually follows this task.
Use this workflow when an API response, webhook, cookie, or configuration value contains Base64 text that needs to be inspected before debugging.
OpenRelated toolEncode or decode Base64 text with UTF-8 support and local-only processing.
OpenRelated toolDecode JWT header, payload, claims, and expiration locally.
OpenRelated toolGenerate bulk UUID v4 and GUID values locally with format options.
OpenEnter or paste text (all Unicode supported).
In Live mode, MD5, SHA-1, SHA-256, and SHA-512 update as you type.
Copy any hexadecimal digest with one click.
Compare against a published checksum to verify file integrity.
Compute a digest and compare it with a vendor-published checksum to confirm a download or copied value was not modified.
Check whether a webhook body, signed message, or canonical request string matches the digest expected by your integration.
Use digests as stable fingerprints to deduplicate content, compare text snapshots, or build content-addressable references.
Understand how hashes support block fingerprints, proof-of-work examples, and Merkle-tree style verification.
Generate consistent digests for cache keys, sharding tests, fixture IDs, and indexing experiments.
Learn password hashing concepts, then use a dedicated slow hash such as Argon2, bcrypt, or scrypt in production.
MD5 and SHA-1 are broken for collision resistance; keep them for legacy checksums and compatibility checks, not security decisions.
Passwords need slow, salted password hashing such as Argon2, bcrypt, or scrypt. A raw SHA digest is too fast for safe password storage.
Whitespace, newlines, character encoding, and file mode changes produce different digests even when text looks similar.
Hash a release note, payload, or manifest string and publish the digest so users can compare their local copy.
web-utils-release-2026-05-13SHA-256: d36a4170ae98dcf5050e74ae158ca5693ade7c3853370ee27907db4f6b557253A one-character change produces a completely different digest, which is useful when validating configuration, webhook payloads, or copied data.
invoice-total=1250
invoice-total=1251Different MD5/SHA digests are produced for each line.A cryptographic hash maps arbitrary input bytes to a fixed-length digest and is designed to be one-way.
Useful properties include determinism, collision resistance, and the avalanche effect: small input changes create very different digests.
Prefer SHA-256 or SHA-512 for integrity work; MD5 and SHA-1 are deprecated for security but still appear in legacy checksum workflows.
A. No. Hashing is one-way and irreversible, while encryption is reversible with the correct key. You cannot "decode" a cryptographic hash.
A. Use SHA-256 or SHA-512 for modern integrity and fingerprinting work. Keep MD5/SHA-1 only for legacy or non-security checks such as quick compatibility checksums.
A. Yes, collisions can exist in theory. There are practical collisions for MD5 and SHA-1; no practical collision attacks are known for SHA-256/512 today.
A. Do not store passwords with MD5, SHA-1, SHA-256, or SHA-512. Use dedicated password hashing functions like bcrypt, scrypt, or Argon2 with salts and proper parameters.
A. No. Hashes are computed locally in your browser from the text you enter. Nothing is uploaded or stored by this tool.
Use these focused guides when you need a practical workflow before opening the tool.
Use this workflow when an API response, webhook, cookie, or configuration value contains Base64 text that needs to be inspected before debugging.
Workflow guideUse this workflow when a vendor, GitHub release, or teammate gives you a checksum and you need to confirm that the file you downloaded has not changed.
Workflow guideUse this workflow when a login, API request, or permission check fails and you need to inspect token claims before changing auth code.
Workflow guideUse this workflow when a URL needs to move from paper, a slide, a package, or a physical sign into a phone camera quickly.
Workflow guideUse this workflow when you need realistic unique identifiers for examples, tests, seeded records, or temporary objects without exposing production IDs.
Workflow guideUse this workflow when a browser request, API response, redirect, or CDN cache behaves differently than expected and you need a clean header-level view first.
Explore more developer tools
Encode or decode Base64 text with UTF-8 support and local-only processing.
Decode JWT header, payload, claims, and expiration locally.
Generate bulk UUID v4 and GUID values locally with format options.
Hash Function Support: Generate MD5, SHA-1, SHA-256, and SHA-512 hashes with live results in your browser. See Security Note for algorithm guidance.
Standards: NIST FIPS 180-4 (SHA-2), RFC 1321 (MD5), RFC 3174 (SHA-1)
Security Note
Do not use MD5 or SHA-1 for security purposes. Use only for non-security checksums.
SHA-256 or higher is recommended.
💡 Live Mode: Results update automatically as you type.
Enter text above to generate hashes