Customize Your Terminal Prompt: Step-by-Step

Updated 14 November 2026 · Standard formula, shown below

Customizing your terminal prompt makes the command line more informative and visually pleasant, showing exactly what you need—like the current directory, Git branch, or time—at a glance. This guide walks you through editing the prompt for Bash and Zsh (the two most common shells) on Linux and macOS. You’ll need a terminal window and a basic text editor; no special tools are required.

What You’ll Need

A terminal emulator (Terminal on macOS, GNOME Terminal, Konsole, etc.)
Access to a shell prompt (Bash or Zsh)
A text editor (nano, vim, or any you prefer)
Basic familiarity with editing dotfiles (like .bashrc or .zshrc)

Step-by-Step

Identify your shell. Run echo $SHELL to see which shell you’re using. If it ends in bash, you’ll edit ~/.bashrc (Linux) or ~/.bash_profile (macOS). If it ends in zsh, edit ~/.zshrc.
Open the config file. Use your editor, e.g., nano ~/.bashrc or vim ~/.zshrc. If the file doesn’t exist, create it.
Find the current prompt setting. Look for a line starting with PS1= (Bash) or PROMPT= (Zsh). If you don’t see one, you’ll add it at the end of the file.
Understand the basics. The prompt is a string with special escape sequences. Common ones:
- \u – username
- \h – hostname (short)
- \w – current working directory (full path)
- \W – current directory basename
- \d – date (e.g., Tue May 21)
- \t – time (24-hour HH:MM:SS)
- \n – newline
- \$ – shows # for root, $ otherwise
Write a simple custom prompt. For example, to show username, hostname, and current directory on one line, set:
```
PS1='\u@\h:\w\$ '
```
In Zsh, use PROMPT='%n@%m:%~%# ' (percent sequences).
Add color (optional). Wrap parts in color codes. For Bash, use \[\e[0;32m\] for green, \[\e[0m\] to reset. Example:
```
PS1='\[\e[0;32m\]\u@\h\[\e[0m\]:\w\$ '
```
In Zsh, use %F{green}%n@%m%f:%~%# .
Include Git branch (if you use Git). For Bash, add a function that extracts the branch name and include it. A simple version:
```
git_branch() {
  branch=$(git symbolic-ref --short HEAD 2>/dev/null)
  if [ -n "$branch" ]; then echo " ($branch)"; fi
}
PS1='\u@\h:\w$(git_branch)\$ '
```
For Zsh, you can use %F{cyan}%c%f and the built-in vcs_info module (requires setup).
Save and reload. Save the file, then run source ~/.bashrc (or source ~/.zshrc) to apply changes immediately. Alternatively, open a new terminal window.
Test and iterate. Your prompt should now reflect the changes. If something looks off, edit again and reload.

Common Mistakes

Forgetting to escape correctly: In Bash, backslashes and special characters must be escaped properly. Use single quotes around the PS1 string to prevent premature expansion.
Using Zsh syntax in Bash: Percent sequences like %n don’t work in Bash; use backslash sequences instead.
Not reloading the config: Changes won’t appear until you source the file or start a new terminal.
Breaking the prompt with unclosed color codes: If you start a color code but forget to reset it, your entire terminal text may be colored. Always include \[\e[0m\] to reset.
Overcomplicating: Adding too many elements can make the prompt cluttered and slow (especially Git commands). Keep it simple.

Tips

Use a prompt generator: Online tools like bashrcgenerator.com can help you create a prompt visually and copy the code.
Keep a backup: Before editing, copy your config file: cp ~/.bashrc ~/.bashrc.bak.
Use multi-line prompts: Put the path on one line and the input on the next to avoid long lines.
Show exit status: Add \$? to see the exit code of the last command, useful for debugging.
Use a prompt theme (Zsh): If you use Zsh, consider installing a framework like Oh My Zsh for pre-built themes, but be aware that it adds overhead.

Troubleshooting

Prompt not changing: Make sure you edited the correct file for your shell. Check with echo $SHELL. Also ensure you didn’t have a syntax error; run bash -n ~/.bashrc to check for errors.
Prompt shows literal text like \u: This usually means you used double quotes instead of single quotes. In Bash, double quotes allow expansion, so backslashes may be interpreted differently. Use single quotes.
Colors not showing: Some terminals need TERM=xterm-256color. Also, ensure you’re using the correct escape sequences and that you reset colors properly.
Git branch not appearing: Make sure you’re in a Git repository and that the git command is available. Test the function separately in the terminal.
Prompt is very slow: If you have a Git branch function, it runs every time the prompt is displayed. If the repository is large, it can be slow. Consider caching or using a faster method.
Changes revert after restart: Ensure you’re editing the correct startup file. Some systems may use .profile or .bash_profile instead of .bashrc for login shells.

Frequently Asked Questions

How do I make my prompt show the time?
In Bash, add \t (HH:MM:SS) or \@ (12-hour time) to your PS1. In Zsh, use %* for 24-hour time or %T for 12-hour.
Can I have different prompts for different directories?
Yes, you can use a function in PS1 that checks the current directory and outputs different strings. For example, if you’re in a project folder, show the Git branch.
How do I make the prompt show the full path?
Use \w in Bash (full path) or %~ in Zsh. If you want just the current folder, use \W or %c.
Why does my prompt not update when I change directories?
The prompt is re-evaluated after each command, so it should update. If it doesn’t, you might have a static string; make sure you’re using the escape sequences, not literal text.
Is there a way to make the prompt show the exit status of the last command?
Yes, add \$? in Bash or %? in Zsh. This shows the exit code (0 for success).
Can I use emojis in my prompt?
Yes, most modern terminals support emojis. Simply paste the emoji character into your PS1 string. Be aware that some emojis may not render in older terminals.

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.