Bits, bytes, nibbles, and octets are the fundamental units of digital data, each serving distinct roles depending on whether data is being stored or transmitted. Understanding how and when each unit is used—along with the difference between bits-per-second and bytes-per-second measurements—is essential for working with networking and storage technologies.
Bits, Bytes, Nibbles & Octets
There's a couple pieces of terminology that we need to make sure that we understand, not to mention how we apply these is going to be dependent on what we're using it for. So let's take a look at what bits, bytes, nibbles and octets are.
A bit is the simplest form. It's either a one or a zero. However, usually a bit doesn't sit by itself. Occasionally it does — if we want to turn something on or off, we say an on is a one and off is a zero, and we call that a flag. There's flags that we'll say, hey, we want this turned on or off. But usually it's not just a bit; usually it comes in a series of bits that represent something.
A lot of times that series of bits is eight bits, and so we call that a byte. And so this is obviously a really common term that we use out there, a byte of data. Now we also will refer to it as an octet. So for instance, when we're talking about IP addresses, that's an octet — OCT being eight — and it's a series of eight bits, so it's an octet.
Now there are times when a byte is too much data, or it represents too much, and so we'll actually break it down into a smaller component. We call that a nibble. So a nibble is four bits. It's just half of a byte.
But what's interesting is sometimes we use bits to measure things and sometimes we use bytes to measure things. For instance, when we're talking about transmission speeds, most of the time that's considered as bits per second, the number of bits per second. So we measure speed in bits per second. But when we're talking about storage, we're measuring it in bytes.
So why do we measure storage in bytes? Well, the reason is because storage is usually in blocks of data, and lots of times we're storing large amounts of data. So bits is just a little too granular for that, and we usually group things up in bytes. So that's why we measure storage in bytes. So if you're talking about some sort of removable media or disk space, then those are measured in bytes.
So why do we measure speed in bits? Well, for a couple reasons. Number one is we just have a stream of bits that are coming in. Usually we have a serial interface as what we interface with other things, and so that is just a stream of bits at just one at a time. So it's pretty easy to measure that a bit at a time to figure out what our speed is. But the other reason is a lot of these bits — every so often there's these parity bits, or there's overhead — and so we have to factor that into our speeds. It's not just as simple as, oh well, I have a 100 megabyte file and I'm downloading at this speed, so I can easily figure out how long that's going to take. It doesn't quite work that way because of all of the overhead.
Here I'm on my demo laptop, and I just want to show you a type of connection on this demo laptop. It's called a serial connection, and I'm going to open up PuTTY and I'm going to go to this serial connection. So what this is, is a connection to a device, and you have some settings. The B is the speed right here. And what I wanted to show you is the data bits. So the data bits is eight, so that's a byte. So that makes sense. I mean, that measures up with what I'm talking about, where a lot of times we group things up in bytes. And so these data bits is 8, so it'll send eight bits over at the same time.
However, it has this stop bit of one, and we can change it. The reason why it's set up this way is because we could actually change this, so we could add more stop bits, or we could actually add some parity bits to this. And so the reason why I'm showing you this is just to show you that it's not as simple as, okay, well let's just measure how many bytes there are, because we add extra bits to that byte when it comes to our speed and our transmitting these bytes.
So how can we tell something's using bytes or bits? Well, it is the difference between a big B and a little b. The little b is bits. So in the measurement of, like, speed of a transmission, that's usually bits per second, so we see a little b on here, bits per second. And then with storage, that's usually measured in bytes, so that's a big B to represent that.
Now transmission speed is not always in bits, so you do have to watch out for this, because there is a difference between little b bps and big B Bps. And where we see a difference with this is like transmission speed of connections to the internet is usually bits per second, but when we're dealing with something like storage we might see bytes per second. So depending on what type of connection — a lot of our computer connections, when it's transferring data, is in bytes per second rather than bits per second.
Here's a Wikipedia article talking about data rate units. And so if we scroll down on here, we're going to see some common technologies and the measurements of them. And at the top here, here's a lot of networking that we see here, so a lot of different types of networking technologies. And if you notice here, a lot of these have little b's to them, so that's an example of that, bits per second. And so if we scroll further down, now we see things like FireWire and parallel, and these are SATA 2. These are things that are more built for like storage, and so now we see most of these are big B. Not all of them: here we have USB 3.1 and this says gigabit per second, versus USB 3 — let's see, where is the 2.0 — is megabytes per second. So we see some differences here.
So I just wanted to point this out, because you've got to be a little bit careful with whether it's a big B or a little b when it comes to the measurement.
TechKnowSurge builds IT and cybersecurity professionals through hands-on, concept-first training built around real understanding — not memorization. Free interactive tools, structured programs, and 25+ years of real-world experience, all in one place.
Explore free tools and programs →