Ethernet Frame Size Calculator – Complete Layer-2 Frame Analysis
The Ethernet Frame Size Calculator breaks down an Ethernet frame into every structural field and computes the exact byte count at both the frame level and the wire level. Whether you are a network engineer verifying MTU compliance, a student learning Layer-2 fundamentals, or an IT professional troubleshooting fragmentation, this tool gives you an instant, precise view of how your payload translates into bytes on the wire.
Anatomy of an Ethernet Frame
An Ethernet frame is not simply payload wrapped in a header — it is a carefully structured sequence of fields that together enable reliable delivery on a shared-medium network. The two most common formats are Ethernet II (used by IP, ARP, and virtually all modern protocols) and IEEE 802.3 (the original standard, still used with legacy LLC and SNAP encapsulation). The table below shows the byte contribution of each field in a standard Ethernet II frame:
| Field | Bytes | Notes |
|---|---|---|
| Preamble | 7 | Alternating 1s/0s for clock synchronization |
| Start Frame Delimiter (SFD) | 1 | 0xAB — marks the start of the frame |
| Destination MAC | 6 | Layer-2 address of the destination NIC |
| Source MAC | 6 | Layer-2 address of the sending NIC |
| EtherType | 2 | Protocol identifier (e.g. 0x0800 = IPv4, 0x86DD = IPv6) |
| Payload (Data + Padding) | 46–1500 | Application data; padded to 46 bytes minimum |
| Frame Check Sequence (FCS) | 4 | CRC-32 checksum for error detection |
| Inter-Frame Gap (IFG) | 12 | Mandatory idle time between frames (wire-level only) |
The frame size spans from the destination MAC through the FCS (14 + payload + 4 = payload + 18 bytes for untagged Ethernet II). The wire size adds preamble, SFD, and IFG, representing what actually occupies bandwidth on the physical medium.
Minimum Frame Size and Automatic Padding
IEEE 802.3 mandates a minimum frame size of 64 bytes (excluding preamble, SFD, and IFG). This requirement exists so that collision detection (CSMA/CD) works correctly — a frame shorter than 64 bytes would complete transmission before the collision signal could propagate back to the sender.
For an untagged Ethernet II frame, the fixed overhead is 18 bytes (6 + 6 + 2 + 4), leaving a minimum payload of 46 bytes. If your application data is shorter, zero-padding is added automatically. The calculator detects this situation, shows exactly how many padding bytes were added, and flags the result so you can factor it into your network design.
VLAN Tagging: 802.1Q and QinQ
VLAN tagging inserts additional 4-byte fields between the source MAC address and the EtherType field. A single 802.1Q tag raises the frame overhead by 4 bytes, pushing the maximum valid frame size from 1518 to 1522 bytes. A QinQ (802.1ad) double-tagged frame adds 8 bytes total, reaching 1526 bytes — exceeding the standard 1518-byte Ethernet MTU and requiring explicit MTU adjustments on all transit switches and routers.
Jumbo Frames and Data-Center Use Cases
Standard Ethernet limits payload to 1500 bytes. Jumbo frames extend this to 9000 bytes, reducing the number of frames needed to transfer large volumes of data and cutting CPU interrupt overhead significantly. Jumbo frames are standard in data-center environments running iSCSI, NFS, FCoE, or VMware vMotion, where every percentage point of CPU efficiency matters. All switches, routers, and NICs on the path must be configured to the same jumbo MTU; a single non-jumbo device will silently drop or fragment oversized frames.
Payload Efficiency
Payload efficiency measures how much of the total wire bandwidth carries useful application data: efficiency = payload ÷ wire_size × 100. For a full 1500-byte payload in an untagged Ethernet II frame with preamble and IFG, efficiency is approximately 97.4%. Small frames are far less efficient — a 46-byte minimum payload frame achieves only about 54.8% efficiency because the 42-byte fixed overhead dominates. This metric is critical for sizing links in latency-sensitive or high-throughput applications.
IEEE 802.3 LLC and SNAP Overhead
Older IEEE 802.3 frames use a 2-byte length field (instead of the Ethernet II EtherType) combined with a 3-byte LLC header (DSAP + SSAP + Control). When a 5-byte SNAP extension is added (OUI + Protocol ID), the overhead grows by an additional 5 bytes. These legacy formats are still encountered in STP (Spanning Tree Protocol) BPDUs, NetBIOS frames, and some industrial protocols. The calculator handles all three variants so you can accurately size frames in mixed-format environments.
Practical Applications
Use this calculator to verify frame sizes before configuring MTU values on switches and routers, to confirm that VLAN-tagged frames stay within your infrastructure's MTU budget, and to quantify the overhead cost of different tagging schemes. It is equally useful as a teaching aid for networking fundamentals courses, providing an interactive, visual decomposition of every byte in a real Ethernet frame.