UUID v4
Use for database records and public object IDs when creation order does not matter.
Tiny tools, fresh entropy
Random generator
Generate identifiers, secure key material, hashes, and encrypted test values locally—with clear guidance for choosing the right tool.
01
Fresh values
Ready-to-copy values generated with cryptographically secure browser randomness. Each card explains its intended use.
UUID v7
Use for record IDs that should sort roughly by creation time.
ULID
Use in URLs or logs when you want a compact, time-sortable ID.
256-bit hex value
Use when an application asks for 32 random bytes written as hexadecimal.
URL-safe token
Use for reset links, invitations, API credentials, or other opaque secrets.
Password / key builder
Choose a format, or build a random string with an exact character count.
32-bit integer
Use for test fixtures, seeds, or a value across the full unsigned 32-bit range.
Random color
Use for mock data, avatars, charts, or design exploration.
02
Hash lab
Turn the same source text into repeatable fingerprints. These are integrity tools, not password-storage functions.
Source text
Enter the exact text you want to fingerprint, or generate a disposable seed.
Waiting
SHA-256
Use to verify that text has not changed or to create a stable fingerprint.
SHA-512
Use when a protocol or integration specifically requires a 512-bit SHA-2 digest.
Deterministic UUID v8
Use when identical text must always map to the same UUID-shaped identifier.
Color fingerprint
Use as a quick visual hint that two source values differ.
03
Crypto kit
Fresh salts, keys, and nonces for modern browser-supported cryptography.
Random salt
Use a unique salt for every password hash or password-based key.
AES-GCM IV
Use once for one AES-GCM encryption with one key.
AES-256 key
Use to encrypt and decrypt data with AES-256-GCM.
HMAC-SHA-256 key
Use to sign and verify webhooks, API requests, or stored messages.
04
Use the bits
Derive, authenticate, encrypt, and decrypt entirely inside this tab with the Web Crypto API.
Key derivation
PBKDF2-HMAC-SHA-256
Use a password and salt to derive a repeatable 256-bit encryption key.
Message authentication
HMAC-SHA-256
Use a shared secret to authenticate a message and detect changes.
Authenticated encryption
AES-256-GCM
Use for confidential text that must also reject tampering.
05
Password hashing
Create an Argon2id verifier for password storage without blocking the page.
This value stays in your browser. Use sample data rather than a real account password.
Memory-hard password hash
Argon2id
Use to store password verifiers for new applications.
Profile: 19 MiB memory, 2 iterations, parallelism 1, 32-byte output, and a fresh 128-bit salt.