Baud rate is the number of signal changes (called symbols) transmitted per second over a communication channel. It’s measured in “baud,” and it determines how fast two devices can exchange data over a serial connection. If you’ve encountered the term while setting up a microcontroller, configuring a serial port, or working with embedded electronics, you’re dealing with one of the most fundamental settings in digital communication.
Baud Rate vs. Bit Rate
Baud rate and bit rate are related but not the same thing. Bit rate measures how many individual bits (1s and 0s) travel across a connection each second. Baud rate measures how many symbols travel per second. A symbol is a single signal change, and depending on the system, one symbol can carry one bit or several bits at once.
In the simplest systems, each symbol represents exactly one bit. A signal is either high or low, on or off. In that case, baud rate and bit rate are identical: 9600 baud equals 9600 bits per second. This is how most basic serial connections work, which is why the two terms are often used interchangeably in everyday electronics work.
The distinction matters in more advanced systems that use modulation techniques to pack multiple bits into each symbol. Instead of just switching between two signal states, these systems use variations in signal strength, timing, or phase to create many possible symbols. Each symbol then encodes several bits at once. The formula is straightforward:
Bit Rate = Baud Rate × Bits per Symbol
So a system running at 1,000 baud where each symbol carries 4 bits achieves a bit rate of 4,000 bits per second. The signal only changes 1,000 times per second, but each change carries four times as much information.
How Modulation Multiplies Data
Modern communication systems exploit this relationship heavily. A technique called Quadrature Amplitude Modulation (QAM) combines changes in signal strength and phase to create large sets of distinct symbols. In a 16-QAM system, there are 16 possible symbols, each encoding 4 bits. In 64-QAM, there are 64 symbols encoding 6 bits each. And 256-QAM pushes it to 256 symbols, encoding 8 bits per symbol, achieving twice the data rate of 16-QAM at the same baud rate.
This is how technologies like Wi-Fi and cable internet deliver high speeds without requiring impossibly fast signal switching. The baud rate stays manageable while the bit rate climbs by cramming more information into each symbol. The tradeoff is that denser symbol sets require cleaner signals. A noisy connection that handles 16-QAM fine may produce errors at 256-QAM because the receiver can’t reliably distinguish between symbols that are very similar to each other.
Common Baud Rates in Serial Communication
If you’re working with serial devices like Arduino boards, sensors, GPS modules, or data loggers, you’ll encounter a standard set of baud rates: 110, 300, 600, 1200, 2400, 4800, 9600, 14400, 19200, 38400, 57600, 115200, 128000, and 256000 bits per second. These are simple binary systems where one symbol equals one bit, so the baud rate and bit rate values are the same.
The most common default is 9600 baud. It’s slow by modern standards but extremely reliable, which is why it remains the go-to for basic serial communication. When speed matters more, 115200 baud is a popular choice for microcontroller projects and debugging consoles. Higher rates like 256000 baud are available but less commonly used because they’re more sensitive to connection quality.
Why Matching Baud Rates Matters
Both devices on a serial connection must be set to the same baud rate. If they aren’t, the receiving device will sample the incoming signal at the wrong intervals and interpret the data incorrectly. The result is garbled text, random characters, or no readable output at all. If you’ve ever opened a serial monitor and seen a stream of nonsense characters, a baud rate mismatch is one of the most likely causes.
This is a common stumbling block when connecting to devices that have been previously configured. For example, if someone connects to a data logger at 9600 baud and the device adjusts its rate to match, you may have trouble reconnecting later at 115200 because the device’s auto-detection doesn’t always scale back up reliably. When in doubt, start at 9600 and work up.
Cable Length and Speed Limits
Higher baud rates require shorter cables. This is a physical constraint: as signals travel longer distances, they degrade and pick up noise, making it harder for the receiver to accurately read fast symbol changes. The limits depend on the communication standard you’re using.
For RS-232, the classic serial standard found on older computers and industrial equipment, the typical maximum cable length is about 50 feet (15 meters) at 19200 baud. RS-485, a more robust standard designed for longer runs, can reach 4,000 feet (1,200 meters) at 9600 baud. But push the speed to 115200 bps and the maximum drops to around 1,200 feet (400 meters). At 1 Mbps, you’re limited to roughly 400 feet (120 meters).
If your project requires both long distances and high speeds, you’ll likely need to switch to a different protocol entirely, such as Ethernet, or add signal repeaters along the cable run.
Choosing the Right Baud Rate
For most hobbyist and prototyping work, 9600 baud is fine. It’s universally supported, forgiving of mediocre wiring, and fast enough for sensor readings, status messages, and basic data logging. If you’re streaming larger amounts of data, such as audio samples or high-frequency sensor data, jump to 115200 baud or higher.
The key factors to consider are how much data you need to move per second, how long your cable runs are, and whether both devices reliably support the rate you choose. Faster isn’t always better if it introduces errors. A stable connection at a moderate baud rate will outperform a flaky connection at a high one every time.