VXLAN Overhead Calculator
Computes effective payload MTU on VXLAN by subtracting outer Ethernet, IP, UDP and VXLAN headers.
—
VXLAN Overhead & MTU Sizing
VXLAN (Virtual eXtensible LAN, RFC 7348) wraps Layer-2 Ethernet frames inside a UDP/IP underlay. Add up what encapsulation costs you and it comes to 8 (VXLAN) + 8 (UDP) + 20 (outer IPv4) + 14 (outer Ethernet) = 50 bytes. Run IPv6 in the underlay and the outer header gains another 20 bytes for a total of 70; toss an 802.1Q VLAN tag onto the outer Ethernet and that's 4 bytes on top.
If you want a full 1500-byte Ethernet payload to travel end-to-end without fragmenting, the underlay has to handle a jumbo MTU of at least 1550 bytes. In practice people just set it to 9000 (jumbo frames). The device doing the encap/decap is the VTEP (VXLAN Tunnel Endpoint), and it keeps the VNI (24-bit VXLAN Network Identifier) → MAC mappings. That 24-bit space gives you up to 16 million logical segments, where 802.1Q VLANs cap out at 4094.
Applications
Walk into any modern data center or cloud fabric and VXLAN is the overlay you'll find running things: NSX-T, Cisco ACI, Arista EVPN-VXLAN, OpenStack Neutron, and the Kubernetes CNIs (Calico, Cilium, Flannel). It's what makes DCI (Data Center Interconnect) work, lets you stretch multi-tenant L2 over an L3 underlay, moves workloads across racks and pods, and pairs with EVPN signaling (RFC 8365) so BGP-distributed MAC/IP routes replace the old flood-and-learn approach.
FAQ
Why is the underlay MTU so important? Once the underlay MTU drops below payload + 50 bytes, your packets either get fragmented or dropped outright (when the DF bit is set). That's where PMTUD black-holes come from, and the performance hit is brutal. The standard fix is jumbo frames at 9000 bytes.
What is a VTEP? Short for VXLAN Tunnel Endpoint. It's whatever originates and terminates the tunnels by tacking on or stripping off those 50 bytes of overhead, whether that's a switch, a hypervisor vSwitch, or a NIC.
How does VXLAN compare to GENEVE or NVGRE? They're all L2-over-L3 overlays. GENEVE (RFC 8926) tacks on variable-length TLV options, and NVGRE leans on GRE rather than UDP. VXLAN ended up the most widely deployed because its UDP source-port entropy plays nicely with ECMP.
Related Tools
TCP MSS from MTU Calculator
Estimates TCP MSS from link MTU, subtracting IP and TCP headers.
HTTP/3 QUIC Overhead Calculator
Computes useful HTTP/3 payload over QUIC, subtracting UDP, QUIC and TLS overhead.
MTU Calculator by Tunnel Encapsulation
Subtracts tunnel overhead from a base MTU of 1500 bytes: PPPoE 8, GRE 24, VXLAN 50, IPsec 56. Returns the effective size to set on the link.
MPLS Label Stack Overhead Calculator
Computes byte overhead of a stacked MPLS label set added to an IP packet.
HTTP/2 Multiplex Streams Calculator
Estimates how many HTTP/2 streams fit per window from MTU and average frame size.
MSS from MTU: TCP Maximum Segment Size
Subtracts the IP and TCP headers from a link MTU, 40 bytes on IPv4 and 60 on IPv6, so 1500 leaves 1460 and 1440 bytes of payload per segment.
The results provided by this tool are for general informational and educational purposes only and do not constitute professional, financial, medical, legal, tax or accounting advice. Always confirm important decisions with a qualified professional and official sources.