Ethernet Frame Size Calculator

Calculate the total Ethernet frame size including all headers, trailers, VLAN tags, and overhead. Understanding frame sizes is critical for troubleshooting MTU issues, configuring jumbo frames, and optimizing network throughput on LANs and data center networks.

Payload Size (bytes) Min: 46, Max: 9000 (jumbo)

VLAN Tags

Include Preamble + SFD?

Include Interframe Gap?

Figure 1 — Ethernet Frame Size Calculator

Anatomy of an Ethernet Frame

An Ethernet II frame (the standard used in virtually all modern networks) consists of several fields. The frame as seen by the Ethernet NIC starts with the destination MAC address and ends with the Frame Check Sequence (FCS). However, the physical layer adds a preamble and start-of-frame delimiter before the frame, and an interframe gap after it.

Field	Size (bytes)	Description
Preamble	7	Alternating 10101010 pattern for clock synchronization
Start of Frame Delimiter (SFD)	1	10101011 — signals the start of the actual frame
Destination MAC	6	Recipient hardware address
Source MAC	6	Sender hardware address
802.1Q VLAN Tag (optional)	4	VLAN ID and priority (if tagged)
EtherType / Length	2	Identifies the upper-layer protocol (0x0800 = IPv4)
Payload	46-1500	IP packet + data (minimum 46 bytes, padded if shorter)
Frame Check Sequence (FCS)	4	CRC-32 error detection checksum
Interframe Gap (IFG)	12	Minimum idle time between frames on the wire

Pro Tip: When calculating network throughput, include the preamble (8 bytes) and interframe gap (12 bytes) in your overhead calculations. A 1500-byte payload actually requires 1538 bytes on the wire (14 header + 4 FCS + 8 preamble + 12 IFG), meaning the maximum efficiency for standard Ethernet is about 97.5% at maximum payload, but drops significantly for small packets.

Standard vs Jumbo Frames

Standard Ethernet frames have a Maximum Transmission Unit (MTU) of 1500 bytes for the payload. Jumbo frames extend this to 9000 bytes (or more, depending on the switch and NIC). Jumbo frames reduce per-packet overhead and improve throughput for large data transfers, especially in data centers and storage networks (iSCSI, NFS).

Frame Type	MTU (bytes)	Total On-Wire	Overhead %	Use Case
Standard Ethernet	1500	1538	2.5%	General networking, internet
Baby Jumbo	1600	1638	2.4%	MPLS, PPPoE overhead
Jumbo Frame	9000	9038	0.4%	Data centers, storage networks
Minimum Frame	46	84	45.2%	ARP, small ACKs (padded)

VLAN Tagging and Frame Size

When 802.1Q VLAN tagging is used, a 4-byte tag is inserted between the source MAC address and the EtherType field. This increases the minimum frame size from 64 to 68 bytes and the maximum from 1518 to 1522 bytes. For Q-in-Q (double tagging, used by service providers), two 4-byte tags are inserted, adding 8 bytes total.

VLAN tagging is configured on managed switches. If your network uses VLANs, ensure that all switches in the path support the frame size. Some older switches may drop frames larger than 1518 bytes even with a single VLAN tag. See our guide on how to set up VLANs for configuration details.

MTU and Fragmentation

