Read the destination rules first
A generated password is useful only if the destination accepts and preserves it. Before opening the Password Generator, check the service’s length limit and allowed characters. The tool supports lengths from 8 through 128 characters and batches of 1 through 20 passwords.
The available groups are Uppercase, Lowercase, Numbers, and Symbols. The symbol set is !@#$%^&*()-_=+[]{}:,.?. If a site accepts only some of these symbols, the tool does not provide a custom alphabet field. Use the site’s own password manager workflow or an accepted group combination rather than repeatedly modifying generated passwords by hand.
Select at least one group. Every selected group contributes at least one character, then the remaining positions are drawn from the combined pool and the positions are shuffled. This makes the group settings meaningful without placing the required uppercase letter or number at a predictable fixed position.
Work through a concrete configuration
Set Password length to 20 and How many passwords? to 3. Enable Uppercase, Lowercase, and Numbers, and disable Symbols. Select Generate passwords.
The expected result is three separate lines, each containing 20 characters. Every line contains at least one uppercase letter, one lowercase letter, and one digit. None contains punctuation. The actual text changes each time; a tutorial should not supply a reusable example password for a real account.
If the service allows all four groups, enable Symbols and generate a fresh value. Save the chosen password directly in your trusted password manager, associate it with the correct site, and confirm that login works before discarding any previous recovery information.
Understand the randomness and its boundary
The implementation uses the browser’s crypto.getRandomValues API with rejection sampling when choosing characters. It does not build passwords from timestamps or Math.random. The Web Cryptography specification describes the browser cryptographic random APIs.
Random generation does not protect a password after you reveal it. Avoid sharing the screen, placing the output in issue reports, or leaving secrets in copied notes. Browser extensions and a compromised device are outside the protection this tool can provide.
Generation takes place in your browser without sending the generated password to an ERITHRA processing endpoint. Use a distinct generated secret for each account. For public record identifiers, use UUID Generator instead; a public identifier should not be confused with a credential that grants access.