Which convention should my project actually use?

It depends where the value lives: environment variables are always flat strings, so a nested setting there is typically written APP_DATABASE_TIMEOUT rather than app.database.timeout. A config file that supports real nesting (YAML, JSON, TOML) can use the dotted form directly. Most projects pick one convention and map between them at the boundary rather than mixing both freely.

Configuration Key Generator

Generates a realistic namespaced configuration key — like service.cache.ttl_seconds — for testing config-loading code or documenting a settings schema.

How many

Don't repeat what I've already seen

Your result will appear here.

What this generator does

Produces a realistic configuration key in dotted or underscored form, for testing config loaders. The two forms are not interchangeable: dotted keys nest, underscored keys are what survives the environment, and most loaders map between them by a rule you have to know.

What it builds, and how many ways

Each result is assembled to this shape: [namespace] + [section] + [setting] — one of 2 sentence patterns this generator uses.

section: 7 options
setting: 7 options
namespace: 6 options

Taken together those banks can be assembled 588 different ways, repeating after about 30.

Some results it can produce:

app.database.enabled
auth_cache_endpoint
client.logging.max_connections
api_queue_level

A fixed sample so this page stays the same between visits. Your own results are assembled at random, each slot filled independently and each press independent of the last, so the same result can come up twice — past the repeat figure above, seeing one twice is more likely than not.

How to use this tool

Press generate for a key.
Generate again for another one.

Common use cases

Testing config-loading code
Documenting a settings schema
Placeholder data for a settings UI

Limitations and good to know

Two conventions are shown (dotted and underscored) but there's no way to request one specifically — you take whichever form the random draw lands on.
Namespace, section and setting each come from a small fixed vocabulary, so the key doesn't reflect any real project's actual settings schema.
Choosing which convention to use in a real project is a team decision this tool can't make for you — it only shows both shapes exist.

Practical tips

Test your loader with a key whose segment contains an underscore of its own. That is where dotted-to-environment mapping usually breaks, and it breaks silently.

Each part of the result is chosen independently with your browser's cryptographic random number generator, so every option in a bank is equally likely. How Generate Random works.

Frequently asked questions

Which convention should my project actually use?: It depends where the value lives: environment variables are always flat strings, so a nested setting there is typically written APP_DATABASE_TIMEOUT rather than app.database.timeout. A config file that supports real nesting (YAML, JSON, TOML) can use the dotted form directly. Most projects pick one convention and map between them at the boundary rather than mixing both freely.