How to Reload .zshrc and Fix Changes Not Taking Effect

You edited .zshrc — added a directory to your PATH, defined an alias, exported a variable — but nothing changed in your terminal. This is one of the most common stumbling blocks when customizing Zsh, the default shell on macOS.

This article covers the quick fix (reloading .zshrc) and what to check when your changes still do not take effect.

1. The Quick Fix: Reload .zshrc

Zsh reads .zshrc when a new interactive shell starts. Terminals that are already open do not pick up your edits automatically. To apply the changes to the current session, run:

source ~/.zshrc

Alternatively, you can restart the shell itself. This gives you a clean state, which is useful when you have removed settings rather than added them (re-sourcing cannot "unload" an old PATH entry or alias):

exec zsh

Opening a new terminal tab or window also loads the updated .zshrc.

2. Still Not Working? Common Causes

2.1. A typo in the export line

The most frequent cause is a small mistake in the PATH line itself. Directories in PATH must be separated by colons (:). If the colon is missing, the new directory gets glued onto the previous one and is silently ignored.

export PATH="$PATH:/usr/local/bin"  # correct
export PATH="$PATH/usr/local/bin"   # wrong: missing colon

To see what your PATH actually contains right now, run:

echo $PATH

2.2. The file you edited is not the one being read

Zsh reads several startup files, and .zshrc is only one of them. On macOS, files such as /etc/zprofile and /etc/profile are processed as well, and ~/.zprofile or ~/.zshenv may also set environment variables. If one of these files sets PATH after your .zshrc runs, your value can be overridden.

cat /etc/zprofile
cat /etc/profile

2.3. macOS path_helper and load order

On macOS, /etc/zprofile runs a utility called path_helper, which builds PATH from /etc/paths and the files in /etc/paths.d/. Because of the order in which these files load, system-defined directories can end up ahead of the ones you added. If the same command exists in two places, the one earlier in PATH wins.

Prepending your directory instead of appending it puts it ahead of the system defaults:

export PATH="$HOME/bin:/usr/local/bin:$PATH"

3. A Sample .zshrc

Here is a minimal example you can adapt to your environment:

# ~/.zshrc

# Base PATH
export PATH="$HOME/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin"

# Homebrew (Apple Silicon)
export PATH="/opt/homebrew/bin:$PATH"

# Global npm packages
export PATH="$HOME/.npm-global/bin:$PATH"

After saving, apply the changes with source ~/.zshrc and verify with echo $PATH.

Summary

Edits to .zshrc do not apply to terminals that are already open. Run source ~/.zshrc, or use exec zsh for a clean restart.
If changes still do not take effect, check the export line for missing colons or typos.
Remember that other startup files (/etc/zprofile, ~/.zprofile, ~/.zshenv) and macOS's path_helper can override or reorder your PATH. Prepend your directories if they need priority.