An increasing number of command-line software programs output text with ANSI color escape codes by default. While some developers and users obviously prefer seeing these colors, many users don’t. Unfortunately, every new piece of software seems to have a different way of disabling colored text output and some software has no way at all.
Accepting the futility of trying to reverse this trend, an informal standard is hereby proposed:
All command-line software which outputs text with ANSI color added should check for the presence of a
NO_COLORenvironment variable that, when present (regardless of its value), prevents the addition of ANSI color.
By adopting this standard, users that prefer to have plain, non-colored text output can set one environment variable in their shell to have it automatically affect all supported software.
This website will document which software has adopted this standard and when support was added. For software that has not or will not adopt this standard, an attempt will be made to document how to otherwise disable color.
To add software to this site, clone this site’s Git repository and submit a pull request.
NO_COLORto disable default color output
|alogview||Android logcat Filter||2018-10-31|
|Bloop||Compilation/test server for Scala and Java||2018-07-02|
|ColorDebug||Colorful command line output C/C++ macros||2019-02-09|
|colored||Rust crate for coloring terminal output||1.7.0|
|crayon||R package for colored terminal output||2018-02-08|
|deno||Secure TypeScript runtime||0.2.11|
|ffind||Rust utility to find files and folders||2018-03-24|
|forest-arborist||Manage a loosely coupled forest of git or hg repositories||1.2.0|
|fselect||Command-line utility for finding files with SQL-like expressions||0.6.1|
|gopass||Password store for teams||1.8.0|
|Homebrew||Package manager for macOS||1.5.5|
|KBSecret||Secret manager backed by Keybase and KBFS||1.4.0|
|kitten||Tiny multi-server automation tool||0.2.14|
|konch||Python shell/REPL configuration tool||4.0.0|
|LogColor||Python library for coloring output in log messages||2018-01-24|
|lr||File list generator||2018-01-29|
|mblaze||Unix utilities to deal with Maildir||2018-01-29|
|Middleman||Ruby-based static site generator||2019-02-18|
|NGLess||Domain specific language for bioinformatics||2018-10-29|
|nvh||Node Version Helper||4.1.0|
|Pastel||Tiny .NET Core library for coloring console output||1.2.0|
|picocli||A mighty tiny Java command line interface||3.9.0|
|pulumi||Programming-language-based IaC framework||0.14.3|
|PyDERASN||Python ASN.1 DER library||2018-02-14|
|rsmodules||Manage your environment by the use of modulefiles||2018-10-09|
|smenu||Terminal selection filter||2018-02-05|
|Snow||Testing library for C||2018-01-24|
|txtnish||Twtxt microblogging client||2018-08-31|
|twa||A tiny web auditor with strong opinions||1.1.0|
|undertime||Timezone coordination tool||2018-06-06|
|The Silver Searcher||
Why not just set
xterm without color support?
Or change all color definitions in the terminal to print black?
The terminal is capable of color and should be able to print color when
NO_COLOR is a hint to the software running in the terminal to suppress
addition of color, not to the terminal to prevent any color from being
It is reasonable to configure certain software such as a text editor to use color or other ANSI attributes sparingly (such as the reverse attribute for a status bar) while still desiring that other software not add color unless configured to. It should be up to the user whether color is used, not the software author.
How should configuration files and command-line arguments be processed
in the presence of
User-level configuration files and per-instance command-line arguments
A user should be able to export
$NO_COLOR in their shell configuration
file as a default, but configure a specific program in its configuration
file to specifically enable color.
This also means that software that can add color but doesn’t by default
does not need to care about
$NO_COLOR, because it will only ever be
adding color when instructed to do so (as it should be).