CrateX.app

Hash Checksum

Generate SHA-256, SHA-512, or legacy SHA-1 hashes locally for text or one file, choose lower or upper hex, and compare against an expected checksum.

Text Input

Characters

0 / 50,000

Hash Checksum

Quick Start

Choose Text or File mode

Enter text or select one file

Select SHA-256, SHA-512, legacy SHA-1, and hex case

Click Compute and copy the hash

Paste expected checksum to compare

Common Scenarios

Download verification

Compare with official checksum to confirm file integrity

Backup validation

Compare hashes before and after to ensure data integrity

Request digest checks

hash request bodies or configs for logs and consistency checks; not HMAC and not a request signature.

Deduplication

Quickly detect identical files via hash comparison

Usage Advice

Use SHA-256 for daily verification—good balance of security and performance

Use SHA-512 for high-security scenarios—stronger collision resistance

SHA-1 is for legacy compatibility only—not recommended for new use cases

Watch case sensitivity: Official checksums are often lowercase; switch output format to match

URL Quick Fill

Prefill text hash mode from the URL hash. text is required, expected-hash is optional, and algorithm/output format stay on the current default or saved setting. File mode is not supported from the URL.

view: View mode (text only for URL fill)

text: Text to hash (required, up to 256 characters)

expected-hash: Expected hexadecimal hash (optional)

Example: #text=hello&expected-hash=2cf24dba5fb0a30e26e83b2ac5b9e29e1b161e5c1fa7425e73043362938b9824

Hash parameters stay in the browser for tool prefill; CrateX.app does not record them.

Do not put private text, secrets, tokens, or unreleased file hashes in URLs.

Limitations & Compatibility

Requires WebAssembly hashing and File.stream support in a modern browser.

File mode streams chunks without a configured file size cap, but GB-scale files still depend on browser, disk, and device performance.

SHA-1 has known collision vulnerabilities—use only for legacy compatibility

Privacy & Security

Processing runs in your browser. Text input, expected checksum, mode, algorithm, and hex-case choices may stay in the current browser session or browser storage. If you save a workspace or enable WebDAV sync, those values may be saved according to your sync settings; the selected file is saved only when you explicitly save or sync it as a workspace attachment. Hash results and match status are recalculated from the current text or file and expected checksum, and are not stored as separate results. This page does not fetch URLs or send file bytes for hash calculation. On shared devices, clear text, expected checksum, selected file, and site data when needed.

FAQ

Continue with these related tools for the next step.