Feature flags in PostHog Web

The PostHog web app is home base for feature flags. It's where you create a flag, decide who gets it, watch the rollout, and turn it off when you need to – all without a deploy.

Open Feature flags in PostHog to see every flag in the project with its status, type, and last-modified date. Open a flag to edit its release conditions, inspect which users match, test how it evaluates, and see the activity log of who changed what.

Before you start

1. Set up Feature Flags – install a PostHog SDK so your app can evaluate flags.
2. Open the web app – no install needed, just sign in to PostHog.

What you can do here

• Create feature flags – set up boolean, multivariate, or remote config flags and define their release conditions.
• Add flag code to your app – the snippet that reads the flag on the other side, for each SDK.
• Test your flag – check how a flag evaluates for a specific user before you widen the rollout.
• Schedule flag changes – queue an enable, disable, or condition change for a future date, including on a recurring schedule.
• Manage early access features – let users opt themselves in and out of a flagged feature.
• Clean up stale flags – find flags nothing has evaluated recently and retire them along with the dead code.
• Manage flags with PostHog AI – describe the flag you want and PostHog AI creates or updates it, or ask it which flags have gone stale. It's an interaction mode inside the web app, not a separate surface. See Manage flags with PostHog AI.

Before you widen a rollout, the flag detail view also shows the blast radius for a release condition – roughly how many users it would affect relative to your total – so a "10% of enterprise accounts" change isn't a guess.

Related

• Manage the same flags from your editor over MCP.
• Evaluate and manage flags programmatically with the API.
• Understand how a value gets decided in server-side local evaluation.