Feature toggle

Also called: feature flag, feature switch

Last updated:

A feature toggle is the same thing as a feature flag: a switch that changes application behaviour at runtime without deploying new code. "Toggle" and "flag" are interchangeable — there is no technical difference between them.

Flag or toggle?

"Feature toggle" is the older term, popularised by trunk-based-development and continuous-delivery practitioners; "feature flag" spread later through SaaS vendors and is more common today. You will also see "feature switch" and "feature gate". The distinction that actually matters is not the word but the kind of toggle — release toggles (short-lived, for decoupling deploy from release), experiment toggles (A/B tests), ops toggles (kill switches), and permission toggles (tier gating) — a taxonomy that describes lifespan and purpose, not naming.

Does the name change anything in practice?

No. The workflow is identical whichever word your team uses: wrap functionality in a conditional, configure the value remotely, and change behaviour without touching code. The practical advice is to pick one term and stay consistent in your own codebase and documentation so searches and onboarding stay simple.

Want the full picture? Read the concept guide: What are feature flags? →

Try it in your own app

Free Solo plan covers 10 flags and 2 environments. No credit card, no demo call — sign up and ship.