How to Fix "zsh: command not found: brew" on macOS (Intel & Apple Silicon)

Running into zsh: command not found: brew basically means your terminal has no idea where Homebrew is hiding. You’ll usually see this right after installing it for the first time or right after updating macOS. Getting it working again is just a matter of pointing your shell to the right folder, depending on the chip inside your Mac.

Target OS: macOS

Apple Silicon Path: /opt/homebrew/bin/brew

Intel Path: /usr/local/bin/brew

Instant Diagnostic Command: /opt/homebrew/bin/brew --version

The 30-Second Diagnostic: Why is Homebrew Missing?

Run that diagnostic command above to see what state your setup is actually in:

• You see a version number → Homebrew is on your drive, but your shell can't find it. Jump straight down to Fix 1.
• You get no file or directory → Homebrew isn't installed at all. Run the install script below, then head to Fix 1.
• The direct command works, but plain brew still breaks after setting PATH → Check out Fix 2 (Rosetta) or Fix 3 (macOS update).

If your Mac says no file or directory, you just need to get the files installed from scratch. Pop open your terminal and run the standard install script:

Bash

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

Once it wraps up, don’t close the window yet - check the output. The installer always prints a little section called Next steps with the exact lines you need to run to fix your PATH. Make sure you copy and paste those right away. Almost everyone skips past that text, which is why the command fails even after a clean install.

Fix 1: Add Homebrew to Your PATH (The Right Way)

You'll see a lot of guides telling you to stitch PATH variables together by hand, but that's really easy to mess up with a typo. Homebrew has a built-in helper called brew shellenv that handles all the heavy lifting cleanly behind the scenes.

For Apple Silicon Macs (M1/M2/M3/M4)

On Apple Silicon, Homebrew keeps all its files tucked inside /opt/homebrew. Just fire up your terminal and paste these two lines in:

Bash

echo 'eval "$(/opt/homebrew/bin/brew shellenv)"' >> ~/.zprofile
eval "$(/opt/homebrew/bin/brew shellenv)"

For Intel Macs

If you’re on an older Intel Mac, it uses the classic Unix folder layout instead. Your install lives over in /usr/local/bin.

Bash

echo 'eval "$(/usr/local/bin/brew shellenv)"' >> ~/.zprofile
eval "$(/usr/local/bin/brew shellenv)"

Why .zprofile is Better Than .zshrc

Your .zprofile only runs once when you first open your terminal session, while .zshrc reloads every single time you open a new tab or split a pane.

Putting your environment setup in .zprofile keeps your terminal snappy when opening new windows. It saves you from running duplicate scripts that quietly slow things down over time, which is why the Homebrew team recommends sticking it there anyway.

Once you’ve pasted the commands for your chip, double-check that it took:

Bash

brew --version

If it prints out a version number, you're good to go.

Fix 2: Resolve the Rosetta 2 Terminal Conflict

If you're on Apple Silicon, there's another sneaky thing that trips people up: running Terminal through Rosetta. Doing that forces your shell into an emulated x86_64 environment.

When that happens, your shell completely ignores the modern /opt/homebrew folder where your tools actually live. You can check this right now by typing uname -m in your prompt. If it prints out x86_64 instead of arm64, you’re running inside Rosetta without realizing it.

To fix it, open Finder, head to Applications, and open Utilities. Right-click on Terminal, choose Get Info, and make sure Open using Rosetta is turned off. Quit Terminal completely, open it back up, and you should be set.

Fix 3: Restore Homebrew After a macOS Major Update

Whenever Apple pushes a big macOS upgrade, it has a bad habit of wiping out or disconnecting the Command Line Tools. Since Homebrew relies heavily on those Xcode tools under the hood, it breaks instantly.

If brew suddenly stopped working right after updating your OS, run this command in your terminal:

Bash

xcode-select --install

A prompt will pop up asking to install the developer tools - just click through, let the download finish, and restart your terminal. If brew is still acting up after that, go ahead and rerun the official Homebrew installer command. It won’t erase your installed tools; it just repairs broken symlinks and cleans up missing pieces.

Fix 4: NVM and PATH Shadowing Conflicts

Tools like Node Version Manager (NVM) can be pretty aggressive about how they rewrite your PATH. If your shell loads NVM after Homebrew, it can end up masking your brew binary altogether. You run into the exact same headache with Conda environments, which love sticking their own folders right at the front of your PATH.

Take a look inside your ~/.zprofile or ~/.zshrc file to see how things are arranged. You want the Homebrew eval line sitting right near the top, well ahead of any NVM or Conda blocks. Rearrange them so it looks like this:

Bash

# Homebrew first
eval "$(/opt/homebrew/bin/brew shellenv)"

# NVM after
export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"

Save the file, then refresh your current terminal window so the changes take effect:

Bash

source ~/.zprofile

Give it a quick test with brew --version to make sure it answers.

Still Failing? Run brew doctor

Homebrew actually comes with its own built-in health check called brew doctor. Even if your PATH is sorted out, weird folder permissions or broken symlinks can still get in the way.

Bash

brew doctor

It will scan your setup and give you plain-English instructions for anything it finds out of place. Just work through whatever warnings pop up before you start installing packages again - most weird post-update glitches get flagged right here.

Once you have Homebrew behaving, run brew list to see what else might need a refresh. Packages like Node.js or tools installed via pip often need a quick recheck after fixing your system environment.