Calculate SHA-512 entirely in your browser and compare a downloaded release file with the known value—without uploading the file.
A SHA-512 digest is a content fingerprint. If your result exactly matches the value published for that specific version and asset, the bytes match. A checksum cannot judge what the program does, whether an unrelated mod is trustworthy, or whether a file from a different version is appropriate.
Select the downloaded asset in the tool below. Your browser reads the file locally and produces hexadecimal and Base64 SHA-512 values. Compare the result character for character with the download center or the corresponding release metadata. Filename, version, algorithm, and encoding must all match.
The verifier uses the browser File and Web Crypto APIs. It does not send the file to a server. The result exists only in the current page session. Large AppImage files can take longer on mobile hardware because the browser must read the entire file.
Delete the incomplete or unexpected copy, confirm available disk space, and download the exact asset again. Do not rename, recompress, or edit a file before comparison; any content change correctly produces a different digest. If repeated downloads differ, stop and verify the release information before running the file.
No. Hashing happens in the browser using the local file bytes.
Confirm the algorithm and encoding. This page shows SHA-512 in both hexadecimal and Base64; a SHA-256 value will never match.
No. It only proves that the selected file matches the referenced digest. Third-party mod code has its own provenance and risk.
Research note: September 13, 2026 snapshot. Release assets and platform behavior can change; verify important details again before installation.
Recommended path: read this guide → download or create a minimal profile → record the result → expand to the full modpack.