NetWorx measures how much network data a computer sends and receives. It can show the current transfer rate, retain hourly and daily totals, warn when usage approaches a quota, and record connection outages. NetWorx also has an active speed test and a connection monitor for ping and downtime. It observes traffic; it does not make an Internet line faster or stop another device from using bandwidth.
The first decision determines what the figures mean. NetWorx can watch applications on the local computer, a selected network adapter, or a compatible router interface. These modes answer different questions. Application monitoring identifies local processes, while router monitoring can include traffic that never passed through the computer.
Choose the meter
Application mode records the programs that use the Internet and disregards local network traffic. It is the useful choice when a user wants to find a browser, backup client, or update process behind a transfer. The portable package cannot use this mode, so running NetWorx without installation removes the application breakdown.
Adapter mode watches the selected interface. A computer with Ethernet, Wi-Fi, a VPN, and virtual adapters can expose several choices. Selecting the wrong one can produce an empty graph or count traffic that the Internet provider never bills. A VPN can also move the visible bytes to its virtual adapter.
Read the reports
The usage report groups transfers by hour, day, week, and month. Per-application pages are available when the chosen mode collects that detail. The first day of the week and billing month can be changed so a monthly total follows the provider’s cycle instead of the calendar.
A quota sets an expected allowance and can warn before the total reaches its limit. The warning depends on the counted interface and the configured start date. It cannot correct for traffic that the provider counts differently, and a reset or missing computer can leave the local total below the account statement.
Watch line quality
The Connection Monitor sends regular pings to selected servers and records delay or downtime. This helps separate a recurring line interruption from a slow website. A failed ping is still not proof that the whole Internet connection stopped, because the target or an intermediate route may reject the request.
The Speed Meter performs an active upload and download. A scheduled test can run as often as every five minutes, but each run consumes data. Frequent tests can distort the usage record and spend part of a capped allowance merely to measure speed. A longer interval gives a more useful trend without turning measurement into a major source of traffic.
Count more devices
NetWorx installed on one computer counts only that computer. Several Windows or macOS installations can synchronise their records directly, but a phone, tablet, or television without NetWorx remains outside that total. Synchronisation also has to be enabled on the participating computers.
Router monitoring can capture a wider total when the router exposes SNMP or UPnP data. The computer performing the polling must stay on, and the resulting total does not show a per-device or per-application split. This is the tradeoff: broader coverage loses the detail that names the responsible process.
Act on thresholds
Notifications can react when transfer volume rises above or falls below a chosen level. An action can report a completed large download or shut down a computer after activity ends. Automatic reports can also write usage figures to a file or send them by email.
A threshold needs enough time to ignore brief bursts. Setting it too close to idle traffic can trigger repeated actions, while setting it too high can miss a slow transfer. NetWorx becomes most useful after the monitored interface, billing dates, and notification window have been tested against one known download and the provider’s own usage page.
