30-Character Password Generator

Either because a system caps passwords at 30 — Oracle Database and older Sybase servers are common examples — and you want every character the limit allows, or because the secret guards infrastructure and will live for years. At about 194 bits, a random 30-character password is beyond brute force under any assumption.

At about 194 bits, an offline attacker testing 10 billion guesses per second would need around 4 × 10⁴⁰ years on average. The number is meaningless in practice: attacks on secrets this long go after storage, transport, or people — never the password itself.

Oracle Database has long capped user passwords at 30 bytes, older Sybase Adaptive Server releases documented a 30-character maximum, and some enterprise login forms stop accepting input at 30. If a system documents a 30-character limit, generate exactly 30 here rather than something longer that may be cut short.

Not for security: both are far beyond brute force (about 194 versus 207 bits). It matters for compatibility. A 32-character password on a system that stops at 30 is either rejected or silently truncated, which can lock you out — so match the system’s limit exactly.

Where the system accepts them, yes — they lift it from about 179 to 194 bits. For database passwords embedded in connection strings or environment files, the letters-and-numbers option avoids escaping problems, and 179 bits is still far beyond any attack.

Yes. Nobody types 30 random characters reliably, and transcription errors at login are likely. Generate it here, store it in a password manager or secrets vault, and paste it from there whenever you need it.