The Origin of the Green, Yellow, and Red Color Scheme for Traffic Lights


Recommended Posts

Today I found out the origin of the green, yellow, and red color scheme for traffic lights.

This color scheme derives from a system used by the railroad industry since the 1830s. At this time, railroad companies developed a lighted means to let train engineers know when to stop or go, with different lighted colors representing different actions. They chose red as the color for stop, it is thought, because red has for centuries been used to indicate danger. For the other colors, they chose white as the color for go and green as the color for caution.

The choice of a white light for go turned out to cause a lot of problems. For instance, an incident in 1914 where a red lens fell out of its holder leaving the white light behind it exposed. This ended with a train running a ?stop? signal and crashing into another train. Thus, the railroad decided to change it so the green light meant go and a caution ?yellow? was chosen, primarily because the color is so distinct from the other two colors used.

So how did this system transfer to the road? In London, England in 1865 there was a growing concern over the amount of horse-drawn traffic causing danger to pedestrians trying to cross the roads. A railway manager and engineer named John Peake Knight, who specialized in designing signaling systems for the British railway, approached the Metropolitan Police with the idea of using a similar semaphore/lighted system for road traffic. In the daytime, this semaphore method used an arm or arms that could be raised or lowered by a police officer, notifying carriages when they should stop when the arm(s) stuck out sideways. At night, his system used the red and green colors to indicate the same type of thing, again traditional to the railroads.

His proposal was accepted and, on December 9, 1868, the system was put in place at the junction of Great George and Bridge Street in London, near Parliament. The system worked extremely well? for about a month. That?s when one of the gas lines that supplied the lights began to leak. Unfortunately, the policeman who was operating the arm was unaware of the leak and ended up being severely burned when the lamp exploded. Thus, despite its early success, the semaphore traffic system was immediately dropped in England.

On the other side of the pond, signaling traffic in the United States also used policemen as it was thought that people would not follow a set of rules unless there was some form of law enforcement present. Towers that allowed officers a better view of the traffic became commonplace in the 1910s and 1920s. During this time, officers could either use lights (usually red and green after the railroad system), semaphores, or simply just wave their arms to let traffic know when to stop or go.

In 1920 in Detroit Michigan, a policeman named William L. Potts invented the four-way, three-color traffic signal using all three of the colors now used in the railroad system. Thus, Detroit became the first to use the red, green, and yellow lights to control road traffic. Many inventors continued to come up with different designs for traffic signals, some adopting the red, yellow, green color scheme and some not. Most usually needed a person to push a button or flip a switch to change the light. As you might expect, this man-power intensive way to change the lights proved costly.

In the late 1920s, several ?automatic? signals were invented. The first ones used the simple method of changing the lights at specific timed intervals. However, the drawback of having some vehicles stopped when there were no cars going in the other direction annoyed people. An inventor named Charles Adler Jr. had an idea to get around this problem. He invented a signal that could detect a vehicle?s horn honking. A microphone was mounted on a pole at the intersection and once the vehicle stopped, all they need do is honk their horn and the light would change. To keep people from continually honking to get the light to change, and thus causing havoc, once the light was tripped, it wouldn?t change again for 10 seconds, allowing at least one car to get through. Presumably this system was incredibly annoying to people walking by and to nearby homes and businesses.

A less annoying automatic signal was invented by Henry A. Haugh. This system used two metal strips that sensed pressure. When a passing car pushed the two strips together, the light would soon change to allow that car to go.

All of these different types of lighting systems began to present a problem. Drivers could drive through different areas and encounter several different types of systems, causing confusion and frustration. So, in 1935, the Federal Highway Administration created ?The Manual on Uniform Traffic Control Devices.? This document set uniform standards for all traffic signals and road signs.

