BWMeter measures the network traffic that passes through a computer and can apply rules to selected connections. It records bytes rather than changing the files being transferred. A graph answers when traffic rose, while filters can narrow the total by network adapter, address, port, protocol, or application. This makes BWMeter different from a simple Internet speed test, which measures one short transfer against a remote server.
Choose the adapter
A computer can have Ethernet, Wi-Fi, virtual private network, virtual machine, and loopback interfaces at the same time. BWMeter watches the interfaces selected in its configuration. Choosing the wrong one can produce an empty graph even while the browser is active. Watching overlapping paths can also make a total confusing when traffic crosses a virtual adapter before leaving through a physical one.
The live graph shows changing bandwidth, while numerical counters preserve totals. BWMeter can separate traffic inside the local network from traffic that reaches the Internet. That distinction is useful when a backup to a network storage device is saturating Wi-Fi but should not count as Internet use. The result depends on correct address rules; an incorrect local-network range can classify ordinary Internet traffic as local or do the reverse.
Traffic filters
Filters describe which packets belong to a counter or rule. An address filter can isolate a server or subnet. Port and protocol conditions can focus on a service, while application conditions connect traffic to a process. Several conditions can describe a narrower stream than one general interface total.
Encrypted traffic still has addresses and connection metadata, but BWMeter does not turn encrypted payloads into readable documents. Modern applications can also share system services or change ports. A filter that assumes one fixed port may miss part of an application’s traffic. Testing a rule against the live graph before relying on its historical total reduces that risk.
Limits and blocks
BWMeter can limit transfer speed or block selected network access. A speed rule can keep one process from taking the entire connection. An access rule can stop a program, address, or service from communicating. These actions happen at the traffic layer; they do not change the application’s own settings.
A broad rule can interrupt legitimate work. Blocking an address range can also block sign-in, updates, or content delivered from the same network. A very low speed limit may look like a broken application rather than an intentional restriction. The interactive firewall can ask for a decision when matching traffic appears, while silent handling avoids prompts. Either mode still depends on the rule being specific enough.
Stored statistics
Daily, weekly, monthly, and yearly records show how usage changes over time. Import and export functions move statistics for later review. These figures represent traffic observed by BWMeter, not the billing method used by an Internet provider. Provider totals can count router traffic, protocol overhead, or other devices that this computer never sees.
BWMeter can collect statistics from other computers that also run BWMeter. Installing it on one machine does not automatically reveal every device behind the same router. Remote collection needs the other systems to participate and remain reachable. A phone, console, or guest computer without that component stays outside those remote statistics.
