Verification: factors follow standard unit definitions; round for display only.

Bits to bytes

Convert bit to B when a PHY datasheet, crypto parameter list, or channel-width spec quotes bits but your buffer allocator, file I/O layer, or storage dashboard expects byte-aligned quantities.

A bit (symbol bit, lowercase) is the smallest binary digit; a byte (symbol B, uppercase) groups exactly eight bits by universal definition. On this site's data-storage catalog, Bit: 1 and Byte: 8 in the base unit graph, so:

1 byte = exactly 8 bits  ·  therefore   bytes = bits ÷ 8

This is not an approximate constant — it is the definition used in networking standards, storage APIs, and hex dumps. Divide any bit count by 8 to get bytes; if the result is not a whole number, you are dealing with a non-byte-aligned field or partial word.

Step-by-step conversion (worked example)

Convert 8,192 bits to bytes — a common small-block size when reading specs in bits but allocating KiB buffers:

1. Write the formula: bytes = bits ÷ 8
2. Divide: 8,192 ÷ 8 = 1,024 bytes
3. Sanity check: 8,192 bit = 8 Kibit in binary counting; 1,024 B = 1 KiB — the factor of 8 applies at every scale.

Second worked example (128-bit key material)

Convert 128 bits — a UUID, AES-128 block, or 128-bit key fingerprint — to bytes:

1. 128 ÷ 8 = 16 bytes
2. Hex dumps show 16 byte pairs (32 hex digits), matching certificate thumbprints and UUID strings in tooling.

Third worked example (Ethernet MAC width)

Convert 48 bits — the width of an Ethernet MAC address — to bytes:

1. 48 ÷ 8 = 6 bytes
2. Packet captures list the same address as six colon-separated octets.

Quick mental estimate (no calculator)

Divide bits by 8, or halve three times. Example: 4,096 bit → 4,096 ÷ 8 = 512 B. Because 8 is a small integer, mental math stays exact when the bit count is divisible by 8 — unlike floating-point prefix conversions.

Bit to byte conversion chart

Where bits → bytes comes up

• Networking & framing: Line rates and channel widths are quoted in bits (Mbit/s, Gbit/s), while capture tools and socket buffers often size payloads in bytes. Convert bit-level specs to bytes before comparing with file sizes or disk quotas.
• Crypto & security: Key lengths and digest sizes are listed in bits (128, 256, 512), while HSM APIs and certificate stores track octet-aligned blobs in bytes — divide by 8 to align documentation.
• Embedded & firmware: Register maps label flag fields in bits; flash images and hex editors show byte-aligned addresses. Converting keeps datasheet and driver code consistent across teams.
• Storage procurement: SSD marketing may mix Gb (gigabits on the label) with GB (gigabytes in the OS). The bit↔byte factor of 8 is separate from decimal vs binary prefix steps — apply ÷8 when crossing bit and byte families.

Bytes to bits

Convert B to bit when a file size, disk quota, or memory footprint is quoted in bytes but you need the bit count for protocol framing, checksum math, or bandwidth budgeting.

Reverse the bit-to-byte process by multiplying bytes by 8. Both routes are equivalent because one byte is defined as exactly eight bits.

bits = bytes × 8  ·  equivalently   bits = bytes × 8 (exact integer)

Step-by-step conversion (worked example)

Convert 1,024 bytes to bits:

1. Multiply: 1,024 × 8 = 8,192 bits
2. Recognize: 1,024 B = 1 KiB; 8,192 bit = 8 Kibit at the same binary scale.

Second worked example (MTU payload)

Convert 1,500 bytes — a typical Ethernet MTU payload before headers:

1. 1,500 × 8 = 12,000 bits
2. At 100 Mbit/s (theoretical): 12,000 ÷ 100,000,000 ≈ 0.12 ms wire time for payload alone — headers add more.

Quick mental estimate (reverse direction)

Multiply bytes by 8. Example: 250 B → 250 × 8 = 2,000 bits. There is no rounding shortcut — the factor is exact.

Byte to bit conversion chart

Reverse conversion is essential when comparing file size in bytes against a link capacity quoted in Mbit/s or Gbit/s — convert to bits first, then divide by bit/s.

Binary literacy, Mbps vs MB/s, and related tools

The bit–byte factor is exact by definition. Keep notation explicit, distinguish storage from transfer rate, and verify with anchor values.

Bits vs bytes at a glance

Common mistakes to avoid

• Confusing b (bit) with B (byte) — lowercase b for bit, uppercase B for byte. A 50 Mb payload is not the same as 50 MB.
• Treating Mbit/s as MB/s — at the base level, 1 byte/s = 8 bit/s. A 100 Mbit/s link moves at most about 12.5 MB/s of payload before overhead.
• Assuming every bit count divides by 8 — serial streams and some codecs carry non-byte-aligned fields. A fractional byte signals misalignment, not a rounding error.
• Mixing decimal prefixes with binary KiB without stating which — the ×8 factor is unchanged; only kilo/mega/giga multipliers may differ by context.
• Forgetting protocol overhead — raw bits ÷ line rate gives a lower bound; TCP/IP, TLS, and retransmits add time beyond the naive calculation.

Related data-storage converters

For the inverse of this page, open bytes to bits. Nearby workflows: gigabit to megabit, kilobyte to megabyte, terabyte to gigabyte, and Mbit/s to Gbit/s for throughput rates.