How to Edit Environment Variables | GUI & Shell Methods

Editing environment variables on Windows is done through System Properties, while macOS and Linux use shell files like ~/.bashrc.

Environment variables quietly control where your system finds executables, how software configures itself, and what preferences stick between sessions. Changing them is a routine task for developers, power users, and anyone setting up a new toolchain. The right method depends entirely on your operating system and whether you need a temporary or permanent change — this guide covers all of them.

Editing Environment Variables on Windows

The standard route on Windows 10 and 11 goes through the System Properties dialog, and the steps are identical on both versions.

Open Control Panel, then click System and Security > System. In the left sidebar, click Advanced system settings. At the bottom of the System Properties window that opens, click Environment Variables.

You’ll see two lists stacked vertically. User variables apply only to your account. System variables apply machine-wide to all users. To add a new variable, click New. To change an existing one, select it and click Edit. To remove one, select it and click Delete. Close each dialog with OK to save your changes.

System variables require Administrator privileges. If the OK button stays grayed out or changes don’t stick, relaunch Control Panel using Run as administrator and try again. User variables never need admin rights — any account can edit its own.

You can also use the command line for persistent user-level changes. The setx command sets a user variable from any Command Prompt window, while PowerShell’s [Environment]::SetEnvironmentVariable("Name", "Value", "User") does the same. Both are documented alongside the GUI method in Oracle’s guide to creating and modifying environment variables on Windows.

User vs. System Variables: What’s the Difference?

User variables belong to one account — switch to a different user and those variables disappear. System variables load for every user at boot and are visible to all processes, including services running in the background.

The practical rule: if only one person on the machine needs a variable, use a user variable. If every account needs it or a system service depends on it, use a system variable. The Windows GUI makes both scopes visible side by side, so you can see exactly what’s set at each level without any command-line detective work.

Editing Environment Variables on macOS and Linux: Shell Configuration Methods

On both macOS and Linux, persistent environment variables are set inside shell configuration files that load each time a terminal starts. Which file to edit depends on which shell you use.

For bash, add the line export VARIABLE_NAME="value" to ~/.bashrc on Linux or ~/.bash_profile on older macOS versions. Modern macOS ships with zsh as the default shell, so the file to edit is ~/.zshrc — the syntax is the same: export VARIABLE_NAME="value". For csh or tcsh, use setenv VARIABLE_NAME "value" in ~/.cshrc or ~/.tcshrc.

After saving the file, run source ~/.zshrc (or the equivalent for your shell) to load the changes into the current session. New terminal windows will pick up the variable automatically.

For system-wide variables on Linux, edit /etc/environment with administrator privileges. Entries follow a plain NAME=value format — no export keyword needed. This file affects all users at login. For a single application that doesn’t need a session-wide variable, Linux also allows setting variables directly in the app’s .desktop file.

What’s the Safest Way to Edit PATH on Windows?

The safest approach is to use the list-based editor that Windows 10 and 11 provide — add each directory path as a separate entry rather than editing the entire string value.

Select Path in the Environment Variables dialog, click Edit, and you’ll see a list of individual paths. Click New, paste or type the directory path, and confirm. This avoids the classic mistake of accidentally deleting every other path entry when you intended to add one. The list editor keeps each directory separate and validates the format, though it won’t check whether the folder actually exists.

If you’re working on an older Windows version or a locked-down machine that lacks the list editor, copy the full PATH value into a text editor first, add your entry with a semicolon separator, and paste the result back. Double-check the whole string before clicking OK.

Common Mistakes to Avoid

A few recurring errors trip up even experienced users. Most are easy to fix once you know what to watch for.

Once you know the correct method for your platform and scope, editing environment variables takes only a minute. The Windows GUI handles the work visually with clear scope separation. macOS and Linux users get the same result with a single export line in a shell file. In both cases, the only real trap is forgetting to open a new terminal window afterward.