Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've downloaded an application that is a command-line application, and want to put it somewhere where I can run it from the command-line without having to type the path explicitly.

  1. What are the conventional paths used for something like this? /usr/bin? Are there different options, one if I want it for all users, and one if I want it for just a particular user, like my administrator account?

  2. Or should I put it in its own directory under the Applications directory, and add it to the path? If so, which file controls where the path is set?

share|improve this question
up vote 17 down vote accepted

Macs are very unusual in this regard. The default $PATH variable for a regular user looks like this:


By putting /usr/local/bin after /usr/bin and /bin, Mac upends the whole system. Normally, you can put something into /usr/local/ (say a second Perl, compiled in some non-standard way), and then a regular user will hit the custom one rather than the system-wide one first. This is good. Users can get variants, but the system stays pure. In any case, you can put things (as is normal) into /usr/local, but if there is something by the same name already in /usr/bin or /bin, that will get found first.

To fix this, you can change the regular user's $PATH by editing the .profile file in the user's home directory. (That file doesn't exist initially, but you can create it easily.) I do that soon after I start any new Mac.

Semi-related: Homebrew provides excellent package management for Macs. By default, Homebrew installs software into /usr/local, but it does so in a way that makes it very easy to remove things and return to a vanilla state later.

share|improve this answer

/usr/local/bin and /usr/local/sbin are well worth adding to your path, as a lot of makefiles for source builds are defaulted to install there.

If you use MacPorts, it's worth adding /opt/local/bin and /opt/local/sbin as well.

The best way to do this is to add

export PATH=/usr/local/bin:/usr/local/sbin:/opt/local/bin:/opt/local/sbin:$PATH

to the .bashrc file in your home directory (which is hidden, so the CLI is the best way to to do this), or, if you want to change the system wide path, add the same line to /etc/bashrc (not hidden), but you will need to sudo to do this.

If you don't have a .bashrc in any user's home, you can make one and add this line to it, but remember to change the permissions on the file you create to make it readable by the user in question (obviously not relevant if you're doing it for your own profile).

The $PATH at the end appends the system default path to whatever you put before. Note that the system searches for binaries in the order of paths given, so if you install a binary in /usr/local or /opt/local that is also installed by default on the system, the versions you install will be found first, which can (though rarely) upset things. It is worth watching out for.

Good information is here.

I should note that the above assumes you are using Bash for the shell, which is the default on Mac OS X v10.4 (Tiger) and Mac OS X v10.5 (Leopard), but not on earlier systems, which used tcsh instead, which has a different syntax.

I hope that helps...

share|improve this answer
/usr/local/bin is already in a default OS X $PATH (though too late - see my answer). If you use MacPorts, its installer should edit your path as necessary - at least it always has in my experience. That said, it's good for users to know what it's doing (and why). – Telemachus Jul 17 '09 at 15:13
well spotted @Telemachus: whenever I build a Mac for myself, I customise the hell out of the path first thing, so I can never remember what's standard and what's mine! – avstrallen Jul 17 '09 at 15:15
I know what you're daying about the MacPorts installer customising the paths in .profile, but I have had an occasion in the past when for some reason, I know not what, this failed to stick (which confused the hell out of me for quite a while!)... so since then I tend to wire it in by hand... – avstrallen Jul 17 '09 at 15:18
"which is hidden, so the CLI is the best way to to do this": dumb question, how do you run TextEdit on a file from the command prompt? – Jason S Jul 17 '09 at 15:32
No such thing as a dumb question: use the open command with the filename as an argument and it should open with whatever is set as the default text editor (TextEdit as standard). – avstrallen Jul 17 '09 at 15:42

I tend to go with /usr/local. Here's a nice explanation why.

share|improve this answer
very helpful, thanks! – Jason S Jul 17 '09 at 14:55
Yep, it's pretty much the same as other *nix operating systems in that regard. – jtbandes Jul 24 '09 at 17:29
Link is broken. – Chris Nolet Jul 26 '12 at 23:42
link works for me – AJcodez Jun 17 '13 at 7:15

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.