Release checks
Confirm published artifacts still match the checksum you were given.
Documentation
Checksum Comparison documentation
Compare checksum values with normalization controls, mismatch diagnostics, and copy-ready canonical output.
Overview
Use it when the format needs to change, not the meaning
Use checksum comparison when two digest strings should match but may differ in case, separators, or prefixes.
Mismatch triage
Separate formatting noise from a real integrity problem.
Handoff cleanup
Standardize copied digests before putting them in tickets or runbooks.
Supported inputs
Bring clean source text and keep the direction straight
- Accepts hex digests copied from CLIs, APIs, package registries, or release notes.
- Uppercase, lowercase, colons, dashes, spaces, and `0x` prefixes can be normalized as needed.
- Length-based hints help you notice when two digests may belong to different algorithms.
Walk through it
Follow the same sequence you see in the tool
Workflow
Compare two checksums
Paste the source and candidate values to see whether they match.
- Paste both checksum values into the comparison fields.
- Leave normalization toggles on first so formatting differences do not hide a match.
- Review the verdict, mismatch position, and similarity score before you decide what to fix.
Workflow
Normalize one digest
Use the normalization controls when you only need one cleaned checksum to share.
- Paste the checksum you want to clean.
- Turn the toggles on or off until the format matches your target system.
- Copy the normalized value once the output is stable.
What you get
Check the result before you copy it into the next step
Verdict
A match or mismatch result shows whether the two inputs are equivalent after normalization.
Normalized digest
A cleaned value is available for sharing when you only need the canonical form.
Mismatch detail
The first mismatch position and similarity score make near-misses easier to review.
Avoid these mistakes
Small input problems create the biggest conversion errors
Different algorithms
Matching lengths do not prove the same algorithm was used.
Strictness set too low
Keep strict length enabled when a truncated digest should never pass.
Raw input assumed clean
Check for spaces, separators, and prefixes before treating a mismatch as final.
Glossary
Decode the terms before you act on them
This section translates the most technical labels on the page into plain language so you can interpret the output without opening another tab.
Digest
A digest is the checksum or hash value produced from the source input. It is the value you compare against another copy.
Hex digest
A hex digest is a digest written with hexadecimal characters, usually `0-9` and `a-f`.
Normalization
Normalization means cleaning formatting differences such as case, prefixes, spaces, or separators before comparing values.
Strict length
Strict length means the comparison will reject values that do not have the exact expected digest length.