Why this tool exists
The UUID + Hash Lab keeps identifier minting and digest comparisons in one workspace so you can seed fixtures, issue API keys, and share checksum evidence without swapping scripts.
Fixture seeding
Mint UUID batches for tests or migrations and hand QA the exact identifiers you generated.
Key distribution
Issue API keys or device identifiers with hashed copies so downstream services can compare safely.
Integrity audits
Attach checksums to every export so reviewers can prove nothing changed between systems.
Quick start
Toggle between UUID batches and hash digests without losing your settings.
- Open the UUID + Hash Lab and decide whether you are generating identifiers or hashing a payload—the UUID tab stays selected by default.
- Choose a UUID version, batch size (1–50), case, and format or paste your payload and toggle the digest algorithms you need.
- Submit the active form to refresh results, then copy the batch, checksums, or digest entries directly into tickets and runbooks.
Supported inputs
- UUID generator accepts batch sizes from 1 to 50 per request with versions v4, v7, or ordered plus hyphenated or compact output.
- Switch between lower and upper casing to match consumers before copying a batch or exporting checksums.
- Hash lab preserves every newline and space while computing MD5, SHA-1/256/384/512, and CRC32B digests in one request.
Mode 01
UUID batch walkthrough
- Pick the UUID version that fits your workload: v4 for random identifiers, v7 for time-ordered rows, or Ordered for sequential inserts.
- Set the batch size within the 1–50 guardrails and choose hyphenated or compact plus the expected letter case.
- Click Generate batch to populate the output list and enable the “Copy batch” shortcut that strings every UUID with newline separators.
- Review the checksum table to share MD5, SHA, and CRC signatures so teammates can validate the entire batch without rerunning the tool.
Mode 02
Hash digest walkthrough
- Paste any payload—JSON fixtures, API responses, or CLI snippets—into the Hash digest helper and keep an eye on the live character count.
- Toggle the algorithms you care about; selections persist so refreshing the page or sending multiple submissions keeps the same lineup.
- Submit the form to compute every digest together; each card shows the algorithm label, digest length, and a copy action for handoffs.
- Use Reset when you need a clean slate without disturbing the UUID generator settings on the left column.
Exports & verification
Copy-friendly controls keep UUID batches and checksum notes consistent between teammates.
- Use the “Copy batch” control to grab every UUID—perfect for `.env` variables, fixture files, or quick seed scripts.
- Checksum cards cover MD5, the SHA family, and CRC32B so you can paste them into release notes or compare against `shasum -a` output in your terminal.
- Hash digest cards double as a verification log: copy signatures per algorithm and drop them into CI artifacts or ticket comments.
Outputs & snippets
Every submission populates batch lists, checksum tables, and digest cards so you can copy or script against them.
UUID batch output lists every identifier with individual copy actions plus a master batch copy.
Batch checksums provide uppercase algorithm labels with digests for MD5, SHA-1/256/384/512, and CRC32B.
Hash digests surface character counts so you immediately know how long each signature should be.
Snippet lineup
PHP
Use hash($algorithm, $value) inside standalone PHP scripts or CLI utilities to confirm digests.
Node.js
crypto.createHash(algorithm).update(payload).digest("hex") mirrors the lab output exactly.
Python
hashlib.new(algorithm, payload.encode()).hexdigest() before saving to notebooks or ETL jobs.
Bash
printf "payload" | shasum -a 256 lets you validate the SHA-256 card from any shell.
SQL
MySQL offers SHA2(payload, 256) while Postgres pgcrypto exposes digest(payload, "sha256").
PowerShell
Use Get-FileHash -Algorithm SHA256 .\uuids.txt to verify exports on Windows hosts.
Field notes
Keep deliveries audit-friendly and ready for verification.
- Lock casing and formatting before copying so the identifiers you ship match downstream expectations.
- Pair each shared batch with the checksum list so recipients can rerun shasum or certutil for instant verification.
- Keep the hash lab open beside incident tickets—paste payloads from logs to prove integrity without storing them elsewhere.
- Chain this guide with the Timestamp Converter when you need to timestamp UUID issuance and hash confirmation together.