An online speed test tells you how fast your broadband is. It can't tell you whether the link between your PC and your NAS, your second PC or your router is running as fast as it should. iperf3 can: it's a free command-line tool that sends test traffic between two devices on your own network and reports the throughput. This guide is based on ESnet's iperf3 documentation; Forge PC hasn't benchmarked any particular network here, so the examples show what to type, not results to expect.
What you need
Two devices on the same network, such as two PCs, or a PC and a laptop. One acts as the server and the other as the client.
iperf3 on both. ESnet, which develops iperf3, says it doesn't distribute binary packages itself; on Ubuntu you can install it with sudo apt-get install iperf3, on macOS with brew install iperf3, and ESnet points Windows users to third-party Windows builds (it lists files.budman.pw as one location).
The server's local IP address. On Windows, open Command Prompt and run ipconfig; look for the IPv4 address of the adapter you're testing.
One caveat: ESnet says iperf3's officially supported platforms are Ubuntu Linux, FreeBSD and macOS, and the Windows builds it points to are provided by third parties.
Step 1: Start the server
On the first device, open a terminal and run:
iperf3 -s
By default the server listens on TCP port 5201. If your firewall asks, allow iperf3 on your private network. Leave this window open.
Step 2: Run a test from the client
On the second device, run this, replacing the address with your server's IP:
iperf3 -c 192.168.1.50
By default a test lasts 10 seconds and sends data from the client to the server. iperf3 prints a line for each second and a summary at the end, with the sender and receiver bitrates.
Step 3: Test the other direction and with more streams
Useful options from the iperf3 manual:
Option | What it does |
|---|
-R
| Reverse the test, so the server sends to the client |
--bidir
| Test both directions at the same time |
-P 4
| Run four parallel streams |
-t 30
| Run for 30 seconds instead of the default 10 |
-p 5202
| Use a different port (default 5201), on both server and client |
-u -b 100M
| UDP test at a target bitrate of 100Mbit/s (the UDP default is 1Mbit/s) |
-1
| Server handles one client connection, then exits |
A sensible routine is a normal test, a -R test and a -P 4 test, then repeat over Wi-Fi from where you actually game.
How to read the results
Compare the result with the slowest link in the path:
If both devices and your switch support 2.5GbE, our 2.5GbE vs 1GbE explainer covers what changes. iperf3 measures throughput; for lag spikes in games, see how to fix high ping and packet loss instead.
Our verdict
iperf3 is the quickest way to find out whether your home network, not your broadband, is the bottleneck. Run iperf3 -s on one device and iperf3 -c with that device's IP on another, test both directions with -R, and compare the result with your slowest cable, port or Wi-Fi link.