Secure Password & UUID Generator

Generate high-entropy cryptographic passwords alongside RFC 9562 UUID v4 and time-ordered UUID v7 identifiers in bulk.

CSPRNG Security · UUID v4 · v7 · Entropy Meter

Loading tool workspace...

Overview of the Online Password & UUID Generator

Whether you are provisioning production database credentials, rotating API signing secrets, or minting globally unique primary keys across distributed microservices, random number quality is non-negotiable. Standard JavaScript Math.random() relies on a non-cryptographic PRNG (XorShift128+) whose internal state can be reconstructed from observed outputs—making it unsafe for security-sensitive credentials or tokens.

AllUtility’s Password & UUID Generator relies exclusively on the W3C Web Crypto API (crypto.getRandomValues), drawing directly from your operating system’s hardware-seeded Cryptographically Secure Pseudo-Random Number Generator (CSPRNG). Featuring dedicated tabs for High-Entropy Passwords and RFC 9562 UUID v4 / v7, every value is generated 100% client-side in browser memory with zero network transmission.

Cryptographic Design (Rejection Sampling & UUID v7) & Key Features

Mapping random bytes to a character pool with naive modulo arithmetic (byte % poolSize) introduces statistical modulo bias whenever 256 is not evenly divisible by the character set length. Our generator applies strict rejection sampling—discarding bytes at or above 256 - (256 % poolSize) and resampling—so every character has an exact, mathematically uniform probability.

  • Unbiased High-Entropy Passwords (8–128 chars): Combine uppercase, lowercase, digits, and symbols, optionally strip visually ambiguous glyphs (O, 0, l, 1, I), monitor live Shannon entropy in bits, and bulk-generate up to 50 passwords at once.
  • RFC 9562 UUID v4 & Timestamp-Ordered UUID v7: Generate classic 122-bit random UUID v4 values alongside modern UUID v7 identifiers (48-bit Unix millisecond timestamp prefix + 74 random bits) in batches of 1–100.
  • Instant Format Controls: Toggle uppercase hex output or strip hyphens (32-char compact hex) with a single click to match SQL schemas, environment files, or legacy APIs.

Step-by-Step Usage Guide

  1. Select Generator Mode: Switch between the Password tab and the UUID (v4 / v7) tab along the top bar.
  2. Configure Password Policy & Check Entropy: Slide or enter a character length (8–128), toggle character classes and ambiguous-character exclusion, and verify the linear entropy gauge (≥ 80 bits recommended for user accounts; ≥ 100 bits for root/API secrets).
  3. Choose UUID Version & Formatting: In the UUID tab, pick UUID v4 (pure random) or UUID v7 (k-sortable by creation time), set batch count (1–100), and adjust uppercase or hyphenless formatting.
  4. Regenerate or Bulk Copy: Click Generate to draw fresh CSPRNG bytes immediately, then copy individual rows or the entire batch to your clipboard.

UUID v4 vs. UUID v7 Architecture & Entropy Guidelines

Choosing the right UUID version under IETF RFC 9562 has a dramatic impact on relational database write throughput:

UUID v4 (122 random bits — unordered):
f47ac10b-58cc-4372-a567-0e02b2c3d479

UUID v7 (48-bit Unix epoch ms + 74 random bits — time-sortable):
019315a4-7c20-7b3d-9f4a-81c92e40b115
  • Why Databases Love UUID v7: Random UUID v4 primary keys scatter inserts across arbitrary leaves of a PostgreSQL or MySQL InnoDB B-Tree index, causing frequent page splits, buffer-pool churn, and heavy disk I/O. Because UUID v7 embeds a big-endian 48-bit millisecond timestamp in its leading bits, newly minted IDs append monotonically at the end of the index while preserving collision-free distributed generation.
  • Length Beats Complexity ($E = L \times \log_2 N$): Password strength scales linearly in bit-entropy—and exponentially in brute-force cost—with length $L$. A 20-character alphanumeric+symbol password exceeds 128 bits of entropy, rendering offline GPU cracking infeasible.

Frequently Asked Questions

Are generated passwords or UUIDs ever transmitted or logged on a server?

Never. Every byte is produced locally inside your browser process via window.crypto.getRandomValues() with zero API calls, analytics payloads, or server storage. Closing or refreshing the tab wipes the generated values from memory immediately.

Why does this tool avoid Math.random() completely?

Math.random() is designed for simulations and UI animations, not security; its internal state is small and predictable if an attacker observes sequential outputs. crypto.getRandomValues() taps directly into OS-level cryptographic entropy sources (/dev/urandom on Linux/macOS, BCryptGenRandom on Windows), making outputs computationally unpredictable.

When should I choose UUID v7 over UUID v4?

Use UUID v7 for database primary keys, event-stream IDs, audit logs, and distributed order records where chronological sortability and B-Tree index locality matter. Choose UUID v4 for password-reset links, invite tokens, or public object IDs where you deliberately do not want the exact creation timestamp encoded inside the identifier.

Does excluding ambiguous characters (O, 0, l, 1, I) weaken my password?

Only slightly per character, and adding just one or two extra characters to the password length more than compensates for the 5-character reduction in pool size. Excluding lookalike glyphs is highly practical for Wi-Fi keys, emergency recovery codes, or temporary credentials that humans must read and type manually.