When you give a brew command on your Mac and encounter a “command not found brew” error, then it can be due to two reasons: one being the wrong path file selection or directory not listed in the path environment, and the other reason can be ‘Brew’ is not installed on your Mac.


In this article, we have provided the working solutions for the brew command error. Have a look at them below.

How to Fix ‘Command Not Found brew Mac’ Error?

Why Do I Get ‘brew: command not found?”


As mentioned above, one of the common reasons for getting the ‘command not found brew’ on Mac is due to the executable brew directory not being present in the ‘PATH’ environment.

What is the ‘PATH’ Environment Variable?

These are the system variables that can be accessed by both the processes as well as the users operating the OS. Environment variables store the values system-wide, and ‘PATH’ is one such variable under it.

‘PATH’ has the address of directories that are searched for the executable files of a program.

How to Fix ‘Command Not Found brew Mac’ Error?

Method 1: Reinstall Homebrew

When the Homebrew software does not perform as expected, the best way is to uninstall the software and then reinstall it. If you want to uninstall the ‘Homebrew’ software completely, without leaving any cache, then you need to open the terminal on your Mac and then enter the following command:

/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/uninstall.sh)"

This is a command given by the official developers of Homebrew on Github.

  • After you uninstall the Homebrew software completely, restart the system.
  • Now, go to the Homebrew website and then paste the following code for installation:
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"

Since the Homebrew is completely rewritten on the ‘Bash’ platform, instead of ruby, the command line is changed to /bin/bash.


Method 2: Install ARM Version on M1 Device

If you are using a Mac powered by an M1 chip, then your device shows an instruction to add brew to the zsh configuration file with the name .zprofile.

Instead of the path /usr/local/homebrew, you need to install Homebrew in /opt/Homebrew.

Use the following code on your M1 Device to install the ARM version of Homebrew:

666@XXX-MacBook-Pro ~ % /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
==> Next steps:
- Add Homebrew to your PATH in /Users/668/.zprofile:
echo 'eval $(/opt/homebrew/bin/brew shellenv)' >> /Users/668/.zprofile
eval $(/opt/homebrew/bin/brew shellenv)
- Run `brew help` to get started
- Further documentation: https://docs.brew.sh
666@XXX-MacBook-Pro ~ % brew install --cask google-chrome zsh: command not found: brew

Note: It is recommended to check each line carefully and then copy-paste accordingly.

You can also add the brew to .zshrc by following the command given below:

echo 'export PATH="/opt/homebrew/bin:$PATH"' >> $HOME/.zshrc

Method 3: Install XCode on your Mac

Most Mac users have complained that the Homebrew software was not running if the Xcode was not installed on the system. So, you need to have an Xcode on your system; follow the process for the same below:

  • Firstly, run the following command to know if the XCode is already installed on your system or not.
/usr/bin/xcodebuild -version
  • In case if the XCode is already installed on your Mac, you will find the exact version like this:
Xcode 12.3 Build version 12C33
  • Now, open the Xcode and navigate to Preferences → Location. You can find this option under the ‘Command Line Tools.’
How to Fix ‘Command Not Found brew Mac’ Error?
  • Now, run the following command after opening the terminal:
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"

For Mac M1 users, it is recommended to use the following command:

echo "export PATH=/opt/homebrew/bin:$PATH" >> ~/.zshrc


We hope this article has helped you fix the ‘command not found brew’ error on your Mac. In case none of the above-mentioned methods work, then we recommend you raise a complaint on Github on the Homebrew repository.



Please enter your comment!
Please enter your name here