colorama does nothing at all outside Windows
Simple cross-platform colored terminal text in Python
At a glance
- What is it?
- A small library that makes ANSI escape sequences work in Windows terminals, where the page says it does nothing on other platforms, recommends one entry point while declaring it will never fix bugs in the older one, and admits that its own heuristic can strip your colours on Linux.
- Who is it for?
- colorama is worth reaching for when you need coloured terminal output on Windows and nothing else, because the modern entry point is two lines with four documented safety guarantees and it delegates to the operating system rather than emulating it. Two things to know.
- Can I use it commercially?
- Yes. BSD-3-Clause is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Activity is slowing. The repository last received commits 6 months ago.
- What is it written in?
- Mainly Python, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- tartley/colorama3,798 ★ · +5
| Repository | 2026-09-24 | 2026-11-15 |
|---|---|---|
| tartley/colorama | 3.8k | 3.8k |
5 Stars in the last 52 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The mechanism changed, and the scope never widened
The page is blunt about what the library is for: it makes ANSI escape character sequences work under Windows. On Unix and Macs those sequences have always worked, so the description says that on other platforms Colorama does nothing. What changed is how it does its one job. On an older Windows, it wraps stdout and stderr in a file object that intercepts the sequences and issues the appropriate Win32 calls to emulate them. On a recent version of Windows 10 or better, the newer entry point instead flips a configuration switch so that Windows' own built-in ANSI support does the work. So there are two implementations behind one import, selected by which function you call and by what the host turns out to be, and on Linux both of them are no-ops by design.
The project declines to fix bugs in the interface most code calls
There are two entry points and the page tells you which to use.
from colorama import just_fix_windows_console
just_fix_windows_console()That is the recommendation: depend on version 0.4.6 or newer and call this. The older one is `init()`, and three separate sentences are spent on why not to. It is not safe to call more than once, because you can end up with multiple layers of wrapping and broken ANSI support. Most users should use the newer function. And then the sentence that decides the maintenance policy for a library with a decade of users: the old interface will be supported indefinitely for backwards compatibility, but they do not plan to fix any issues with it, also for backwards compatibility. That is a project declining, in print, to repair bugs in an API its own users depend on.
A heuristic the page calls not particularly clever can strip your colours
This is the most surprising thing in the documentation. Calling the older entry point makes the library apply a heuristic to guess whether stdout and stderr support ANSI, and if it decides they do not, it wraps them in a file object that strips the escape sequences out before printing. The page then adds two sentences that change how you read the library: this happens on all platforms, and the heuristic is not particularly clever. So on a Linux terminal with colour, calling `init()` can remove your colours because a guess came out wrong, and calling `just_fix_windows_console()` cannot. That is a fair trade for the library's purpose and an unpleasant surprise for anyone who installed it for cross-platform reasons and then switched to the older interface on the assumption it was harmless.
The modern entry point comes with four stated safety guarantees
The page enumerates what the newer function will and will not do, which is unusual for a library this small. It is safe to call multiple times. It is safe to call on non-Windows platforms, where it simply will not do anything. It is safe to call when one or both of the output streams are redirected to a file, and it will not touch those streams. And in all other circumstances it does nothing whatsoever, which the page glosses as the idea being that it makes Windows behave like Unix with respect to ANSI handling. Each of those is a case where the older interface would have wrapped a stream and changed its behaviour, so the four sentences are really a changelog of the bugs the newer one avoids.
The page names an alternative and explains why it is not the default
There is an alternative approach mentioned before the library is described at all: install `ansi.sys` on Windows, which provides the same behaviour for all applications running in terminals. The page then says Colorama is intended for situations where that is not easy, giving the parenthetical that maybe your app does not have an installer. That is a precise statement of scope, and it reframes the project: this is not the better way to handle colour on Windows, it is the way to handle colour on Windows for an application that cannot install a system component. It also explains why the library stays small, since the whole problem is scoped to embedding in something you do not control.
The example prints dim text and the screenshots admit it does nothing
The coloured output example is five lines using the Fore, Back and Style constants, and the page calls those constants deliberately rudimentary.
from colorama import Fore, Back, Style
print(Fore.RED + 'some red text')
print(Style.DIM + 'and in dim text')Then the screenshots section says the opposite about one of them: on Windows, Colorama does not support ANSI dim text, and it looks the same as normal text. So the sample prints dim text, and the page's own images demonstrate that the line had no effect. Anyone reading only the code would assume dim works everywhere. The same section that admits the limitation also points at three other libraries, describing them as venerable, fabulous and incredible, and suggests using one of them to generate the colours while keeping Colorama for the terminal handling.
An empty requirements file and five PowerShell scripts
The claim that there are no requirements other than the standard library is enforced by a file whose entire contents are one comment.
# noneThat file still exists so the bootstrap target has something to pass on the command line, alongside a separate development requirements file. Windows has its own parallel set of scripts: five PowerShell files for bootstrapping, building, cleaning, releasing and testing, alongside the Makefile. Two of them are called test release, once as an extensionless script and once as a PowerShell script, which is a small trap for anyone typing the target name by hand on either platform. The rest of the tree is conventional: a changelog, a licence file, a security file, a contributor note about the readme itself, and a directory of demos and screenshots.
The Makefile describes itself as a Windows XP cheatsheet
The build file opens with a comment that is worth quoting in full, because it explains what the project considers its own tooling to be: this makefile is just a cheatsheet to remind me of some commonly used commands, and the commands are generally executed on Ubuntu, or on Windows XP with Cygwin binaries at the start of the path. So a library whose entire purpose is modern Windows support has a build file that describes a workflow last current when Windows XP was. Two other details are visible in it. The help target is implemented by grepping the makefile for lines ending in a comment marker and printing the target names in cyan, which is why every target carries a trailing comment. And the release target uploads to a repository whose name is hardcoded, so publishing depends on that name existing in the developer's own twine configuration.
Editorial conclusion
colorama is worth reaching for when you need coloured terminal output on Windows and nothing else, because the modern entry point is two lines with four documented safety guarantees and it delegates to the operating system rather than emulating it. Two things to know. The name overstates the scope, since the library is a no-op on Linux and macOS, so a cross-platform dependency on it is really a dependency on Windows behaviour. And the older init interface, which most existing code still calls, can strip your colours on any platform on the judgement of a heuristic the page itself calls not particularly clever.
Frequently asked questions
Is Colorama still maintained?
The page says the older init interface will be supported indefinitely for backwards compatibility but that no issues with it are planned to be fixed, and it recommends depending on 0.4.6 or newer and calling just_fix_windows_console instead. The project's own classifier reads Development Status 5, Production/Stable, and it is tested on CPython 3.9 through 3.13 and on PyPy 3.11.
how to install colorama
With pip install colorama, or with conda install from the anaconda channel. The page states there are no requirements other than the standard library, and the repository's own requirements file contains only the comment none. Nothing else is needed for either route.
What is Colorama used for?
Making ANSI escape sequences work in Windows terminals. On a recent version of Windows 10 or newer it flips the built-in support on; on an older version it wraps stdout and stderr so the sequences are emulated with Win32 calls. On Linux and macOS it does nothing.
Why does colorama remove my colours on Linux?
That happens only if you call the older init interface. It applies a heuristic to guess whether the output streams support ANSI and, if it decides they do not, strips the escape sequences out before printing. The page says this occurs on all platforms and that the heuristic is not particularly clever.
Should I use init() or just_fix_windows_console()?
The page says most users should depend on version 0.4.6 or newer and use the newer function. init is not safe to call more than once, and while it will be supported indefinitely, no issues with it are planned to be fixed.
Does colorama support dim text on Windows?
No. The page says the screenshots show that on Windows dim text looks the same as normal text, even though the constant is present and appears in the example. The sample prints dim text and the page's own images show the line having no effect.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/tartley-colorama)Star history chart for your README
[](https://hysenlabs.com/projects/tartley-colorama)Was this useful?