Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Flutter and app store releases

Flutter web cannot find Chrome and asks for CHROME_EXECUTABLE

ErrorCannot find Chrome. Try setting CHROME_EXECUTABLE to a Chrome executable.

Short answer

Flutter looks for Chrome in one fixed place per operating system, unless CHROME_EXECUTABLE is set. Install Chrome in the default place, or point CHROME_EXECUTABLE at the real binary. If the variable is set but wrong, Flutter reports that the path is not executable. Edge, or flutter run -d web-server, also work.

  • Applies to Flutter 3.3x stable (web), Chrome current, macOS 26, Ubuntu 24.04, Windows 11
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 1Find out which cause you have

    Run flutter doctor and read the Chrome line. Then list the devices; a working setup shows Chrome (web) or Edge (web).

    flutter doctor -v
    flutter devices
  2. 2Match what you see, then jump to its fix

    1. 1Cannot find Chrome in flutter doctor, and no Chrome (web) in flutter devicesChrome is not installedFix
    2. 2Cannot find Chrome ... Try setting CHROME_EXECUTABLE although Chrome or Chromium runs fineChrome is installed somewhere Flutter does not lookFix
    3. 3is not executable. or Cannot find Chrome executable at <path>CHROME_EXECUTABLE is set, but the path is wrongFix
    4. 4Remote or headless machine, or a Firefox or Safari userYou use another browser or a machine with no ChromeFix

What does the error look like?

  • Cannot find Chrome. Try setting CHROME_EXECUTABLE to a Chrome executable.
  • Cannot find Chrome executable at
  • is not executable.

Cause 1 of 4

Chrome is not installed

1Check

Flutter's web tooling needs Google Chrome or Microsoft Edge. Check that one of them is installed for this user.

# macOS
ls "/Applications/Google Chrome.app"
# Linux
command -v google-chrome

2Fix

Install Google Chrome or Microsoft Edge, then run flutter devices again.

flutter devices

3Verify

The device list shows Chrome (web) or Edge (web).

flutter devices

Confirmed by docs.flutter.dev

Did this fix it?

Cause 2 of 4

Chrome is installed somewhere Flutter does not look

1Check

On Linux, Flutter looks for a command named google-chrome, so a Chromium package or a Flatpak install is not found. On macOS it expects /Applications/Google Chrome.app/Contents/MacOS/Google Chrome. On Windows it checks the Google\Chrome\Application\chrome.exe path under LOCALAPPDATA, PROGRAMFILES and PROGRAMFILES(X86).

command -v google-chrome chromium chromium-browser

2Fix

Set CHROME_EXECUTABLE to the full path of the browser binary. It takes priority over the defaults.

# Linux or macOS shell (add to ~/.zshrc or ~/.bashrc to keep it)
export CHROME_EXECUTABLE=/usr/bin/chromium

# Windows PowerShell for the current user
setx CHROME_EXECUTABLE "C:\Path\To\chrome.exe"

3Verify

Open a new terminal so the variable is loaded, then run doctor again.

flutter doctor -v

Confirmed by raw.githubusercontent.com

Did this fix it?

Cause 3 of 4

CHROME_EXECUTABLE is set, but the path is wrong

1Check

Flutter returns the variable's value without checking that the file exists, so a typo only shows up later, when it tries to start it. Print the value and test it.

echo "$CHROME_EXECUTABLE"
ls -l "$CHROME_EXECUTABLE"

2Fix

Point the variable at the browser binary itself, not at a folder or an .app bundle, and make sure the file is executable. Remove the variable to go back to the defaults.

# macOS binary inside the app bundle
export CHROME_EXECUTABLE="/Applications/Google Chrome.app/Contents/MacOS/Google Chrome"
# or drop it
unset CHROME_EXECUTABLE

3Verify

Doctor reports Chrome as found.

flutter doctor -v

Confirmed by raw.githubusercontent.com

Did this fix it?

Cause 4 of 4

You use another browser or a machine with no Chrome

1Check

The Chrome device is only needed for flutter run -d chrome. Other browsers can use the web-server device.

flutter devices

2Fix

Run the web-server device and open the printed address in the browser you prefer. Debugging support in this mode is limited.

flutter run -d web-server

3Verify

The terminal prints a local URL; the app loads when you open it.

flutter run -d web-server

Confirmed by docs.flutter.dev

Did this fix it?

How do I stop it coming back?

  • Install Chrome in its default location, or keep CHROME_EXECUTABLE in your shell profile so every terminal gets it.
  • Run flutter doctor -v after changing browsers or reinstalling the OS.
  • In CI, install Chrome in the image and set CHROME_EXECUTABLE explicitly.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.

Which stack is behind this page?

Projects of mine built on the same technologies:

Related fixes

Mobile apps

A phone is plugged in over USB but Android Studio and adb do not list it

adb devices prints List of devices attached with nothing below it

adb lists a phone only when four things hold: USB debugging is on, you accepted the computer's RSA key on the phone, the computer has a driver or udev rule for the device, and the cable carries data to a running adb server.

6 causes, each with a fix

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.