Developer workflow
Verify a download with checksums
Release pages publish MD5 or SHA digests so you can confirm a binary was not corrupted or tampered with in transit. This workflow hashes the file locally, cross-checks string digests, and handles Base64 when vendors publish encoded fingerprints.
Category: Developer · Last updated: 2026-07-22
Step-by-step path
Steps (3 tools)
Hash the file you downloaded, compare digests, and encode strings when docs ship Base64.
Step 1: Hash the file
Tool: File Checksum Calculator
Compute MD5, SHA-1, or SHA-256 for the downloaded file.
Open File Checksum Calculator- On your device
- No signup
- Stays on your device
Step 2: Hash a reference string
Tool: Hash Generator
Reproduce digests from published text samples when needed.
Open Hash Generator- On your device
- No signup
Step 3: Decode Base64 digests
Tool: Base64 Encoder & Decoder
Convert Base64 fingerprints from docs into a comparable form.
Open Base64 Encoder & Decoder- On your device
- No signup
When to use this workflow
- A vendor publishes SHA-256 next to a ZIP or installer.
- You need to confirm two copies of a build artifact match.
- Documentation shows a Base64-encoded digest instead of hex.
Tips
Tips for better results
- Compare digests character-by-character—one differing nibble means a mismatch.
- Prefer SHA-256 over MD5 when both are offered.
- Hashing large files happens on your device; keep the tab open until it finishes.
FAQ
Frequently asked questions
Is my file uploaded?
No. Checksums are computed locally in the browser. The file bytes are not sent to Utilnivo.
What if the hash does not match?
Re-download from the official source and verify again. Do not run mismatched installers.
Which algorithm should I use?
Match whatever the publisher printed. If they list SHA-256, use that algorithm in File Checksum.
Keep going
Related workflows
Provision staging credentials
DeveloperGenerate passwords, UUIDs, and hashes for dev, QA, and fixture data.
- Generate password
- Generate UUIDs
- Hash sample input
Debug a JWT or API token
DeveloperDecode a bearer token, pretty-print JSON claims, and inspect Base64 segments.
- Decode JWT
- Format JSON
- Decode Base64
