Skip to main content
Control browser launch behavior for debugging, automation, and runtime experiments.
Looking for chrome://flags or edge://flags? Type it into your address bar, which is the browser’s built-in page. Firefox has no firefox://flags; use about:config instead.If you’re toggling flags to test or build a browser extension, Extension.js applies them per-project automatically across Chrome, Edge, and Firefox, so you don’t pass flags by hand on every run. Create your first extension in 30 seconds →
Extension.js is a framework that builds and runs browser extensions from one manifest.json for Chrome, Edge, Firefox, and Safari. To create an extension, run these commands in a terminal:
This page is part of the Extension.js documentation. npx extension@latest dev launches the browser with the flags on this page applied. Tune browser launch behavior without changing extension source code. Extension.js merges browser flags from your extension.config.* and applies them in dev, preview, and start flows.

Does Firefox have firefox://flags?

Firefox does not use firefox://flags the way Chromium browsers use chrome://flags or edge://flags. Firefox exposes runtime toggles through about:config (preferences) and accepts launch flags from the command line. If you searched for firefox://flags, firefox //flags, browser://flags, mozilla://flags, or about flags firefox, you are probably trying to change browser behavior during extension development. In Extension.js, do that in two places:
  • Use browserFlags for launch-time flags Extension.js passes to the browser binary.
  • Use Firefox preferences for repeatable Gecko runtime behavior that would otherwise live in about:config.
Both work for Chrome, Edge, and Firefox extension development from the same Extension.js project.

Flags in other browsers

Extension.js launches and configures any Chromium-based browser the same way.
  • brave://flags, opera://flags, vivaldi://flags, yandex://flags: all Chromium-based, so they behave identically to chrome://flags, and Extension.js manages them per-project.
  • internet://flags and browser://flags: these are not real browser schemes. You are most likely looking for chrome://flags (Chromium) or about:config (Firefox).
  • edge://flags: Edge is Chromium, so it works exactly like Chrome in Extension.js.
Building an extension that needs specific flags at launch? Set them once in extension.config.* and Extension.js applies them every run. See browserFlags below.

GPU and WebGL flags

A headless session, a container, or a virtual machine often has no GPU. WebGL contexts then fail to create, and canvas code that needs one throws. Pass the Chromium switches through browserFlags:
--ignore-gpu-blocklist lets Chromium use a GPU that its blocklist would refuse. --use-gl=angle with --use-angle=swiftshader renders WebGL in software, which is the right choice in continuous integration. --enable-unsafe-webgpu turns on WebGPU where the browser still gates it. Firefox has no equivalent switches. Set webgl.force-enabled through browser preferences instead.

Template examples

new-browser-flags

new-browser-flags template screenshot See browser flags in action with a new-tab extension that configures launch behavior.
Repository: extension-js/templates/newtab-browser-flags

How it works

Configure flags in extension.config.*:
  • browser.<target>.browserFlags
  • commands.dev|start|preview.browserFlags
  • Optional excludeBrowserFlags to remove defaults or user flags (behavior depends on whether you target Chromium or Firefox).
Override order: browser defaults → command defaults → CLI-selected command context.

Flag capabilities

Example configuration

Chromium vs Firefox behavior

  • Chromium family (chrome, edge, chromium, chromium-based)
    • Starts from an internal default flag set, then appends your browserFlags.
    • excludeBrowserFlags removes matching default and user flags.
    • Extension.js manages --load-extension=... and filters it out from user-provided flags.
  • Firefox/Gecko family (firefox, gecko-based / firefox-based)
    • Uses user-provided browserFlags (no large default flag bundle like Chromium).
    • excludeBrowserFlags removes matching user flags, with the same rule as Chromium.
Both families share one exclusion rule: a flag is removed when it equals the exclude value, or when the exclude value names a switch whose value continues with = or ,. So --disable-features also removes --disable-features=Translate, while --dev never removes --devtools.

Default Chromium flags

Extension.js applies these flags automatically when launching Chromium-family browsers. Use excludeBrowserFlags to remove any you do not need.

The debugger permission changes two flags

An extension that attaches chrome.debugger must handle the Cancel button on Chrome’s debugging bar. From the release after 4.1.39, a session shows that bar when your manifest lists debugger under permissions or optional_permissions:
  • --silent-debugger-extension-api is left out, because that flag hides the bar.
  • --disable-infobars is passed, because it clears the notice that holds the bar back.
Chrome for Testing shows its own testing notice in the same slot, and the debugging bar waits behind it. --disable-infobars hides every infobar that has no button, so the bar can show. Other Chromium builds honor that flag only in headless mode. To hide the bar again, list --silent-debugger-extension-api under browserFlags. To keep the testing notice, list --disable-infobars under excludeBrowserFlags. The identity card prints a Dev flag line for each verdict:
ready.json carries the reason for each verdict under devAdditions.

Always-on session flags

Beyond the default table, every Chromium launch gets a fixed block of session-stability flags. They keep background timers, occluded windows, and renderer throttling from distorting automated and AI-driven sessions. excludeBrowserFlags cannot remove them:
In dev mode only, Extension.js also wires the debugging channel with three flags: --remote-debugging-port=<derived port>, --remote-debugging-address=127.0.0.1, and --remote-debugging-pipe. Production-mode launches (start, preview) skip this trio.

Feature-switch merging

Chromium honors only the last occurrence of a repeated switch. Extension.js therefore merges every --enable-features and --disable-features occurrence into one comma-joined switch each. Defaults, config, and environment values all merge, and duplicate feature names are removed. You can safely pass --disable-features=Foo in browserFlags without erasing the defaults.

Environment switches

  • EXTENSION_BROWSER_FLAGS appends whitespace-separated flags to every launch. It is applied after config flags and after excludeBrowserFlags filtering, so excludeBrowserFlags cannot remove flags that come from this variable.
  • EXTENSION_HEADLESS=1 (or true) forces --headless=new, unless a --headless flavor was already passed through config or environment flags. Use it as a focus-steal guard for automated sessions.
In Docker, continuous integration (CI), or containerized environments, Extension.js also applies --no-sandbox and --disable-setuid-sandbox automatically. On Linux it detects a container through any of these signals: CI=true, a /.dockerenv file, a /run/.containerenv file, REMOTE_CONTAINERS=true, CODESPACES=true, or a set container variable.

Supported targets and references

Use binary flags when needed for engine-based targets:
  • --chromium-binary=...
  • --gecko-binary=...

Best practices

  • Add only necessary flags: Minimize long flag lists to reduce flaky or non-portable setups.
  • Prefer excludeBrowserFlags over replacing defaults: Remove only what conflicts with your workflow.
  • Do not pass --load-extension manually: Extension.js manages extension loading flags internally.
  • Validate per browser family: A flag working in Chromium may be invalid or ignored in Firefox.

Next steps