Legacy distribution
Some firmware mirrors still publish only MD5 checksums. Generate both MD5 and SHA-256 digests so you can satisfy legacy tooling while documenting the stronger alternative.
Browser tools for developers
Check a file checksum, inspect a JWT, convert Base64, or reproduce an AES-GCM payload across browser, Node.js and Python. Start with a tool below; examples explain the input, result and limitations.
Protect text with AES-GCM and PBKDF2 tokens that stay on-device.
Generate MD5, SHA-1, and SHA-256 digests locally with Web Workers.
Decode claims and verify HMAC signatures without network calls.
Convert any text to or from Base64 without leaving your browser.
Validate, format, and diff JSON without network calls.
Format, minify and inspect XML locally with tree view and JSON conversion.
Experiment with regular expressions and capture groups locally.
Encode components and inspect query parameters locally.
Create collision-resistant UUID v4 identifiers using Web Crypto.
Build strong passwords with custom length, charset, and entropy.
Translate Unix timestamps into readable dates and back again.
Convert case, slugify, and clean strings on-device.
Switch between HEX, RGB, HSL, and Tailwind palettes instantly.
Design QR codes for text, Wi-Fi, contacts, email, or SMS locally.
Generate EAN and Code 128 barcodes and download crisp PNG output.
Look up your public IP using disclosed external services.
Produce paragraphs, lists, and markdown filler text fast.
Run the AES interoperability guide or read how these tools are checked.
Generate MD5, SHA-1, and SHA-256 from text or files. Everything runs locally with Web Workers.
MD5 and SHA-1 are weak. Prefer SHA-256 for integrity.
A cryptographic hash is a one-way function that turns any input into a fixed-length digest. The best algorithms are deterministic, fast to compute, and make it computationally impractical to reverse the process or find two inputs that collide.
Unlike encryption, hashing is irreversible by design. HashyTools keeps every calculation in your browser so you can vet files, configuration snippets, and secrets without transmitting them anywhere.
Pick the digest that matches your security and compatibility requirements. Older algorithms remain for legacy workflows, but modern integrity checks should prefer SHA-2 family members such as SHA-256.
| Algorithm | Digest length | Typical use today | Security notes |
|---|---|---|---|
| MD5 | 128 bits | Legacy checksum validation, non-security critical fingerprints. | Broken collision resistance. Never use for new security boundaries. |
| SHA-1 | 160 bits | Legacy APIs, old TLS or Git history verification. | Practical collision attacks. Avoid except when backward compatibility is mandatory. |
| SHA-256 | 256 bits | Modern integrity checks, digital signatures, blockchain data. | Considered secure and widely supported. Recommended default. |
Different environments still surface MD5 or SHA-1 requirements. Use these guidelines to decide when a compromise is acceptable and when you should upgrade.
Some firmware mirrors still publish only MD5 checksums. Generate both MD5 and SHA-256 digests so you can satisfy legacy tooling while documenting the stronger alternative.
Prefer SHA-256 combined with a signature (for example, GPG or code signing certificates) so tampering triggers a digest mismatch and fails signature validation.
Never store plain hashes. Use battle-tested password hashing functions such as Argon2, scrypt, or bcrypt. HashyTools can help verify exported digests, but the heavy lifting belongs in a purpose-built KDF.
Enter abc (without a newline), select SHA-256, and compare with this digest. A trailing newline produces a different result.
ba7816bf8f01cfea414140de5dae2223b00361a396177a9cb410ff61f20015ad
const bytes = new TextEncoder().encode('abc');
const digest = await crypto.subtle.digest('SHA-256', bytes);
console.log(Array.from(new Uint8Array(digest), b => b.toString(16).padStart(2, '0')).join('')); import hashlib
print(hashlib.sha256(b'abc').hexdigest())A checksum detects a changed file only when the expected value comes from a trusted source. A plain SHA-256 digest is not a password-storage scheme.
A cryptographic hash is a one-way mathematical function that converts any input into a fixed-length digest that is designed to be collision resistant. If the digest changes by even one bit, you know the source data changed.
MD5 and SHA-1 are vulnerable to collision attacks, which means attackers can craft different inputs that produce the same digest. They should no longer protect certificates, signed binaries, or any security sensitive workflow.
Yes. HashyTools processes files locally with Web Workers, streams progress, and never transmits the bytes outside of your browser session.
No. The tool runs entirely on-device, and neither your inputs nor the resulting digests touch a server controlled by HashyTools.
Paste the expected digest into the comparison field. HashyTools instantly re-computes the hash and flags a match or mismatch so you can finish your release checklist quickly.