Manchester Code Named IEEE Milestone

In the late 1940s, as computer engineers struggled with unreliable hardware and noisy transmission environments, a team of engineers in a modest laboratory at the University of Manchester, England, faced a problem so fundamental that it threatened the viability of digital computing itself. Machines could generate bits, but they couldn’t reliably read them back.

The incoherent rereading of memory data did not initially present itself as a great theoretical challenge. This manifested itself as something more mundane: inconsistent computer results.

Engineers including Frederic C. Williams, Tom Kilburn, and GE (Tommy) Thomas attributed the failures not to logical errors but to the physical behavior of the machines themselves. The team developed a technique to keep a transmitter and receiver in sync without relying on a separate clock signal. Their innovation, known as Manchester Code Or phase codingencoded each bit with a transition in the middle of the bit period, effectively integrating the timing information directly into the data stream to constitute a self-timing signal. So even if the signal degraded or the timing drifted slightly, the receiver could continually keep time based on these regular transitions.

By eliminating the need for separate clocks and reducing timing errors, the Manchester code made data transfer more robust between cables and circuits.

These qualities then made it a natural choice for technologies such as Ethernet and early data storage systems. Its self-synchronizing nature helped standardize the way machines communicate and laid the foundation for modern networking and digital communication protocols.

On April 13, 2026, this major breakthrough was honored with an IEEE Milestone plaque during a ceremony at the University of Manchester. Dignitaries from IEEE and the university attended the ceremony.

Integrating timing into signals

These University of Manchester engineers from the 1940s worked on systems that powered the Manchester Mark I, one of the first practical stored-program machines.

When problems arose, they used oscilloscopes to probe the signals. They found that the electrical impulses did not arrive at a consistent rate. The memory signals also faded over time, making them harder to read, and when long sequences of identical bits occurred, the waveform flattened into stretches without transitions.

This led to a crucial insight: The problem wasn’t just detecting whether a signal was high or low; the system also lost track of when to sample the signal. Without reliable timing markers, even correctly formed signals were misinterpreted. Bits could actually be lost or miscounted because the system was no longer in sync.

At first, engineers tried to tame the hardware. They experimented with stabilizing circuits and more coherent pulse generation, attempting to impose a steady rhythm on an inherently unstable system. But the fixes proved fragile and the electronics of the time could not maintain the required precision. The Manchester group therefore took a different approach.

If the hardware couldn’t provide a reliable clock, the signal itself would have to carry one. Instead of representing data as static levels, each bit changed state, with a guaranteed transition in the middle.

Incorporating timing into the signal reduced erratic behavior. Machines were suddenly able to reliably transmit, store, and replay data, an essential step toward practical stored-program computing.

Make signals unmistakable

Manchester’s code addressed several issues at once. Regular transitions allowed for continued recovery of timing. Transitions were found to be easier to detect than static levels, and long sequences of identical bits no longer produced flat, ambiguous waveforms. Rather than fighting the imperfections of early electronic devices, the design worked with them.

From laboratory curiosity to a global standard

What started as a local solution in Manchester shaped digital communications systems for decades, including early Ethernet technologies, for which synchronization and shared media communication were central challenges.

According to Robert Metcalfe, a member of the team that built the first Ethernet system at Xerox PARC in 1973, he and his colleagues relied on the Manchester code.

“The Manchester code solved a fundamental problem for us: timing,” says Metcalfe, explaining that each bit carried its own clock and eliminated the need for a global synchronized signal.

This self-clocking property was not the only advantage provided by the coding scheme. On shared coaxial cable, Manchester coding did more than provide synchronization. Each transceiver left the medium undriven – effectively “turned off” – most of the time, allowing packets from other machines to pass through without interference. Even during transmission, a station only transmitted the signal about half the time, leaving the line unused for the other half of each bit cycle.

This distinction – between a driven signal and an undriven line, rather than simple 1s and 0s – allowed receivers to retrieve both data and clock timing while monitoring the cable for other activity. If a transceiver detected a signal when it expected the line to be undriven, the signal indicated that another station was transmitting at the same time. In other words, the system could detect collisions in real time and react accordingly.

The idea has proven itself well beyond local networks. The Manchester code is used aboard the Voyager spacecraft, which now navigates interstellar space, highlighting its reliability in extreme environments.

The code has also found its way into everyday consumer electronics. Infrared remote controls for televisions and audio equipment typically rely on Manchester Code through protocols such as RC-5, developed by Philips in the early 1980s. The protocol encodes commands as timed infrared signals transmitted through a handset’s integrated circuit and LED, allowing devices to reliably interpret button presses, even in the face of noise and signal distortion. Manufacturers across Europe – and many in the United States – have adopted this approach, extending the Manchester Code to the home.

Why the milestone is important

An IEEE Milestone designation recognizes technologies with lasting impact. Manchester’s code qualifies because it solved a fundamental timing problem at a critical moment in computing history.

Without a way to embed timing into the data itself, early digital systems would have remained fragile and unreliable. The Manchester Code helped turn them into reliable machines and enabled much of today’s digital communication.

“The Manchester Code solved a fundamental problem for us: timing” —Robert Metcalfe, an inventor of Ethernet

Key attendees at the plaque dedication ceremony included Tom Coughlinm, IEEE 2024 President; Duncan Ivison, President and Vice-Chancellor of the University of Manchester, and Nagham Saeed, Chair of the IEEE UK and Ireland Section.

Presentations by Kees Schouhamer Immink (2017 IEEE Medal of Honor winner, probably best known for his work making compact discs and other high-density digital media practical) and Peter Green (assistant dean of the Manchester School of Engineering) highlighted the lasting impact of code on digital data storage and communications.

The IEEE Milestone plaque for the Manchester Code reads:

“HAS At this site in 1948-1949, Manchester Code was invented to reliably encode digital data stored on the magnetic drum of the Manchester Mark I computer. It became a standard for magnetic tapes and computer floppy disks and was used in digital communications, notably in the Voyager 1 and 2 spacecraft and in early Ethernet networks. It has been widely used in home remote controls, radio frequency identification (RFID) tags and many control network standards..”

Administered by the IEEE History Center and supported by donors, the Milestone program recognizes outstanding technical developments around the world. The IEEE UK and Ireland Section sponsored the nomination.