If a packet exceeds the MTU of a link, it must be fragmented into smaller pieces or dropped (if the Don't Fragment flag is set). Fragmentation reduces performance because each fragment requires its own headers, and the receiving host must reassemble them. Modern networks set the DF flag and use Path MTU Discovery (PMTUD) to determine the optimal packet size.

Common MTU issues arise when VPN tunnels, PPPoE connections, or MPLS labels add overhead to packets. A standard 1500-byte payload inside a VPN tunnel may exceed the underlying link's MTU, causing fragmentation or drops. The solution is to reduce the MTU on the tunnel interface (typically to 1400-1460 bytes) or enable MSS clamping.

Pro Tip: To test the MTU on a network path, use ping with the Don't Fragment flag: ping -f -l 1472 8.8.8.8 on Windows or ping -M do -s 1472 8.8.8.8 on Linux. Start with 1472 (1500 MTU minus 20 IP header minus 8 ICMP header) and decrease until the ping succeeds. The Packet Size Calculator can help you determine the exact overhead.

Ethernet Efficiency by Payload Size

Payload (bytes)	On-Wire (bytes)	Overhead (bytes)	Efficiency	Typical Traffic
46 (minimum)	84	38	54.8%	ARP, TCP ACKs
64	102	38	62.7%	DNS queries
576	614	38	93.8%	Legacy minimum MTU
1460	1498	38	97.5%	TCP over IPv4 (MSS default)
1500	1538	38	97.5%	Maximum standard payload
9000	9038	38	99.6%	Jumbo frames

Checking and Configuring MTU

Windows

netsh interface ipv4 show interfaces
netsh interface ipv4 set subinterface "Ethernet" mtu=1500 store=persistent

Linux

ip link show eth0 | grep mtu
sudo ip link set eth0 mtu 9000

Cisco Switch (Jumbo Frame)

switch(config)# system mtu jumbo 9216
switch(config)# exit
switch# reload

Video Tutorial

Key Takeaways

A standard Ethernet frame with 1500-byte payload is 1538 bytes on the wire (including preamble + IFG)
Minimum frame size is 64 bytes (46 payload + 18 header/FCS), padded if payload is shorter
VLAN tagging adds 4 bytes per tag; Q-in-Q adds 8 bytes
Jumbo frames (9000 MTU) reduce overhead to 0.4% — ideal for data center traffic
MTU mismatches cause fragmentation or packet drops — test with ping -f
Include preamble + IFG when calculating true wire-level throughput

Related Tools & Guides

Frequently Asked Questions

What is the minimum Ethernet frame size?

The minimum Ethernet frame size is 64 bytes (excluding preamble and IFG). This includes 14 bytes of header (6 dst MAC + 6 src MAC + 2 EtherType), a minimum 46-byte payload, and 4 bytes of FCS. If the payload is less than 46 bytes, it is padded with zeros to meet the minimum. This minimum exists to ensure collision detection works properly in half-duplex Ethernet.

What is the maximum Ethernet frame size?

The maximum standard Ethernet frame is 1518 bytes (14 header + 1500 payload + 4 FCS). With a single 802.1Q VLAN tag, it is 1522 bytes. Jumbo frames extend the maximum payload to 9000 bytes or more, but jumbo frame support must be enabled on every device in the path, as defined in IEEE 802.3.

What is the interframe gap (IFG)?

The interframe gap is a mandatory 12-byte (96-bit) idle period between transmitted frames on Ethernet. It allows receiving devices to process the previous frame before the next one arrives. The IFG is enforced by the physical layer and counts toward wire-level overhead when calculating maximum throughput.

Should I enable jumbo frames on my home network?

For most home networks, jumbo frames provide negligible benefit and can cause compatibility issues. Jumbo frames are most useful in data center environments with iSCSI storage, NFS, or high-performance computing clusters where large data transfers are common. Every device in the path must support the same jumbo frame size.

What causes MTU mismatch problems?

MTU mismatches occur when devices along a network path have different maximum frame sizes. A common scenario is a VPN or PPPoE connection that adds headers to packets, exceeding the next hop's MTU. Symptoms include connections that stall during large transfers, web pages loading partially, or SSH sessions hanging. Fix by reducing MTU or enabling MSS clamping.

What is the difference between MTU and MSS?

MTU (Maximum Transmission Unit) is the largest frame a network interface can send, measured at the IP layer (typically 1500 bytes). MSS (Maximum Segment Size) is the largest TCP payload, which is MTU minus IP header (20 bytes) minus TCP header (20 bytes), typically 1460 bytes. MSS is negotiated during the TCP three-way handshake.