Password Generator
Cryptographically secure passwords using crypto.getRandomValues — never sent to a server.
Runs 100% client-sideOn this page4 sections
HOW TO USE
- 01Adjust Length and pick the character classes you want included.
- 02Toggle Exclude 0Ol1I for passwords that need to be read off a screen.
- 03Click Generate. Each password gets a strength bar based on length and alphabet entropy.
WHEN TO USE
Use this to generate strong, random credentials for test user accounts, seed data, and local environment configs. Never use real user passwords as test data — generated passwords isolate test data from production credentials and meet complexity policies without manual crafting. Use the strength bar to confirm the generated password meets your application's requirements before seeding it into a test database or fixture file.
WHAT BUGS THIS FINDS
Password complexity validation gaps
Generate passwords with only one character class at a time to test whether the application correctly enforces minimum complexity requirements for each class independently.
Off-by-one on minimum length
Generate passwords at length−1, length, and length+1 relative to the application's minimum to confirm the boundary check uses the correct inequality direction.
Ambiguous character handling
Toggle 'Exclude 0Ol1I' on and off to generate passwords with and without visually ambiguous characters, then test whether the application renders them unambiguously in a password-reveal field.
Special character rejection
Some applications silently strip or reject specific symbols — generate a password rich in special characters and test the full login round-trip to confirm all characters survive storage and retrieval.
QA USE CASES
Test user credential seeding
Generate a strong password for each test persona, store the hash in the DB fixture, and use the plaintext in test login steps — avoids hardcoded weak passwords in the test suite.
Password policy boundary testing
Generate passwords at exact boundary lengths and with each character class combination to cover the equivalence partitions of the application's complexity rules.
Local environment secrets
Generate random database passwords and API secret values for .env.local files — keeps local credentials unique and avoids accidentally committing real credentials.