Random string gen

How it works

Each position in the string is a draw from the allowed set. Length 8 with uppercase English letters can never emit a digit. Length 8 with letters and digits can. The generator does not know whether you wanted a dummy invoice, a test username, a game code, or a secret. It only knows the set and the length. “Gen” in the search is the short name for that job.

Most page widgets are pseudorandom. That is enough for filler IDs, layout samples, and throwaway codes in a mock. It is the wrong instrument for a cryptographic key unless the page is built for that job. A reconstructable stream is a feature for tests. It is a defect for secrets. Drawing again is a different string. Copy once if you need a fixture.

Repeats inside a string are allowed on independent position draws. A double letter can be honest. If you need each glyph unique inside one string, that is sampling without replacement, and the string cannot be longer than the set. Say which rule you wanted. Do not call a double “m” a bug in a with-replacement draw.

Alphabet first, length second

Choose the set before you choose how long. Letters only. Letters and digits. Hex digits. A wider ASCII set. Ambiguous glyphs cause practical pain: uppercase I, lowercase L, and the digit 1 look alike on paper. If a human must type the result, drop the look-alikes or use a font that distinguishes them. If only a machine will store the result, the look-alikes are fine.

Name the alphabet: which glyphs may appear. Name the length. Every position is drawn; do not pad a chosen word with one random mark and call the whole string generated. Name whether order and case matter. They do.

Draw once. If it is a secret, store it in a manager, not in a chat log. A short string from a tiny set is easy to write down and easy to guess. A long string from a wide set is the opposite. This page will not quote bit counts you did not measure. The qualitative fact is enough: more positions and a larger set make guessing harder. Padding “password” with a random character at the end is still the word password. Let the generator pick every position if you wanted the generator to work.

String: several glyphs in a fixed length. Single character: one glyph; a different tool if that is all you needed. Sentence: words and syntax; not this page. UUID: a formatted identifier with its own layout, not a free string from your alphabet.

Dummy text versus a secret

If you are filling a test database, keep length and alphabet stable enough that the test is about the software. A generator that suddenly emits punctuation in a column that only allowed digits will hide bugs. Label the column as generated so the next person does not moderate it as user content. Dummy invoice numbers can be thrown away. Secrets cannot.

A string of eight identical letters can be an honest draw. Ugly is not the same as biased. Do not paste a generated secret into a screenshot album or an unencrypted note. The generator’s job ended when it showed the glyphs. Storage is a different tool. Refresh the page and you may get a new sequence. That is normal. Save the output if the string matters. A memory of what the page showed is not a fixture.