# Bytefield examples

Byte field diagrams are the reason binary format specifications are readable. Bytefield draws them from a short description, so the offsets cannot drift.

Five examples, from the canonical TCP header to a nested structure.

---

## Every example here is real

Each page holds a diagram that is stored, rendered and editable exactly like one you drew yourself. Open any of them, change something, and see what happens. Nothing here is a screenshot.

---

## In this set

[TCP header (Bytefield)The TCP header drawn field by field, including flags and the options region.](https://help.gocapable.com/diagrams/tcp-header-bytefield.html)[Protocol header (Bytefield)A custom protocol header with column headers and named byte spans.](https://help.gocapable.com/diagrams/protocol-header-bytefield.html)[Memory layout (Bytefield)A memory map showing regions, offsets and sizes as a single diagram.](https://help.gocapable.com/diagrams/memory-layout-bytefield.html)[Nested structure (Bytefield)Show a struct inside a struct, using gaps and boxes to nest one layout in another.](https://help.gocapable.com/diagrams/nested-structure-bytefield.html)

---

## Related

[ReferenceThe language reference behind these.](https://help.gocapable.com/diagrams/reference.html)

[Diagram typesGrouped by what you want to draw.](https://help.gocapable.com/diagrams/diagram-types.html)

[ExamplesEvery other set.](https://help.gocapable.com/diagrams/examples.html)

---

_The offsets are computed, not drawn._