A Number That Sounded Like a Fact
The bit count of a console's processor is a real technical property. It describes, roughly, the width of the data the CPU handles in one operation. It is also, as a predictor of whether games will be good or even whether they will look good, close to worthless — a fact the industry understood perfectly and concealed with enthusiasm for over a decade.
The appeal of the number to marketers was that it was simple, it was quantitative, and it sounded like a fact rather than a claim. Sixteen is twice eight. Thirty-two is twice sixteen. A consumer standing in a shop with no way to evaluate architecture, memory bandwidth, or graphics hardware could grasp instantly that a larger number was better, and the industry spent ten years ensuring they never learned otherwise.
The reality was messier at every turn. The Super Nintendo's CPU ran at 3.58 MHz against the Genesis's 7.67 MHz, which sounds decisive until you notice that the SNES had a vastly more capable graphics chip, better colour, and hardware scaling and rotation the Genesis could not touch. Neither machine was simply "better." Both were 16-bit. The number explained nothing.
Blast Processing
Sega's answer to this ambiguity was one of the great marketing coinages in the history of the medium, and its origins are more honest than its use. Sega of America's Marty Franz discovered a genuine technique that allowed developers to push data onto the Genesis graphics chip while a scanline was actively being drawn, exploiting the DMA unit's bandwidth to change the colour palette mid-scanline. His colleague Scott Bayliss gave it a name: Blast Processing.
As an engineering term for an obscure DMA trick, it was fine. As a marketing weapon, it was devastating — and completely untethered from what it originally described. Sega's advertising deployed "Blast Processing" not as a specific capability but as a vague, thrilling assertion that the Genesis was simply faster, and consumers, who had no idea what the phrase had ever meant, accepted it as a technical fact about the hardware.
The blowback was inevitable. Because almost nobody knew what the term had originally referred to, Nintendo was later able to dismiss Blast Processing as a pure myth with no basis whatsoever — a rebuttal that was itself misleading, since the underlying technique was real. The truth, awkwardly, sat in the middle, which is precisely where marketing arguments go to die. The man who coined the phrase has since publicly apologised for creating "that ghastly phrase."
The Arms Race Eats Itself
Once bits became the axis of competition, escalation was the only strategy available. The 16-bit generation gave way to a scramble for 32, and the claims grew increasingly desperate and increasingly meaningless. Sega's 32X bolted two 32-bit processors onto a 16-bit console specifically so the box could say 32; the Sega CD, the 32X, and the Saturn coexisted in the market simultaneously, fragmenting Sega's message and its customers.
The absurdity peaked with the Atari Jaguar, marketed relentlessly as "the world's first 64-bit interactive multimedia system." The claim was arrived at by counting the width of a bus rather than the CPU, an accounting exercise designed to produce a bigger number than anyone else could claim. The Jaguar was not meaningfully more powerful than its 32-bit rivals; it had a bewildering multi-processor architecture that developers struggled to program, a controller with a numeric keypad and three face buttons, and a game library that never materialised. It sold catastrophically.
The Jaguar is the perfect endpoint of the bit wars because it demonstrates the whole logic collapsing: a console that won the number and lost everything else. Nintendo, meanwhile, put 64 in the actual name of its console — a final, cheerful admission that the number had become the product.
What Replaced It
The bit wars ended not because consumers grew sophisticated but because the number stopped scaling usefully. Once processors moved past 64-bit, the figure ceased to be a differentiator, and the industry needed a new axis. It found several: polygons per second, then resolution, then frame rate, then teraflops. Each has been deployed in exactly the same way — a single quantitative claim, technically real, presented as though it settled a question it does not actually address.
It is worth being clear about what the bit wars actually were. They were not a technical debate that consumers happened to misunderstand. They were a deliberate strategy of substituting a legible number for an illegible reality, because the real question — which console has the better games, the better development tools, the better architecture for what developers actually want to do — cannot be printed on a box.
The most instructive fact in the whole saga is that the SNES and the Genesis, the two machines whose rivalry the bit wars were invented to adjudicate, were both 16-bit, both excellent, and both produced masterpieces the other could not have run. The number never had an answer. It just had a bigger version.