Secure Password Generator

Each character is selected with the browser's cryptographically secure random-number generator, not Math.random. Rejection sampling avoids favoring some characters when the selected pool size does not divide evenly into 256. The generator first includes at least one character from every enabled set, fills the remaining positions from the combined pool, and shuffles the result with Fisher-Yates. You can create 8- to 128-character passwords in batches of up to 20 without sending the generated values to TmpKit.

For a password created by a reliable random generator, length contributes more security than hard-to-remember substitutions. Twenty random characters from the default pool provide a large search space while remaining compatible with most services. Disable symbols only when a site rejects them, and avoid shortening the result to compensate. The ambiguous-character option removes I, l, O, and 0 for passwords that must be read aloud or typed from paper; it slightly reduces the pool but prevents common transcription mistakes.

The displayed bit estimate is length × log2(pool size), the theoretical uncertainty of independent uniform draws. A 20-character password drawn from a 72-character pool is roughly 123 bits by that simplified model. The forced inclusion of each selected set changes the exact distribution slightly, so the number is a guide rather than a certification. Real account security also depends on rate limiting, password storage, multi-factor authentication, recovery procedures, and whether the password appears anywhere else.

A strong generated password is only useful if it stays unique and recoverable. Save it directly into a reputable password manager rather than a notes app, screenshot, email draft, or reused naming pattern. Clipboard contents can be read by some extensions, synced across devices, or retained by clipboard managers, so clear sensitive history when your platform supports it. This page does not store generated values, which also means TmpKit cannot recover them after you close or refresh the tab.

• Are passwords uploaded? — No. Generation runs in this browser tab and no API request contains the result.
• Is 12 characters enough? — It may satisfy a policy, but 16–20 random characters provide more margin; use the longest value the service accepts.
• Should every account get a different password? — Yes. Reuse turns one service breach into access to several accounts.
• Does excluding ambiguous characters make a password weak? — It reduces the pool slightly, but sufficient random length still provides a very large search space.