{
  "slug": "byte",
  "term": "Byte",
  "aliases": [
    "Eight-bit byte",
    "Octet (eight-bit byte)"
  ],
  "definition": "A byte is a group of bits treated as one storage unit, conventionally eight bits in modern storage and networking.",
  "note": "Units: Modern storage capacity uses 1 B = 8 bits. An octet is explicitly an eight-bit group: its 256 patterns range from hexadecimal 00 to FF. Octet is an alias here only for the eight-bit usage of byte. [nist-units] [rfc-octet]\n\nC portability: The C11 draft defines a byte as an addressable storage unit, with implementation-defined width. CHAR_BIT gives its bit count and must be at least 8; sizeof(char) is 1, not a promise of eight bits. A serialized octet and a C byte therefore need not have the same width. [c11-byte]\n\nText: A byte count is not a character count. UTF-8 encodes one Unicode scalar value in one to four octets, excluding surrogate code points. For example, U+0041 occupies 41 in hexadecimal, while U+20AC occupies E2 82 AC. Count the encoded bytes when sizing a text payload. [rfc-utf8]",
  "status": "unknown",
  "advantages": [],
  "limitations": [],
  "supersedes": [],
  "supersededBy": [],
  "firstSeen": null,
  "lastSeen": null,
  "updated": "2026-11-17",
  "related": [
    "bit",
    "binary-prefix",
    "byte-order",
    "file-size",
    "character-encoding",
    "utf-8",
    "unicode-normalization",
    "hexadecimal"
  ],
  "citations": [
    {
      "id": "nist-units",
      "title": "NIST: Prefixes for binary multiples, unit examples",
      "url": "https://physics.nist.gov/cuu/Units/binary.html",
      "accessed": "2026-11-17"
    },
    {
      "id": "c11-byte",
      "title": "WG14 N1570, C11 committee draft: sections 3.5-3.6, 5.2.4.2.1 and 6.5.3.4",
      "url": "https://www.open-std.org/jtc1/sc22/wg14/www/docs/n1570.pdf",
      "accessed": "2026-11-17"
    },
    {
      "id": "rfc-octet",
      "title": "RFC 5234: Appendix B.1, OCTET core rule",
      "url": "https://www.rfc-editor.org/rfc/rfc5234.html#appendix-B.1",
      "accessed": "2026-11-17"
    },
    {
      "id": "rfc-utf8",
      "title": "RFC 3629: section 3, UTF-8 definition",
      "url": "https://www.rfc-editor.org/rfc/rfc3629.html#section-3",
      "accessed": "2026-11-17"
    }
  ],
  "provenance": [
    "The C-specific statement is scoped to the April 2011 N1570 committee draft. UTF-8 examples describe encoding, not filesystem allocation."
  ]
}
