Compare two text blocks
Normalized Levenshtein similarity and token overlap both run locally.
Hash local files or pasted text, compare expected checksums, measure similarity, and export manifests without uploading your data.
Use file mode for release artifacts and downloads, or text mode for quick payload checks and copied values.
Switch between local file hashing and pasted text hashing.
Use SHA-256 for most checksum sharing unless you need a different format.
SHA-1, SHA-256, SHA-384, and SHA-512 all run locally in your browser.
Useful for API payload checks, copied secrets, or quick integrity comparisons.
OzHashKit can auto-detect the likely algorithm from the checksum length when it matches a known SHA/MD5 pattern.
Checksum comparison works best with a single current result.
Paste an expected checksum to show the likely algorithm and compare it with the current result.
Use CSV for spreadsheets, checksum sums for release packages, or Markdown for team notes.
The selected manifest style controls the final file extension when you download.
| Name | Size | Hash | Status |
|---|
You can copy or download the current manifest without uploading your files or text.
Comparison happens locally in your browser. OzHashKit does not upload your files or text.
Exact matches come from hashes. Similarity for non-identical files is heuristic unless the files are treated as text and compared directly.
Normalized Levenshtein similarity and token overlap both run locally.
SHA-256 runs first. If files differ, OzHashKit uses a safe local heuristic based on file type.
Exact duplicate groups scale well. Heuristic similarity checks stay limited and optional.
No batch analysis is running.