X
Popular Searches

Why DOS Applications Used White-On-Blue Text

Many DOS applications use white text on a blue background as the default colors.  Why is this the default color choice? The answer, like so many things in technology, is because of its history. You’ll often find this same color scheme on many Windows and Linux applications that run in character mode.

DOS Applications in Color

To understand why applications adopted white-on-blue, it helps to first recall how DOS applications displayed text on the screen. An ever-present DOS application was the word processor. WordStar, WordPerfect, PC-Write, and other word processors were the mainstay of office computing in the 1980s and 1990s. Whichever word processor you preferred, you probably used the default colors: either white text on a black background, or white text on a blue background.

But you might ask, “If you’re editing text that would later be printed on paper, why not show your document in black text on a white background?” To answer that, let’s consider DOS text.

DOS text was character only. You could change the color, but you couldn’t modify the style. There was no bold, italics, and underline “font” in plain text mode. And for more complex documents, you didn’t have a separate text style for links or footnotes. In character mode, the PC could only display plain text. You could change the text color and background color, and that was about it.

To get around this limitation, DOS applications used colors in place of screen formatting. Let’s say your word processor used white text on a black background. You might see bold text in a bright white color, italics text in cyan, underlined text in green, or other text styles in different colors:

White text on a black background

This text is easy to read. You should be able to distinguish the different text styles, and see the different text colors against the main body text.

But reading white-on-black can be very tiring, so many applications adopted a more popular color scheme of white text on a blue background:

White text on a blue background

Even with the same colors for each of the text styles, you can still easily identify the different styles used in this sample. The bright white stands out as bold, the cyan and green identify italics and underlined text.

If we change the colors to try to represent text as it might appear on a printed page, with black text on a white background, we first run into the limitation that background colors can only use the “low intensity” colors. For example, a standard PC display cannot show text with a bright white background. Using the same “style” colors from above, black text on a white background looks like this:

Black text on a white background

But what if you wanted to display bold text in black? Assuming plain black for the text color, you need a different text color to represent bold. There isn’t a darker color of black to represent bold text, so you might instead change bold to use the “bright black” color. This makes the bold text more difficult to read against the white background:

Black text on a white background

And it gets worse if you try to set the text color to “bright black” and display bold text in plain black. The bold text is easy to read, but the body text fades into the white background:

Bright black text on a white background

Simulating a DOS Display

The screenshots don’t completely represent how users saw text in their DOS applications. Computers of the era used CRT displays. These were lower resolution than today’s LCD displays. Where a modern display might support 1920×1080 pixels, standard VGA displays supported only 640×480 resolutions.

I can approximate this lower resolution through graphics software. (I used GIMP on Linux.) I’ve added a very soft “bloom” to each of the screenshots, to simulate the CRT’s tendency to show lighter areas with a slight glow. I’ve also simulated a video degradation, representative of displaying text on a lower-resolution monitor.

Viewing the screenshots with these distortions, you can see how white text on a black background provided the best readability on a VGA monitor of the day. Here, the soft glow that was typical of DOS text on a CRT monitor actually helps make text easier to read:

White text on a black background (VGA)

The more popular white text on a blue background also affords great readability. You can clearly distinguish the different text styles. Even the bright white color for bold remains visible against the blue background. Scaling these images for the website adds a slight artifact with the background “scan lines” – so this might be more representative of a cheap VGA monitor:

White text on a blue background (VGA)

This also demonstrates why using black text on a white background isn’t a great solution for DOS word processing. The CRT adds a soft glow around brighter areas on the screen, causing black text on the white background to appear dim:

Black text on a white background (VGA)

The text becomes increasingly difficult to read if you change the bold text to use a “bright black” color, or if you change the body text to use “bright black” with plain black for bold. The text fades into the background, making the text difficult to read:

Black text on a white background (VGA)
Bright black text on a white background (VGA)

And that’s why most DOS applications used white text on a blue background. When you consider that DOS text only had one “font,” and factor in the limited color set with sixteen text colors and eight background colors, using white-on-blue or white-on-black made applications easier to read. Many applications started out with plain white text on a black background, but added color when CGA, EGA, and VGA became the norm in offices. The extra touch of color, even just a blue background, made the applications feel a bit more modern.

The next time you see a DOS application, or even a Windows console application running in text mode, remember the colors. That’s why white-on-blue is so prevalent.

Jim Hall Jim Hall
Jim Hall is an innovative, high-achieving Senior IT Leader with over 25 years' experience in Linux, open source, and IT Leadership. He has contributed to dozens of open source projects as developer or maintainer, including FreeDOS and GNOME. Jim is also CEO at Hallmentum, where he empowers IT Leaders to drive meaningful change through hands-on training, workshops, and coaching. Read Full Bio »

The above article may contain affiliate links, which help support CloudSavvy IT.