Provision staging credentials
DeveloperGenerate passwords, UUIDs, and hashes for dev, QA, and fixture data.
3 steps
- Generate password
- Generate UUIDs
- Hash sample input
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.
Hash the file you downloaded, compare digests, and encode strings when docs ship Base64.
- 3 steps
- About 6 minutes
- Data stays on this device
- Updated 2026-07-24
Workflow
Steps to complete
Work through each step in order. Progress is saved in this browser. Utilnivo does not save uploaded files permanently between tools.
Progress: 0 of 3 steps complete (0%)
Hash the file
File Checksum CalculatorCompute MD5, SHA-1, or SHA-256 for the downloaded file.
Open File Checksum Calculator- On your device
- No signup
- Stays on your device
Hash a reference string
Hash GeneratorReproduce digests from published text samples when needed.
Open Hash Generator- On your device
- No signup
Decode Base64 digests
Base64 Encoder & DecoderConvert Base64 fingerprints from docs into a comparable form.
Open Base64 Encoder & Decoder- On your device
- No signup
Track progress
Your progress
0 of 3 complete (0%). Your progress is saved in this browser.
Printable step list with checkboxes—generated on your device.
Results
Overall output
What you entered and what each step produced appear here. Values used in the next step are passed when supported. Data stays in this browser only.
Run each step and submit the calculator form. Key results will appear here as a connected summary.
Progress: 0 of 3 steps marked complete (0%).
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