No in Binary

"no" in binary is 01101110 01101111

2 bytes, 16 bits, one 8-bit ASCII code per character.

"no" is two letters and two bytes, sixteen binary digits, one of the shortest real messages you can send. And like yes, it has a one-bit rival: a computer's native no is a single 0, an unset bit. Programs answer millions of yes/no questions per second that way, without spelling anything. The full ASCII spelling exists for human eyes, when the word itself has to appear in a message or on a screen.

The two bytes hide a nice detail. The letters n and o sit next to each other in the alphabet, and ASCII numbers the alphabet consecutively, so the two bytes below are identical except for their final bit. A one-bit edit turns n into o.

There is also a trap worth knowing: the decimal codes for n and o are 110 and 111, digit strings that look exactly like binary but are not. If you feed "110 111" to a decoder as binary, you will not get "no" back. When a string of 1s and 0s shows up without context, check which base it claims before decoding; the binary translator can tell the difference for you.

Byte by byte

CharacterDecimalBinary
n11001101110
o11101101111

The same phrase in hex and decimal

Binary is not the only way to write the bytes. In hexadecimal, "no" is:

6E 6F

And as decimal byte values:

110 111

More words in binary

Browse the full collection at words in binary, or convert any text to binary with the translator.

FAQ

What is no in binary?

Lowercase "no" is 01101110 01101111: the byte for n followed by the byte for o, sixteen digits in total. The two letters sit next to each other in the alphabet, so their bytes are identical except for the very last bit.

Is 0 the same as no in binary?

In logic, yes: a single 0 bit is how a program stores a no answer. As text, no: the word itself is two full ASCII bytes, sixteen digits. The blank bit and the printed word are different layers of the same idea, and which one you need depends on who is reading.

Why do the decimal codes for no look like binary?

Coincidence. In decimal, n is code 110 and o is code 111, and those digits happen to use only 1s and 0s. Reading 110 as binary would give you six, not the letter n. It is a neat trap: always check which base a string claims to be in before decoding it.