Master macOS Global Environment Variables: Bash & Zsh Made Simple

Overview

macOS supports both the traditional /etc/profile file (read by login shells) and a modular PATH management system based on /etc/paths, /etc/paths.d and the path_helper utility. The same mechanism works for Bash and Zsh.

Setting non‑PATH global variables

Login shells (Bash or Zsh) read /etc/profile first. Adding export statements to this file defines variables for all users.

Example: Define JAVA_HOME

Open /etc/profile with root privileges: sudo nano /etc/profile Add the following lines at the end of the file:

# Global JAVA_HOME
export JAVA_HOME=$(/usr/libexec/java_home)
export CLASS_PATH="$JAVA_HOME/lib"

Save, exit, and open a new terminal. Verify:

echo $JAVA_HOME

Managing PATH with /etc/paths.d and path_helper

The utility path_helper is invoked by /etc/profile (or /etc/zprofile for Zsh). It reads /etc/paths and every file in /etc/paths.d, concatenates the entries, and exports the resulting PATH.

Modular – each application can drop a plain‑text file containing one directory per line.

Upgrade‑safe – system updates may replace /etc/paths but never delete files in /etc/paths.d.

Simple syntax – no export statements are required inside the files.

Example: Add a custom directory to PATH

Create a file in /etc/paths.d, e.g. custom-tools: sudo nano /etc/paths.d/custom-tools Write the absolute path, one per line, without any shell syntax: /opt/custom/bin Save the file. New terminal windows will automatically include /opt/custom/bin in $PATH. Verify with:

echo $PATH

Loading sequence

When a login shell starts, macOS performs the following steps:

Read /etc/paths (system‑wide entries).

Read each file in /etc/paths.d (additional entries, sorted alphabetically).

Combine them and export PATH.

Execute user‑level configuration files ( ~/.zshrc, ~/.bash_profile, etc.) which may prepend or modify PATH further.

Best practices

PATH – Prefer adding files to /etc/paths.d. This is the recommended, modular way that works for both Bash and Zsh.

Other globals – Use /etc/profile (or /etc/zprofile for Zsh) to export variables such as JAVA_HOME, ANDROID_HOME, GOPATH, etc.

User‑specific settings – Place aliases, functions, and per‑user variables in ~/.bash_profile or ~/.zshrc.

Zsh considerations – Since macOS Catalina, Zsh is the default shell. Its login shell reads /etc/zprofile (which also calls path_helper) and then /etc/zshrc for non‑login shells, followed by the user’s ~/.zshrc.

Conclusion

macOS blends the classic Unix /etc/profile mechanism with a modern, file‑based PATH management system ( /etc/paths.d). Understanding how path_helper assembles PATH allows developers to configure a consistent environment across Bash and Zsh without modifying individual user files.