Microdeck.tools 100% In-Browser

SHA Checksum & Webhook HMAC Verifier

New

Verify downloaded installers, ISO images, release tarballs, and Stripe/GitHub/Shopify webhook signatures using hardware-accelerated browser `crypto.subtle` APIs. Hash local files without uploading a single byte, compare digests against pasted `SHA256SUMS` manifests, or generate HEX/Base64 HMAC signatures.

100% In-Browser No Server Storage Instant Results

1. Local File / Text SHA Checksum & Manifest Verifier

2. Webhook & API HMAC Signature Generator

Computed SHA-256 (hex)

Did this tool save you time? Help keep Microdeck free and maintained. Completely optional · From $3.

How It Works Under the Hood

Streams selected local file bytes or UTF-8 text buffers directly into `window.crypto.subtle.digest()` across `SHA-1`, `SHA-256`, `SHA-384`, and `SHA-512`, performs length-normalized XOR comparisons against `SHA256SUMS` lines, and derives raw HMAC tags via `crypto.subtle.sign('HMAC', ...)`.

Step-by-Step Instructions

1

Choose a local file (archive, binary, ISO) or type UTF-8 text to compute all four SHA digests instantaneously.

2

Paste an official digest string or `sha256sum` manifest line to verify MATCHED vs MISMATCH.

3

In Section 2, pick `HMAC-SHA256`, `HMAC-SHA512`, or `HMAC-SHA1` plus `HEX` or `BASE64` format.

4

Enter your webhook secret and raw body payload to reproduce API signatures locally.

Key Features & Performance

  • Native hardware-accelerated Web Crypto hashing handles multi-hundred-MB downloads fast
  • Simultaneously outputs SHA-256, SHA-512, SHA-384, and SHA-1 digests for quick copy
  • Parses GNU `sha256sum` / `SHA256SUMS` manifest formats (`<hash> <filename>`) cleanly
  • Built-in HMAC-SHA256 / SHA-512 signature generator supports both HEX (GitHub/Stripe) and Base64 (Shopify) formats
  • Zero server exposure: safe for private webhook secrets and unpublished release artifacts

Methodology, Formulas & Technical Standards

Comparison uses constant-time character XOR accumulation across lowercase hex strings, matching standard GNU coreutils checksum formatting (`hash *filename` or raw hex).

Common Real-World Use Cases

  • Verifying integrity of downloaded CLI binaries, crypto wallets, or OS installers against publisher checksums
  • Debugging `X-Hub-Signature-256` or webhook HMAC mismatches locally without exposing signing secrets
  • Validating S3/R2 artifact integrity manifests before production deployment
  • Generating quick API HMAC request signatures while testing curl/insomnia integrations

Worked Examples & Edge Cases

SHA256SUMS Manifest Match

Input
File digest vs `a948904f...  release.tar.gz`
Output
MATCHED — release.tar.gz

Ignores binary asterisk flags (`*filename`) and case differences.

Shopify vs GitHub HMAC Output

Input
Secret + JSON payload -> Base64 vs Hex
Output
Instant HMAC-SHA256 encoded to exact webhook header format

Always hash the exact un-prettified raw payload string bytes.

Limitations, Scope & Accuracy Notes

  • • Browser Web Crypto (`SubtleCrypto`) intentionally omits legacy MD5 due to collision insecurity and supports SHA-1/256/384/512 cleanly.
  • • Multi-gigabyte disk ISO images (`>2 GB`) may exceed single `ArrayBuffer` limits in memory-constrained browsers.

Local Browser Processing & Privacy

Traditional web converters upload your documents, snippets, or media files to remote servers. SHA Checksum & Webhook HMAC Verifier runs inside your browser tab:

Processed in This Tab

Your input text and files are processed locally without uploading payloads to a processing server.

No Tool Payload Logging

Microdeck does not log or store the files or inputs you paste into tool workspaces (normal static hosting/CDN requests still load page assets).

Tab Memory Lifecycle

Working outputs stay in your browser tab and are released when you reset the tool or close the tab.

Frequently Asked Questions

Why does HMAC verification sometimes differ from my server code?

Check whether your server hashes raw request body bytes (`req.text()`) versus re-serialized JSON (`JSON.stringify()`), and check `hex` vs `base64` encoding.

Does uploading a 200 MB release file send anything over my internet connection?

No. `file.arrayBuffer()` stays completely local inside browser RAM.

Why is SHA-256 recommended over SHA-1?

SHA-1 has practical collision weaknesses; SHA-256 and SHA-512 remain industry standard for tamper verification and HMAC signing.

Can I verify multiple checksum lines at once?

Yes. Paste the entire `SHA256SUMS` block and each line reports MATCHED or MISMATCH cleanly.

Explore Related Micro-Tools

Support Microdeck

Completely optional · From $3 · No account required

Choose an amount (USD):Selected:$5

Minimum support amount is $3 USD.

Completely optional · From $3 · Checkout opens on Gumroad.