BashSnippets / Tools / Bash $PATH Debugger
FREE TOOL

Bash $PATH Debugger

Paste your $PATH below. Instantly see what's broken, what's duplicated, and get a clean export line.

Your $PATH value
Run: echo $PATH — then paste the output here
⚠ "Load My PATH" only works when this page is opened locally in a terminal browser — it cannot read your actual system PATH from a web browser.
Or try an example: load example $PATH
← Paste your $PATH and click Analyze
Copied to clipboard
// recommended hosting
Test your PATH fixes on a clean Linux server
Spin up a fresh Ubuntu 24.04 droplet and test your PATH configuration without touching your local machine.
Get $200 Free Credit →
// guide

How to Use This Tool

01

Open a terminal and run: echo $PATH

02

Copy the output and paste it into the input box above.

03

Click Analyze PATH to see which directories exist, are missing, or appear more than once.

04

Copy the cleaned export PATH= line and add it to your ~/.bashrc or ~/.zshrc.

// faq

Frequently Asked Questions

Why does "command not found" happen even when a program is installed? +

Usually because the directory containing the binary isn't in your PATH. Use this tool to find missing or mistyped directories.

What does exit code 127 mean in bash? +

Exit code 127 means "command not found" — bash searched your entire PATH and couldn't locate the binary. Check our Exit Code Lookup tool for a full reference.

Can I use this tool on macOS? +

Yes. macOS uses the same colon-separated PATH format as Linux. Paste your $PATH and the analysis works identically.

How do I permanently fix my PATH? +

Add the corrected export PATH= line to ~/.bashrc (bash) or ~/.zshrc (zsh), then run source ~/.bashrc to apply it immediately.

// learn more

Related Snippets

beginner · scripting
Bash Error Handling
View snippet →
beginner · monitoring
Check if Website Is Up
View snippet →
tool · debugging
Exit Code Lookup
Open tool →