What Is a Feature Flag?

A feature flag (also called a feature toggle) is a mechanism that lets teams turn a feature on or off in production without deploying new code. Feature flags give product and engineering teams control over who sees what, when, without waiting for a full release cycle.

Why feature flags matter

Shipping software is risky. Even well-tested features can behave unexpectedly in production. Feature flags reduce that risk by letting teams gradually roll out changes to a small percentage of users, monitor the results, and expand or roll back instantly if something goes wrong.

Beyond risk reduction, feature flags enable product teams to run experiments, manage beta programs, and coordinate launches across time zones. They separate the act of deploying code from the decision of releasing a feature to users.

How feature flags work

At a basic level, a feature flag is a conditional check in your code: if the flag is on for this user, show the new feature; if not, show the existing experience. The flag value can be controlled through a dashboard, targeting rules (such as user segment, geography, or account plan), or percentage-based rollouts.

Teams typically start with a small rollout (say 5% of users), monitor key metrics like error rates and engagement, then gradually increase the percentage until the feature reaches everyone. If problems appear at any stage, the flag can be turned off in seconds.

Related terms

• Technical Debt

  Stale feature flags that are never removed become a form of technical debt.

• Agile Product Management

  Feature flags support agile practices by enabling frequent, low-risk releases.

• Continuous Discovery

  Flags let teams test hypotheses in production as part of an ongoing discovery practice.