Feature Flag Name Generator
Generates clear, conventional feature flag names for safe rollouts
About this generator
A feature flag named `flag1` or `new_thing` tells nobody what it controls, making it impossible to audit which flags are safe to remove after a rollout. This tool returns a shuffled set of feature flag names that follow a readable convention — a clear verb prefix plus a specific subject. The only input is how many you want, from 1 to 10 (14 in the pool). The set demonstrates five verb prefixes: `enable_` for activating a feature, `use_` for switching implementations, `show_` for UI toggles, `gate_` for premium access, and `kill_switch_` for emergency-off flags. Each name is a specific, real-sounding toggle like `enable_new_checkout` or `kill_switch_legacy_api`. Pick names that match your toggles, use the prefix that signals intent, and plan to remove each flag once its rollout is complete.
How to use
- Choose how many flag names you want.
- Generate a set matching your toggles.
- Keep the verb prefixes consistent.
- Record each flag's purpose and plan to remove it.
Use Cases
- •Naming flags for a gradual rollout
- •Setting up an A/B test toggle
- •Adding a kill switch for risky code
- •Gating a premium or beta feature
- •Keeping a flag list self-documenting
Tips
- →Start each name with a clear verb prefix.
- →Be specific about what the flag controls.
- →Use kill_switch_ for emergency-off flags.
- →Plan to remove a flag once its rollout is done.
FAQ
what makes a good feature flag name
A verb prefix that signals behaviour — `enable_`, `use_`, `show_`, `gate_`, or `kill_switch_` — followed by a specific subject naming what it controls. The combination tells the next reader exactly what the flag does without a comment.
why group flags by verb prefix
Prefixes make a long flag list scannable and naturally group flags by what they do. When auditing for stale flags, you can quickly identify `enable_` flags stuck `true` or `kill_switch_` flags that were never removed.
how do I keep a flag list from growing indefinitely
Assign each flag an owner and a planned removal date when you create it. Use a descriptive name so it is obvious when the rollout is done and the flag is safe to delete. The generator avoids generic names so each flag stays tied to a specific, temporary decision.
You might also like
Popular tools from other categories that share themes with this one.