Why Is It Called a Byte?

You have typed the word thousands of times. Every file size, every memory chip, every firmware image is measured in bytes, kilobytes, and megabytes. Yet almost nobody stops to ask a simple question: why is it called a byte, and why is it spelled with that odd "y" in the middle? The answer takes us back to 1956, to an IBM engineering team building one of the most ambitious computers of its era, and to a naming decision that still shapes how we design connected devices today.

Who coined the word byte?

The word byte was coined in July 1956 by Werner Buchholz, a German-born engineer working at IBM on the design of the Stretch, formally the IBM 7030. Stretch was IBM's attempt to build a supercomputer many times faster than anything before it, and the team needed a term for a group of bits handled as a single unit, typically the bits used to encode one character.

Buchholz deliberately spelled it "byte" rather than "bite." The reason was purely practical: in a world of memos, code listings, and hand-transcribed notes, "bite" was one careless typo away from "bit," and the two words meant very different things. Changing the vowel to a "y" made the new term visually distinct and typo-resistant. It is one of the earliest examples of an engineering team naming something with human error in mind, a habit good hardware and firmware teams still practice.

A byte was not always 8 bits

Here is the part that surprises most people. When Buchholz coined the term, a byte did not have a fixed size. On the Stretch, a byte could be anywhere from 1 to 8 bits depending on how the machine was configured. The word simply meant "the group of bits we operate on together," and different machines of the era used 6-bit, 7-bit, and 9-bit groupings.

The 8-bit byte only became the near-universal standard with the launch of the IBM System/360 in 1964. The System/360 was wildly successful, and its 8-bit byte, capable of encoding 256 distinct values, became the de facto unit that the rest of the computing industry adopted. To be precise, engineers often use the word octet for a group of exactly 8 bits, precisely because the term byte was historically ambiguous. When you see octet in a networking specification, that is the ghost of this old ambiguity.

Why this matters for IoT and embedded systems

This is not just trivia for the embedded and IoT world, it is the foundation of how we reason about every device we build. When we specify that a microcontroller has 320 KB of RAM or that an over-the-air firmware image must fit in 4 MB of flash, we are counting in the exact unit Buchholz named seventy years ago. On the resource-constrained hardware that powers most connected products, every byte is a budget line.

An ESP32 sensor node, a smart meter, or an industrial controller lives or dies by how carefully its firmware manages bytes. Buffer sizes, packet payloads, and memory maps all trace back to the humble 8-bit byte. A single MQTT message, a Modbus register, a sensor reading serialized for the cloud, each is measured and transmitted in bytes. Understanding that history sharpens the instinct to treat memory as the scarce, precious resource it genuinely is on embedded targets. If you want a deeper look at how we approach that discipline, our IoT and embedded services page walks through the process.

From a 1956 supercomputer to your pocket

There is a pleasing symmetry to it. The byte was born on a room-sized machine that cost millions and pushed the limits of 1950s engineering, and today the same unit describes the few kilobytes of RAM inside a chip that costs a couple of dollars and fits on a fingertip. The scale inverted completely, but the vocabulary held.

That continuity is part of why understanding tech history is useful rather than merely charming. The constraints that shaped early computing, scarce memory, careful naming, and a relentless focus on efficiency, are exactly the constraints that shape good IoT engineering now. At Fluidwire we build connected hardware and the web services behind it, from silicon to cloud, and we care about every byte along the way. If you have a product idea that needs to run lean on real hardware, get in touch and let us help you count them well.