Half duplex is a communication mode where two devices can both send and receive data, but only one can transmit at a time. Think of it like a walkie-talkie: you press the button to talk, release it to listen, and your conversation partner does the same. Data flows in both directions, just never simultaneously.
How Half Duplex Works
In a half-duplex system, both devices share a single communication channel. While one device is transmitting, the other stays silent and listens. Once the transmission finishes, the roles can reverse, and the device that was listening can now send its own data back. This back-and-forth swap is called “line turnaround,” and the time it takes to switch roles is the line turnaround time.
The key limitation is that shared single channel. Because only one device can use it at any given moment, half-duplex systems are inherently slower than setups where both sides can talk at once. But they’re also simpler and cheaper to build, since they need fewer wires or radio frequencies to operate.
Half Duplex vs. Simplex vs. Full Duplex
Communication systems fall into three categories based on how data flows between devices:
- Simplex is one-way only. Data travels in a single direction, and the receiving device can never send anything back. A keyboard sending keystrokes to a computer is simplex: the keyboard transmits, the computer receives, and that’s it.
- Half duplex is two-way, but one direction at a time. Both sides can send and receive, just not simultaneously. Walkie-talkies are the classic example.
- Full duplex is two-way and simultaneous. Both devices send and receive at the same time, the way a phone call works. You can talk while the other person is also talking, and both voices travel through the line at once.
Full duplex effectively doubles the potential throughput of a connection compared to half duplex, since the channel (or channels) carry data in both directions simultaneously. The tradeoff is that full-duplex systems typically require either two separate channels or more sophisticated hardware to keep the two data streams from interfering with each other.
Everyday Examples of Half Duplex
The walkie-talkie is the most intuitive example. You hold the push-to-talk button, say your message, then release it so the other person can respond. If both people try to transmit at the same time, neither message gets through clearly.
Wi-Fi is a less obvious but far more common example. Standard Wi-Fi (the IEEE 802.11 protocol) operates over a half-duplex channel. Your laptop and your router take turns sending and receiving data on the same radio frequency. They can’t do both at the same time. This is one reason wired Ethernet connections often feel snappier than wireless ones for tasks like video calls or online gaming, where data needs to flow rapidly in both directions.
To manage the fact that multiple Wi-Fi devices share the same airspace, the protocol uses a system called Carrier Sense Multiple Access with Collision Avoidance (CSMA/CA). Each device listens to the channel before transmitting. If the channel is busy, the device waits. If two devices happen to transmit at the same moment and their signals collide, they each back off for a random amount of time before trying again.
Half Duplex in Networking History
If you’ve been around computers long enough to remember network hubs, you’ve used half-duplex networking. Hubs operated in half-duplex mode: every device connected to a hub shared the same communication path, so only one device could send data at a time. When two devices tried to transmit simultaneously, a collision occurred, and both had to stop and retry. As networks grew and more devices were added, collisions became frequent and performance suffered.
Network switches replaced hubs and brought full-duplex support. A switch creates a dedicated connection between each pair of communicating devices, so data can flow in both directions at once without collisions. This change alone dramatically improved network speed. Today, hubs are considered outdated and are rarely used. Modern wired networks run almost entirely on switches operating in full-duplex mode.
Industrial and Hardware Uses
Half duplex remains common in industrial settings where simplicity and low cost matter more than raw speed. A widely used example is RS-485, a standard for wired communication in factories, building automation systems, and other industrial environments. In its half-duplex configuration, RS-485 needs just two wires to connect devices, which keeps cabling simple and affordable over long cable runs. These two-wire setups are popular in systems like Modbus, a protocol used to let sensors, controllers, and other equipment exchange data on a factory floor.
Half duplex also appears in hardware-level communication protocols inside electronic devices. The I2C protocol, used to connect components on a circuit board (like a sensor talking to a microprocessor), is inherently half duplex. It uses a single data line that devices take turns using. Some variants of SPI, another common hardware protocol, also operate in half-duplex mode, though the standard version of SPI is full duplex.
Why Half Duplex Still Matters
Half duplex persists because it solves a real engineering problem: how do you let two devices communicate when you only have one shared channel? Running a second channel costs money, whether that means extra wires, extra radio spectrum, or more complex hardware. In situations where the data doesn’t need to flow in both directions at exactly the same time, half duplex delivers reliable two-way communication with less infrastructure.
Wi-Fi is the clearest proof that half duplex isn’t obsolete. Billions of devices use it daily, and for most tasks, the line turnaround happens so quickly you never notice the back-and-forth switching. The performance ceiling is lower than full duplex, but the convenience of a single shared wireless channel makes the tradeoff worthwhile for the vast majority of everyday use.