Bonus Facts:

  • Current traffic systems use a variety of methods to optimize throughput in intersections. For instance, some use such things as lasers or rubber tubes filled with air to sense pressure (often the bane of motorcyclists and small car owners); however, the most common is the ?inductive loop? method. You?ve probably seen the groves cut in the roadway just at the stop line of traffic lights. The common misconception is that there is a scale under these grooves, sensing the weight of a vehicle. In actuality, embedded in these grooves are what is known as an inductive loop. Inductive loops work by detecting a change of ?inductance? or magnetic field. It uses a wire wrapped around some metal with a power source. When the wire wrapped around the metal is powered, it begins to build up a magnetic field. Sensors known as inductance meters continually check the inductance of the coil. Once a car, which contains a lot of different types of metal, enters the inductors? magnetic field, the inductance rises and lets the system know a vehicle is parked over it. From here, different municipalities will use different algorithms to tell the lights how to use this information, thus how long lights stay red or green.
  • Older incandescent traffic light bulbs typically used 175 watt bulbs. New LED traffic lights use only around 10-25 watts.
  • In the early police officer manned traffic control systems, police officers often used red for stop and green for go, but rather than have a yellow light, they simply blew a whistle to indicate that they were about to change the signal.
  • Another early traffic light system, developed by Earnest Sirrine, threw out the whole red/green paradigm and instead had lit words saying ?Proceed? and ?Stop?.
  • The word ?semaphore? comes from the Ancient Greek words s?ma, meaning ?sign?, and ?phoros?, meaning ?bearer? or ?bearing?. So, essentially, ?semaphore? translates to ?sign bearer?.
  • The railroad semaphore system was originally patented by Joseph James Stevens in the 1840s.
  • In the U.S. and some other countries, modern traffic signal lights are either 8 or 12 inches in diameter and must be visible in every kind of weather and lighting condition.

  • Like 2

Current traffic systems use a variety of methods to optimize throughput in intersections. For instance, some use such things as lasers or rubber tubes filled with air to sense pressure (often the bane of motorcyclists and small car owners); however, the most common is the ?inductive loop? method. You?ve probably seen the groves cut in the roadway just at the stop line of traffic lights. The common misconception is that there is a scale under these grooves, sensing the weight of a vehicle. In actuality, embedded in these grooves are what is known as an inductive loop. Inductive loops work by detecting a change of ?inductance? or magnetic field. It uses a wire wrapped around some metal with a power source. When the wire wrapped around the metal is powered, it begins to build up a magnetic field. Sensors known as inductance meters continually check the inductance of the coil. Once a car, which contains a lot of different types of metal, enters the inductors? magnetic field, the inductance rises and lets the system know a vehicle is parked over it. From here, different municipalities will use different algorithms to tell the lights how to use this information, thus how long lights stay red or green.

Most of this is completely false. Most are simply now timed base (based on a study of passing traffic). If 60 seconds pass, its time to go off, another 60 go on, etc....

Good article but there is a question:

Is the other light, besides green and red, actually yellow, amber or orange? :)

False.

I know one that as soon as you hit the button, it swithes to red. Obviously when it switches back to green, you cant hit the button AGAIN and it goes to red. There is a small timeout period.

Yea, I know a few that as soon as you hit the button, the "Stop walking" light will start to flash beginning the countdown for the light change.

