Free Bandwidth Monitor Options for One Device or a Whole Network

Free Bandwidth Monitor Options for One Device or a Whole Network

Free Bandwidth Monitor Options for One Device or a Whole Network

A laptop that downloads updates at night needs a monitor on that laptop. A household wondering which devices fill its internet connection needs a view at the gateway or another point that sees their traffic. Free tools for monitoring bandwidth can answer either question, but only if they observe the right connection.

A no-cost network bandwidth monitor can report the traffic crossing an interface, such as Wi-Fi, Ethernet, or a router’s internet-facing port. Choose the observation point first; then choose the tool and the history you need.

Free network bandwidth monitor choices

The following options were checked against their publishers’ information in November 2026. They solve different problems:

Option Platform and scope Free terms and limits
vnStat Linux and BSD host interfaces; can also run on a compatible gateway Free, open source interface counters and historical totals. It does not identify which application or household device generated traffic.
PRTG Network Monitor On-premises Windows server; can poll a compatible router via SNMP Full 30-day trial, then an on-premises freeware edition for up to 100 sensors. A sensor measures an aspect, not necessarily a whole device. Hosted PRTG has no continuing freeware tier.
ntopng Community Linux, FreeBSD, Windows x64, macOS, and Raspberry Pi OS; observes packets presented to it Free, open source community edition; advanced features belong to paid editions. A mirror port, TAP, or gateway placement is needed to see other devices’ traffic.

A free bandwidth monitor on a single computer is often the simplest way to investigate that computer. vnStat reads interface counters rather than inspecting packet contents. Its history starts accumulating when it is running and collecting data; it cannot reconstruct traffic from before collection began.

A free network bandwidth monitor such as PRTG can use Simple Network Management Protocol (SNMP), a way to query counters on a compatible router. An internet-facing interface gives a combined total, while individual device attribution requires another data source. Keep the bandwidth monitor free by staying within the 100-sensor freeware allowance, and count all sensors in the installation, not just the router’s.

The ntopng Community edition is a no-cost network bandwidth monitoring tool that shows traffic by host and flow when it receives the relevant packets. A normal computer plugged into a switched network usually sees its own traffic, not all the traffic between other devices. A managed switch’s mirror port or a network TAP can supply that view. Flow collection from routers through ntopng requires nProbe, which is a separate commercial product.

Set up the right measurement

  1. Name the question. For one Linux machine, install vnStat and identify its active interface with ip link or ip -br link. For the shared internet link, identify the router’s WAN interface—the port carrying traffic to the provider.
  2. Connect the source. Start the vnStat service and query its chosen interface with vnstat -i INTERFACE, replacing the placeholder with its actual name. For PRTG, enable SNMP on a supported router, restrict access to the monitoring host, and add an SNMP traffic sensor for the WAN interface. Use SNMPv3 where both devices support it.
  3. Check the path. Run a known download on the observed device and watch received traffic rise. At a router, direction is relative to the router’s interface, so confirm which counter corresponds to household downloads.
  4. Record the window. Set the polling or sampling interval, retain history, and note the reset date. A free network traffic monitor that stops collecting when its computer is off will leave gaps.

A router may expose physical and virtual interfaces for the same traffic. When using a network bandwidth monitor at no cost, select the interface representing the actual link and avoid adding duplicate counters together. If VPN traffic appears on both a tunnel and its underlying interface, adding both can count the same bytes twice.

Read rate and total separately

A rate is traffic per unit of time, often megabits per second (Mbps). Usage is an accumulated quantity, often gigabytes (GB). A 40 Mbps download held for one minute transfers about 300 MB: 40 million bits per second multiplied by 60, then divided by eight bits per byte. Protocol overhead and changing rates affect real totals.

A free tool for monitoring network bandwidth may poll counters every five minutes, averaging over that interval so a short burst can disappear in the graph. Shorter intervals reveal more detail but create more samples. Counter resets after a reboot, missed polls, and the monitor’s data retention settings can affect the history. Check the tool’s handling of resets before relying on monthly totals.

Even a free bandwidth monitor at the WAN interface may differ from an ISP bill. The provider may count at a different point, include different overhead, use a different billing period or time zone, or round units differently. Compare the same dates and directions, and use the provider’s meter for billing disputes. A speed test measures throughput during a short test; it does not report a month’s usage, and the test itself consumes data.

Quick setup reminder

  • One device: choose its active network interface and keep collection running.
  • Whole network: observe the WAN interface or supply mirrored traffic to the analyzer.
  • History: align the reset date and time zone with the period you want to compare.
  • Interpretation: separate Mbps from GB, check polling gaps, and avoid counting the same path twice.