Calculate packets per second from Mbps or Gbps, convert PPS back to bandwidth, or solve for average frame size. Ethernet wire overhead is included by default, and the device-capacity check turns a datasheet Mpps rating into usable headroom.
Choose what to calculate. Values use decimal networking units and constant average frame size.
Decimals:
0
Calculated
Link rate, traffic rate, or required bandwidth.
Calculated
Packets or frames processed each second.
Calculated
bytes
Meaning depends on the size basis below.
64B Ethernet frame → 84B on the wire. Frames below 64B are padded.
Common frame or MTU sizes
Packet sizes vary by protocol and workload; these are calculation examples, not traffic labels.
Calculated result
1,488,095 PPS
1.488 Mpps at Ethernet line rate
Line-rate PPS1,488,095
No-overhead comparison1,953,125 PPS
Bandwidth1 Gbps
On-wire size84 B
Average frame/IP size64 B frame
Packets per minute89,285,714
Check a router, firewall, switch, or VM PPS rating
Enter the packet-rate capacity tested for your actual feature set. Choose your own maximum utilization target; the tool does not invent a universal safety margin.
Current calculated load
74.4%
Above your 70% planning target
At this packet size, the selected target supports approximately 940.8 Mbps. Also check connections/s, concurrent sessions, inspection, encryption, backplane, and application limits.
What Does Packet Per Second Mean?
Packets per second (PPS) is the number of packets a system sends, receives, or processes each second. On Ethernet, line-rate calculations are more precisely frames per second. Packet size matters: 1 Gbps ranges from 81,274 PPS with a 1,500-byte IP MTU to 1,488,095 PPS with minimum 64-byte Ethernet frames.
A device performs work for every packet: parsing headers, looking up a destination, applying policy, tracking state, or handing data to an application. Two traffic streams can therefore use the same Mbps while creating radically different processing loads. That is why useful specifications report both bit rate and packet rate.
Packets Per Second or Bits Per Second: Which Is the Real Limit?
Both are real limits, and neither tells the whole story alone. A physical interface cannot exceed its line rate in bits per second or its corresponding frame rate. The system attached to it may reach a different ceiling first: packet forwarding, new connections per second, concurrent sessions, TLS operations, firewall inspection, memory, CPU, NIC queues, backplane capacity, or application transactions.
The link limit
Bit rate caps total wire traffic. Frame rate caps how many frames fit when each one consumes its framing and inter-frame time.
The device or application limit
A firewall, load balancer, VM, or application may stop scaling before the link fills—especially with small packets, many new flows, encryption, or deep inspection.
The practical capacity is the first relevant ceiling reached under the configuration you will actually run. Cisco makes the same distinction: routers and switches need bit-rate and packet-rate metrics, while stateful devices also need connection-rate and concurrent-connection metrics. The capacity checker above deliberately asks for your tested PPS rating rather than pretending one generic hardware range applies to every device.
Packets Per Second Formulas
Bandwidth → PPS
PPS = bits/s ÷ (wire bytes × 8)
PPS → bandwidth
bits/s = PPS × wire bytes × 8
Bandwidth + PPS → size
wire bytes = bits/s ÷ PPS ÷ 8
Why 10 Gbps equals 14.88 Mpps at minimum frame size
1. Minimum Ethernet frame: 64 bytes from destination MAC through frame check sequence.
2. Add 8 bytes of preamble/start-frame delimiter and 12 byte-times of inter-frame gap: 84 on-wire bytes.
Most PPS disagreements are not arithmetic errors; they are measurement-boundary errors. “Packet size” may mean a Layer 3 IP packet, a Layer 2 Ethernet frame, or all time occupied on the wire. State the boundary before comparing results.
Packet and frame size assumptions used by the PPS calculator
Input basis
What the number includes
What the calculator adds
Example
Ethernet frame
MAC header through FCS
20B preamble/SFD + inter-frame gap
64B → 84B wire
IP packet / MTU
Layer 3 packet
18B Ethernet header/FCS + 20B wire time
1500B → 1538B wire
Custom on-wire
Your complete accounting boundary
Nothing
Useful for non-Ethernet or custom models
VLAN tags, tunnels, encryption, and other encapsulation can add bytes. Model the frame actually presented to the link or enter a custom on-wire size.
Ethernet Line-Rate PPS Reference
Rounded to the nearest frame/s · wire overhead included
Ethernet packets or frames per second by link speed and frame size
Link speed
64B frame
128B frame
512B frame
1500B IP MTU
9000B frame
100 Mbps
148,810
84,459
23,496
8,127
1,386
1 Gbps
1,488,095
844,595
234,962
81,274
13,858
10 Gbps
14,880,952
8,445,946
2,349,624
812,744
138,580
25 Gbps
37,202,381
21,114,865
5,874,060
2,031,860
346,452
40 Gbps
59,523,810
33,783,784
9,398,496
3,250,975
554,324
100 Gbps
148,809,524
84,459,459
23,496,241
8,127,438
1,385,809
The 1,500-byte column treats 1,500 bytes as the IP MTU, producing a 1,518-byte Ethernet frame and 1,538-byte on-wire cost. The 9,000-byte column treats 9,000 bytes as the Ethernet frame size.
How to Find the Practical PPS Limit of a Device
A datasheet maximum is a test result under stated conditions—not a promise for every configuration. Before sizing a router, firewall, load balancer, NIC, or VM, record five things:
1. Size and direction. Was PPS tested with 64-byte frames? Is the number one-way, bidirectional, per port, or aggregate?
2. Enabled features. Test the actual NAT, ACL, IPS, VPN, TLS, QoS, and logging configuration.
3. Other ceilings. Capture connections/s, concurrent sessions, backplane, CPU, memory, queues, and application transactions.
4. Loss and latency. Capacity ends where loss, queueing, or latency crosses your acceptance criteria—not where the box stops completely.
5. Growth and headroom. Use a planning target you can defend, then test again after major policy, firmware, or traffic-mix changes.
A practical small-packet example
Suppose a workload generates 3 million PPS and each complete Ethernet frame averages 100 bytes. With 20 bytes of wire time, it occupies 3,000,000 × 120 × 8 = 2.88 Gbps. A 10 Gbps link has bandwidth left, but the host, load balancer, firewall, and application must each sustain the packet, connection, and transaction rates. If “100 bytes” means application payload instead of Ethernet frame size, the real wire rate is higher because protocol headers still need to be added.
For a baseline and procurement workflow, continue with What Is a Good PPS in Networking?. It explains how to measure peak PPS on Linux, macOS, Windows, routers, and cloud VMs, then compare it with a feature-on device test.
Frequently Asked Questions
Packet-rate definitions, formulas, and limits
What does packet per second mean?
Packets per second (PPS) is the number of packets or frames transmitted, received, or processed each second. On an Ethernet link, the technically precise line-rate term is frames per second, but equipment specifications and monitoring tools commonly use PPS.
How many packets per second is 1 Gbps?
It depends on frame size. At Ethernet line rate, 1 Gbps carries 1,488,095 minimum 64-byte frames per second because each frame occupies 84 bytes on the wire. With a 1,500-byte IP MTU, the frame occupies 1,538 bytes on the wire and the rate is 81,274 PPS.
How do I convert Mbps to packets per second?
Convert Mbps to bits per second, then divide by the on-wire bits per packet: PPS = Mbps × 1,000,000 ÷ (wire bytes × 8). For an Ethernet frame, wire bytes normally equals frame bytes plus 20 bytes for the preamble, start-frame delimiter, and inter-frame gap.
Can I convert PPS to Mbps?
Yes, if you know the average packet or frame size and its overhead basis. Multiply PPS by the on-wire bytes per packet and by 8, then divide by 1,000,000. Without an average size, PPS cannot be converted to one unique Mbps value.
Is packets per second or bits per second the real network limit?
Both can be limits. The link has a bit-rate and frame-rate ceiling; the device may also have packet-processing, new-connection, concurrent-session, encryption, inspection, or application transaction limits. The practical limit is whichever relevant resource reaches its tested ceiling first.
What is 14.88 Mpps?
14.88 Mpps is the Ethernet line rate of a 10 Gbps link carrying minimum-size 64-byte frames. Each frame occupies 84 bytes or 672 bits on the wire, so 10,000,000,000 ÷ 672 = 14,880,952 frames per second.
Why do some PPS calculators show 1.95 Mpps for 1 Gbps?
They divide 1 Gbps by 64 bytes and ignore 20 bytes of Ethernet wire time per frame. That produces 1,953,125 PPS. Including the 8-byte preamble and start-frame delimiter plus the 12-byte inter-frame gap produces the correct line-rate result of 1,488,095 frames per second.
Why is measured PPS lower than the calculator result?
The calculator gives a theoretical link rate for a constant average size. Real results can be lower because of mixed packet sizes, idle gaps, protocol behavior, retransmissions, queueing, software and NIC limits, enabled security features, and whether counters measure Layer 2 frames or Layer 3 packets.
All table values were independently calculated from the stated on-wire byte counts and cross-checked against Cisco's published 1 Gbps values. See a discrepancy? Use the contact page; our editorial standards explain the correction process.