This topic is now closed to further replies.
  • Posts

    • i got a better prices on reddit /homelabsales. same drives for $80 less
    • The fact that memory in general is so high I have to take a loan out to build a computer now is just beyond stupid. Who's really to blame here? Low supply or high demand?
    • Display Driver Uninstaller (DDU) 18.1.5.5 by Razvan Serea Display Driver Uninstaller (DDU) is a utility for completely removing AMD/NVIDIA/INTEL graphics drivers and related packages from your system, attempting to eliminate all leftovers (including registry entries, folders and files, driver store). Though AMD/NVIDIA/INTEL drivers can usually be removed via the Windows Control Panel, this uninstaller tool was created for situations where standard uninstall fails, or when you need to fully remove NVIDIA or ATI graphics card drivers. After using this driver cleaner, your system will behave as though it’s the first time you’re installing a new driver—similar to a fresh Windows installation. As with all such tools, we recommend creating a restore point beforehand, allowing you to undo changes if issues arise. If you're having trouble installing an older or newer driver, try it—there are reports that it resolves such problems. Recommended usage: The tool can be used in Normal mode but for absolute stability when using DDU, Safemode is always the best. Make a backup or a system restore (but it should normally be pretty safe). It is best to exclude the DDU folder completely from any security software to avoid issues. You do NOT need to uninstall the driver prior using DDU. Requirements: .NET Framework 4.8 Compatible with Windows 7, 8, 8.1, 10, and 11 (32-bit or 64-bit) Note: Using on Insider Preview builds is at your own risk. Display Driver Uninstaller (DDU) 18.1.5.5 changelog: Added 'Reset to recommended' button for the Options. General fixes and improvements. Download: Display Driver Uninstaller (DDU) 18.1.5.5 | 1.7 MB (Freeware) Download: DDU Portable | 1.2 MB Links: Display Driver Uninstaller Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • WACUP 1.99.51.24568 Preview by Razvan Serea WACUP (WinAmp Community Update Project) is a modern, enhanced version of the classic Winamp music player, designed for better stability, performance, and compatibility. Built for Windows, WACUP retains the familiar Winamp interface while adding 64-bit support, bug fixes, and new features like improved audio format support, customizable skins, and optimized playlist management. Unlike bloated alternatives, WACUP focuses on lightweight performance and regular updates, making it the best choice for fans of the classic Winamp experience. Basically, if you miss the good old days of Winamp and want a modern upgrade that doesn’t mess things up, WACUP is for you! WACUP key features: Classic Winamp Feel – Keeps the familiar interface and functionality. Bug Fixes & Stability – Fixes old Winamp issues and improves performance. 64-Bit Support – Works better on modern systems. More Formats & Plugins – Supports additional audio formats and third-party plugins. Customizable UI – Skins and tweaks for a personalized look. Better Library Management – Improved playlists, media organization, and search. No Bloat – Focuses on performance without unnecessary extras. Regular Updates – Community-driven development with new features and fixes. WACUP 1.99.51.24568 Preview changelog: Fixed a deadlock seen from the recent crash reports when doing some of the drag + drop actions within the media library window Fixed a loading crash seen related to a problem with some of the artwork cache image files being restored which should now be better handled allowing for the bad image to be removed without it failing Fixed a deadlock seen from the recent crash reports when the internal metadata cache clearing is triggered which could block the main ui thread for too long with this now being moved to a background thread Fixed some performance issues with some of the methods related to determining artwork support which mainly affected the local library import / refresh (this is still slower for some compared to other players because there's more data & artwork aspects being checked for which means doing more processing on a single file despite the best of attempts to reduce duplicate / heavy processing where possible) Fixed a crash with the JTFE based missing files hotkey which no one seems to have used for an age for this to appear (maybe it's time to seriously consider stripping out features that aren't being used) Fixed how some of the file types which use extra information to reference their sub-songs is handled which was preventing some from being correctly resolved back to their base file (noticed fixing above) Fixed an issue with the handling of files with underscores in their filepath which wasn't being correctly handled causing some of the filename to be lost when shown as the title if title reading is delayed Fixed a few things that might be behind NotSoDirect not being stable for some setups though am still not certain that the changes done for this are going to fully resolve the problem from the crash reports Fixed the OS toast handling when there's no prior shortcut in the OS start menu to now create the shortcut (needed to allow the yes/no buttons for the new build / post-release toast) to be done as a hidden one so it's less likely to cause annoyance for those not wanting to see it whilst still allowing this less than ideal OS api implementation requirement to be met to avoid toasts without the needed buttons Fixed a regression when moving from taglib1 to taglib2 which broke some of the handling in place to allow for external programs to still access files when wacup has a held open cached instance of the file Everything else Updated cppwinrt (gen_win10shell.dll) to 3.0.260520.1 (26 May 2026) Updated libcurl (libcurl.dll) to 8.2.1 (24 Jun 2026) Updated Monkey's Audio (in_ape.dll) to 13.15 (28 Jun 2026) Updated mpg123 (mpg123.dll) to 1.33.6 (6 Jun 2026) Updated OpenSSL (libcurl.dll) to 3.5.7 (9 Jun 2026) Updated pugixml to 1.16 (16 Jun 2026) Updated taglib (tag2.dll) to 2.3.0 (11 May 2026) Updated vgmstream (in_vgmstream.dll) to the latest Git commit from 28 Jun 2026 Download: WACUP 64-bit | 9.6 MB (Freeware) Download: WACUP 32-bit View: WACUP Website | Screenshots Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Week One Done
      Collagen Project earned a badge
      Week One Done
    • Reacting Well
      Wakeen1966 earned a badge
      Reacting Well
    • Rookie
      Almohandis went up a rank
      Rookie
    • Apprentice
      jahara21 went up a rank
      Apprentice
    • Reacting Well
      NovaEdgeX earned a badge
      Reacting Well
  • Popular Contributors

    1. 1
      +primortal
      526
    2. 2
      +Edouard
      265
    3. 3
      PsYcHoKiLLa
      146
    4. 4
      Steven P.
      98
    5. 5
      macoman
      55
  • Tell a friend

    Love Neowin? Tell a friend!