Introduction

If Git output appears plain or hard to read in macOS Terminal, the issue is usually configuration rather than a Git bug. Git only shows colors when the terminal reports color support and the pager can pass ANSI color codes through correctly. Once those pieces are aligned, commands such as git diff, git status, and git log become much easier to scan.

Start With Git's Own Settings

Git has built-in color support, and the simplest way to enable it is through color.ui.

git config --global color.ui auto

auto means Git will emit color when writing to an interactive terminal and avoid raw color codes when output is redirected to a file.

You can also set individual sections if you want more control:

1git config --global color.status auto
2git config --global color.branch auto
3git config --global color.diff auto
4git config --global color.interactive auto

To verify the configuration:

git config --global --get color.ui
git config --global --list | grep '^color\.'

If color.ui is false, Git will stay monochrome even if the terminal supports color perfectly.

Make Sure the Terminal Type Supports Color

Git relies on the terminal environment to decide what capabilities are available. On macOS Terminal, TERM should usually be something like xterm-256color.

Check the current value:

echo $TERM

If the value is something minimal or unusual, update your shell profile. For zsh:

printf '\nexport TERM=xterm-256color\n' >> ~/.zshrc
source ~/.zshrc

For bash:

printf '\nexport TERM=xterm-256color\n' >> ~/.bash_profile
source ~/.bash_profile

Do not set this blindly in every environment, but on a normal local macOS terminal session it is a common and reasonable choice.

Fix the Pager Path

Git often sends long output through a pager such as less. If the pager is not configured to display raw control sequences, colors may disappear or look broken.

A safe configuration is:

git config --global core.pager "less -FRX"
export LESS='-FRX'

If you still see escaped color codes instead of actual colors, add -R:

git config --global core.pager "less -FRX -R"
export LESS='-FRX -R'

That tells less to display ANSI color sequences instead of printing them literally.

You can test it with:

git diff

If git diff is colored when the output is short but not when it scrolls through less, the pager is the part to fix.

Customize the Colors

Once color output works, you can tune the palette.

1git config --global color.branch.current "yellow reverse"
2git config --global color.status.added green
3git config --global color.status.changed red
4git config --global color.diff.meta "yellow bold"

These settings are optional, but they are useful if the default contrast is hard to read in your terminal theme.

To inspect the resulting config file:

cat ~/.gitconfig

Git stores the settings there unless you chose a different config scope.

A Minimal Working Setup

For most macOS users, this is enough:

git config --global color.ui auto
git config --global core.pager "less -FRX -R"
echo 'export TERM=xterm-256color' >> ~/.zshrc

Then open a new terminal session and test:

git status
git diff --cached
git log --decorate --oneline --graph

If all three display sensible colors, the setup is working.

Common Pitfalls

A common mistake is enabling color in Git but leaving the pager unable to render it. In that case, colors may disappear whenever output scrolls.

Another mistake is using color.ui always by default. That can put raw escape codes into redirected files or scripts. auto is usually the safer choice.

Developers also sometimes override TERM with a value that does not match the real terminal capabilities. If TERM is wrong, tools can misbehave in subtle ways.

Finally, remember that terminal themes matter. A color can technically be present but still unreadable against your background, so contrast may need adjustment.

Summary

• Enable Git colors with git config --global color.ui auto.
• Ensure your terminal reports a color-capable TERM such as xterm-256color.
• Configure less so paged Git output preserves color.
• Customize specific Git color slots only after the basic setup works.
• Test with git status, git diff, and git log in a fresh terminal session.