Loading page
About this tool
Generate consistent feature flag names with type prefix, owning team, expiry tag and your team's case convention.
This generator builds a consistent feature flag key from four parts — a type prefix (release, exp, ops or perm), the owning team, what the flag gates, and a planned removal date for temporary flags. It follows Pete Hodgson's feature-toggle taxonomy and the naming guidance published by LaunchDarkly, Unleash and Flagsmith, and lints the result for negative names, vague words and keys over 64 characters, in any of six case conventions.
Open Feature Flag Naming Generator on AltFTool — it loads instantly in your browser.
Provide your input — an image, text, or data.
Let the tool analyze or generate the result.
Review, refine, and reuse the output wherever you need it.
Release and experiment flags get expiry tags; operational kill switches and permission gates stay evergreen.
Warns on negative names like disable-x, vague words like temp or v2, and keys past 64 characters.
One input renders kebab, snake, camel, Pascal, SCREAMING_SNAKE and dot.case keys with per-row copy.
A widely used pattern is type-team-description, optionally ending with a removal date for temporary flags — for example release-payments-guest-checkout-20261001. The exact separators matter less than consistency: every flag in the codebase should encode its category, its owner and what it gates.
Positively — the flag ON should mean the behaviour is enabled. Names like disable-legacy-search force code to check a double negative (if not disabled), which is a well-documented source of inverted-logic bugs when defaults change.
Yes for temporary flags. Release toggles and experiment flags are meant to be deleted once rollout or the test completes, and a date tag such as 20261001 in the key makes stale flags visible in any dashboard sort. Operational kill switches and permission flags are long-lived by design and should not carry one.
Pete Hodgson's taxonomy on martinfowler.com defines release toggles (ship code dark, roll out gradually), experiment toggles (A/B tests), operational toggles (kill switches and circuit breakers) and permission toggles (plan or cohort gates). The first two are short-lived; the last two can live as long as the product does.