UUID Studio

UUID Studio

SHA-1 Hash

SHA-1 for legacy compatibility only.

  • đź”’ No data stored or uploaded
  • ⚡ 100% client-side
  • 🆓 Free, no account
Click Convert when ready

Override only when Auto cannot parse your paste. Changing this loads a matching sample into Input — click Convert to run. Use Load sample to cycle every format example.

All conversions

Read-only representations of the same 16 bytes. Every textual form is listed here, not in “Prefer format”.

Paste two values: if both sides are valid JSON, a structural diff appears; otherwise UUID / bytes are compared when both decode to the same format.

A
B

Create or edit JSON here (syntax colors), then format, validate, or convert - same as MongoDB $binary UUID blobs on the Convert tab once detected.

New document

Hash, HMAC, AES-GCM/CBC + RSA-OAEP, codecs, JWT decoding, UUID v4, and secure random - all client-side. JWTs use Base64URL (three segments), not a single MIME Base64 block - use Decode JWT below, not raw Base64 decode.

Examples

  • Input 
    legacy-content

About SHA-1 Hash

SHA-1 has been broken for collision resistance since 2017 and shouldn't be used for anything security-sensitive anymore - but it's still baked into old Git internals, legacy TLS configurations, and artifact formats that haven't been updated.

This exists for exactly that legacy case: quickly reproducing a SHA-1 checksum an older system expects. For anything new, use SHA-256 or stronger.

FAQ

Should I use SHA-1 for new code?
No - use SHA-256 or stronger.