What case should feature flag names use?

Use whatever your platform and codebase share. snake_case (enable_new_checkout) and kebab-case (enable-new-checkout) are both common. Consistency across the team matters far more than which one you pick.

Should I put the environment in the flag name?

Usually no. Most flag platforms scope flags per environment, so a suffix like _prod is redundant. Add an environment suffix only if your tool stores all environments under one flat namespace.

What do the prefixes mean?

Prefixes signal a flag's intent and lifecycle. enable_ marks a release toggle, experiment_ marks an A/B test, kill_ marks a kill switch, and ops_ marks an operational toggle. They help you spot stale flags during cleanup.

Why does consistent naming matter?

Feature flags accumulate fast and become technical debt. A predictable naming scheme makes flags searchable, signals their purpose at a glance, and makes it obvious which ones are safe to remove after a launch.

Is anything sent to a server?

No. The word pools are bundled with the page and every name is assembled in your browser. Nothing about your choices is uploaded or stored.

Feature Flag Name Generator

Feature flags multiply quickly, and a tangle of inconsistent names turns into untouchable technical debt. This tool generates flag names in a consistent convention, with optional type prefixes and environment suffixes, so your toggles stay searchable and their purpose is obvious at a glance.

How it works

A name is assembled from up to four parts: an optional type prefix (enable, experiment, kill, ops), a feature word (checkout, dashboard, onboarding), an aspect word (redesign, flow, v2), and an optional environment suffix (prod, staging, dev). The parts are joined with the separator for your chosen case: an underscore for snake_case or a hyphen for kebab-case. Each generated batch is de-duplicated so you can scan a list of distinct candidates at once.

Tips and example

Sample output with the experiment prefix in snake_case:

experiment_pricing_table_v2
experiment_search_ranking_flow
experiment_signup_form_redesign

Prefer descriptive names over cryptic ones. enable_new_checkout beats flag_42 every time you grep the codebase six months later.
Use the type prefix to track lifecycle. When a launch is done, every experiment_ and kill_ flag is a candidate for removal.
Avoid baking the environment into the name unless your platform forces a single flat namespace. Most tools scope flags per environment already.