Unit Converter
Ethernet Line Rate Converter
Estimate maximum frame rate and application payload rate from Ethernet MAC capacity, IP packet size, protocol headers and VLAN tags.
Ethernet Line Rate Converter examples
Sample inputs for the Ethernet Line Rate Converter include gigabit and fast Ethernet with full-size and minimum packets.
| Input | Expected result |
|---|---|
| 1,000 Mbps; 1500-byte IP; IPv4/TCP; no tag | ≈949.2847854 Mbps application; ≈81,274.38231 frames/s |
| 100 Mbps; 1500-byte IP; IPv4/TCP; no tag | ≈94.92847854 Mbps application |
| 1,000 Mbps; 40-byte IP; IPv4/TCP; no tag | 64-byte padded frame; zero application payload |
| 1,000 Mbps; 1500-byte IP; IPv4/TCP; one tag | ≈946.8223087 Mbps application |
Supported units & limits
Select a listed MAC capacity from 10 to 800,000 Mbps as a mathematical input, not a hardware-compatibility claim. IP length must be a whole number no greater than 9000 bytes and at least the selected combined header size. Supports IPv4 without options (20 bytes), IPv6 without extensions (40 bytes), TCP without options (20 bytes), UDP (8 bytes), and zero to two 4-byte VLAN tags. Model assumes one IP packet per Ethernet frame, minimum 64-byte frames including FCS/padding, full-duplex single-direction steady transmission and minimum IFG. Jumbo support is not inferred. PHY coding/FEC, collisions, stalls, reverse ACK capacity, retransmissions, TLS and tunnels are not modeled. Floating-point results use selected precision.
Common mistakes
1500 bytes usually describes the complete IP packet, not TCP application data. With the default IPv4/TCP headers it contains 1460 application bytes. A MAC bit rate is not a raw PHY symbol rate or guaranteed useful throughput. VLAN bytes and Ethernet minimum padding consume link time. A zero-payload header-only packet is allowed but delivers no application bytes. A 1,500-byte MTU is the IP packet size; enter it as the IP length in the Ethernet Line Rate Converter, not as the frame size.
Privacy
Conversions run in your browser. This site does not upload or store the values you enter. We use Google Analytics, loaded through Google Tag Manager, to count page visits and see which tools are used; Google may set cookies for this. The hosting server may keep standard access logs when you load a page.
Conversion guide
Keep MAC capacity, packet size and useful data separate
Choose MAC capacity for one direction. Enter the full IP packet length including its IP and transport headers, select the header model and VLAN count, then inspect the complete frame length and occupied byte-times. Compare application payload ceiling with measured throughput only after considering transport behavior and additional encapsulation.
Ethernet Line Rate Converter FAQ
Why is application throughput below MAC capacity?
Some link time carries Ethernet/IP/transport headers, FCS, padding and preamble, or is reserved for the inter-frame gap. Only the selected application bytes count toward the payload result.
Does this simulate TCP?
No. It only budgets bytes and link time. TCP windows, RTT, slow start, acknowledgments and losses can reduce achieved throughput further.
Are small packets padded?
The model pads the complete frame to at least 64 bytes including FCS. Padding is not added to the IP or application payload.
Can I use the result as a measured link speed?
No. It is a theoretical ceiling under the displayed header and steady-transmission assumptions. Actual systems require measurement.