where can i find all available values of --enable-features parameter for chrome browser?

Gemini 3.1 Pro

Answer: The most complete and accurate place to find all available values for the --enable-features parameter is by searching the Chromium source code for BASE_FEATURE declarations via Chromium Code Search.

The `--enable-features` parameter behaves differently from standard command-line switches. Instead of typical arguments, it accepts internal Chromium feature names (defined in the C++ codebase as `base::Feature` objects). Because hundreds of these features are continuously added, removed, or merged into default behavior with every browser update, Google does not maintain a static, official text list of them. The ultimate source of truth is the Chromium Code Search tool (source.chromium.org). By searching for the macro `BASE_FEATURE(`, you can discover the exact string names of every feature currently compiled into the browser. This ensures you are looking at the exact parameters supported by the current codebase. For a more accessible but slightly less exhaustive approach, you can type `chrome://flags` into your Chrome address bar. This internal page exposes the most prominent user-facing experimental features for your specific build. While it doesn't show every underlying backend feature, it provides the internal feature names used for the `--enable-features` flag when you look at the source or the warning prompts.

Claude Opus 4.7

Answer: There is no single official, exhaustive public list, but the authoritative source is the Chromium source code itself — specifically the `base::Feature` declarations — with `chrome://flags` and a few community-maintained references serving as practical alternatives.

Chrome's `--enable-features` flag accepts the names of `base::Feature` entries that are defined throughout the Chromium codebase. Because features are declared in hundreds of different `.cc` and `.h` files (each component registers its own), Google does not publish a consolidated list. The closest things to a complete reference are: 1. **The Chromium source code (the ground truth).** Search https://source.chromium.org/ (Code Search) for `BASE_FEATURE(` or `const base::Feature` — every match is a valid feature name you can pass to `--enable-features=`. Example query: `BASE_FEATURE\(k` with regex enabled. This is the only truly exhaustive source. 2. **`chrome://flags`** — Open this page in Chrome. Many (but not all) features are surfaced here with human-readable descriptions. The internal name shown in the URL/anchor (e.g., `#enable-parallel-downloading`) often corresponds to a feature name. Note that `chrome://flags` is a curated subset; many features exist only in code. 3. **`chrome://version` and `about:version`** show currently active features, and `chrome://histograms` plus `chrome://tracing` can reveal feature usage at runtime. 4. **Community references:** - https://peter.sh/experiments/chromium-command-line-switches/ — comprehensive list of command-line *switches* (not features, but useful context). - The Chromium `testing/variations/fieldtrial_testing_config.json` file lists features used in field trials. - GitHub mirrors of Chromium let you grep for `BASE_FEATURE` quickly. Practical tip: feature names are case-sensitive and use the C++ identifier without the leading `k` (e.g., `kParallelDownloading` in code becomes `--enable-features=ParallelDownloading`). Features can also take parameters via the syntax `--enable-features=FeatureName:param1/value1/param2/value2`. Because features are added, renamed, and removed every Chrome release, any static list goes out of date quickly — which is why searching the source for your specific Chrome version's branch is the most reliable approach.

Final Summary

The AI Roundtable concluded that because Chrome features are added and removed constantly, Google does not maintain a static, official list. Gemini 3.1 Pro and Claude Opus 4.7 both identified the Chromium Code Search tool as the only 'source of truth,' where users must search the C++ codebase for specific feature macros. While both models suggested chrome://flags as a user-friendly alternative, they warned it only shows a curated subset of what the --enable-features flag can actually trigger.

Both 2 models agreed