Finding Your App-Wise Data Usage in Windows: Task Manager, Settings, and the Data Limit Cap That Resets Monthly

Windows tracks network traffic per app, but it keeps two separate ledgers that disagree with each other. The real-time figures live in Task Manager's App history tab, measured in megabytes. The billable figures live in Settings under Data usage, measured in gigabytes and split by network type, and that second ledger is the one Windows uses to enforce a monthly data limit. If your goal is to find out which app ate your mobile hotspot allowance, open Settings > Network & internet > Data usage and check the per-app list under the active Wi-Fi or Ethernet connection, sorted by usage. Task Manager tells you what is happening now; Settings tells you what already happened and what counts against a cap.

Why Task Manager and Settings Report Different Numbers for the Same App

Microsoft publishes two network accounting systems inside Windows and they were never designed to reconcile. Task Manager's App history samples traffic at the process level and reports cumulative totals since the last reset, which is why a freshly reinstalled browser shows a near-zero figure while your Settings page still shows hundreds of megabytes from the previous week. Windows Update, Delivery Optimization, and system services frequently attribute traffic to a different process than the one you recognize.

The Settings page pulls from the same underlying network usage database but groups traffic by app package rather than process, and it discards data that Windows classifies as unmetered background activity on certain connection types. In practice this means a VPN client can show 400 MB in Task Manager and 40 MB in Settings for the same hour, because encrypted tunnel traffic gets counted once at the adapter level and once at the socket level depending on which subsystem logged it.

Connection type changes the answer too. Windows assigns a network profile of Public or Private when you first join a network, and that profile determines whether the connection is treated as metered. A metered connection suppresses background downloads and changes how some apps report usage, so the same app on the same laptop can show wildly different monthly totals depending on whether you marked your home Wi-Fi as metered.

Use Task Manager when you suspect an app is misbehaving right now, and Settings when you need a number you can act on for billing or hotspot budgeting. Neither is authoritative for a third-party router's accounting, which counts packets at the gateway and will always be the number your carrier sees.

The Fastest Route: Task Manager's App History Tab in Five Clicks

Task Manager is the only built-in tool that attributes live traffic to a named process without opening a settings page, and the App history tab keeps a running total that survives reboots. The catch is that this tab exists only in the full Task Manager window, not the compact view that opens by default on some systems, and Microsoft removed the per-process network column from the Processes tab in Windows 8 and never restored it.

1: Press Ctrl + Shift + Esc to open Task Manager directly, or right-click the taskbar and choose Task Manager. 2: If the window is small and shows only a list of apps, click More details at the bottom left. 3: Select the App history tab. On Windows 11 builds the tab may be hidden behind the overflow chevron if the window is narrow. 4: Click the Network column header once to sort descending, so the biggest consumer sits at the top. 5: Read the values in megabytes. To zero the counters, click Delete usage history in the top right and confirm.

If the App history tab is missing entirely, you are likely on Windows 10 version 1809 or later where Microsoft moved the feature behind a policy, or on a managed work machine where an administrator disabled it through Group Policy under User Configuration > Administrative Templates > Windows Components > File Explorer. In that case the Settings path below is your only built-in option.

Sorting by network descending is the right first move because the top three rows almost always account for the majority of traffic. Expect browsers, cloud sync clients, and game launchers in that top group. A single Windows Update delivery can push the BackgroundDownloader or MoUsoCoreWorker entry into the hundreds of megabytes without any obvious user action.

Windows 11 Settings: Reading the 30-Day Per-App Breakdown

The Settings page is where Windows stores the number it will act on, and the per-app list underneath it is the closest thing to a bill you will get without third-party software. Open Settings with Windows key + I, then go to Network & internet > Data usage. The top card shows total usage for the last 30 days across all connections, and below it a list of apps appears once you click View usage details per app or scroll to the app breakdown. On Windows 11 22H2 and later the breakdown sits directly on the Data usage page under a heading that lists each app with a usage figure in megabytes.

The app list is grouped by connection type. Click the dropdown that shows your active adapter name, and you can switch between Wi-Fi, Ethernet, and any mobile broadband adapter. Usage figures shown here are cumulative for the default 30-day window, which the Windows networking stack recalculates on a rolling basis rather than on the first of the month unless you change it.

Two behaviors trip people up. First, the list only shows apps Windows recognizes as packaged or registered; portable executables run from a USB stick may appear as "System" or not at all. Second, the totals include traffic from Windows Update and Delivery Optimization lumped under a single background entry, so a machine that has just installed a cumulative update will show a large unexplained block.

Microsoft's own support documentation for Windows 11 confirms the 30-day default and notes that usage history is stored per user profile, not per device. Sign in as a different account and the Data usage page shows that account's traffic only, which explains why a shared family PC never adds up to the household's router total.

Setting a Data Limit So Windows Warns You Before the Cap

A data limit converts the per-app list from an interesting readout into an active guard. Windows can warn you at a threshold and cut metered background traffic when you approach the limit, and the per-app breakdown then becomes the audit trail for what consumed the allowance. The feature works on any connection type but is most useful on a mobile hotspot or a capped home plan.

1: Open Settings > Network & internet > Data usage. 2: Click Enter limit (Windows 11) or Set limit (Windows 10) next to the active connection. 3: Choose the limit type: Monthly, One time, or Unlimited. Monthly resets on the day of the month you pick. 4: Enter the data cap in gigabytes or megabytes, then set a restart date. 5: Toggle on the warning at a percentage threshold and save.

The reset day matters more than most people realize. If your carrier billing cycle starts on the 18th, set the Windows restart date to the 18th; otherwise the counter zeroes on the wrong day and your warning fires mid-cycle. Windows does not know your carrier's billing date, and it will not infer it.

Failure handling for the obvious cases: if the Data limit option is greyed out, the connection is marked as unmetered — set it to metered first by clicking Properties on the network in Settings > Network & internet > Wi-Fi > Manage known networks. If the limit never triggers a warning, check that background data restrictions are on under the same page, because turning that off disables the enforcement even though the counter keeps running.

A monthly limit set to 50 GB with a warning at 80 percent gives you 40 GB of free movement before Windows nudges you. On a 15 GB hotspot plan, a 12 GB limit with a 75 percent warning leaves 3 GB of buffer, which is roughly two hours of HD video streaming at the 3 GB per hour figure Netflix publishes for its High definition tier.

Third-Party Meters That Survive a Windows Reinstall

Built-in tools have one hard limitation: the usage database lives in the user profile and dies with a clean install or a profile rebuild. If you need continuous records across a reinstall, a third-party meter stores its log in a separate location or syncs it. GlassWire, NetWorx, and the open-source TrafficMonitor all do per-app accounting, and each handles the attribution problem differently.

GlassWire presents a firewall-style graph with a per-app breakdown and keeps history for months depending on edition; the free tier retains a shorter window than the paid editions, and the paid tiers are subscription-based, so confirm current pricing on the maker's site before budgeting. NetWorx from SoftPerfect is the older, plainer option and reports per-application usage with exportable reports in its paid edition. TrafficMonitor is a lightweight taskbar readout that logs per-process totals to a CSV file, which is the most portable record of the three.

The trade-off is trust. Every third-party meter installs a network filter driver to see traffic before Windows aggregates it, and that driver is exactly the kind of component that conflicts with VPN clients and endpoint security software. If you run a corporate VPN, check with IT before installing one, because filter driver conflicts produce dropped connections that look like a VPN fault.

For most home users the built-in Settings page is enough. Reach for a third-party tool only when you need history that survives a reinstall, sub-app process-level attribution, or alerts that fire in real time rather than at the next Settings visit.

Reading the Numbers in the Right Unit: MB, GB, and Binary Confusion

Half the confusion about data usage comes from unit mismatches, and Windows does not help by mixing conventions between screens. Task Manager's App history reports in megabytes using the binary definition, where 1 MB equals 1,048,576 bytes, while carriers bill in decimal gigabytes where 1 GB equals 1,000,000,000 bytes. The gap is roughly 7 percent at the gigabyte scale, which is enough to make a 10 GB carrier allowance look exhausted when Windows still shows 600 MB remaining.

Convert before you compare. Take the Task Manager figure in MB, multiply by 1.048576 to get decimal megabytes, then divide by 1,000 to reach decimal gigabytes. A 4,000 MB App history total becomes about 4.19 GB on your carrier's bill, not 4 GB. That 190 MB difference is a rounding error on a home plan and a real overage trigger on a 1 GB emergency hotspot.

Windows also reports some figures in bits per second in Resource Monitor and Performance Monitor, which matters if you are trying to convert a live throughput reading into a monthly projection. A sustained 1 Mbps for an hour is 450 MB, because 1 megabit per second times 3,600 seconds is 3,600 megabits, divided by 8 gives 450 megabytes. Carriers quote speeds in megabits and allowances in gigabytes, so the factor of 8 sits between every speed reading and every data figure.

Rounding compounds once you project. A background sync running at 200 Kbps around the clock consumes roughly 2.16 GB per day by the same arithmetic, which turns a "small" background task into a plan-killer. That is why the per-app list matters more than the total: a single always-on client can hide inside a household total that looks normal until the cap hits.

The Apps That Quietly Eat the Most Background Data

The per-app list is only useful if you know what to look for, and the biggest offenders are rarely the apps you actively use. Windows itself tops the list on most machines that have recently updated. According to Microsoft's Delivery Optimization documentation, updates can be pulled from other PCs on the local network and from Microsoft's servers, and on a metered connection those transfers should pause, though the pause only works if the connection is correctly marked as metered.

Cloud storage clients are the second category. OneDrive, Dropbox, and Google Drive all sync in the background and all show up in the per-app list under their own names. OneDrive has a built-in setting to pause syncing on metered connections, which is worth enabling if you tether. Google Drive's desktop client historically ran as a background process that appeared under DriveFS in the Settings list. Dropbox reports under its own name and offers a bandwidth limit in preferences.

Browsers are the third. Chrome, Edge, and Firefox all continue background activity after you close the window unless you disable the setting, and Edge specifically runs background extensions and update checks that appear in the per-app list even when no tab is open. Edge's startup boost feature keeps processes alive after the window closes, and that shows up as traffic after you think you have stopped browsing.

The honest way to read the list is to look for surprise entries above 500 MB on a metered connection. A browser at 2 GB in a 30-day window with heavy use is normal. A browser at 2 GB with light use is a background process problem. A system component above 1 GB almost always means an update cycle, and that is worth checking against your plan before it repeats on the next Patch Tuesday.

When the Numbers You See Don't Add Up

Discrepancies between the router, the carrier, and Windows are normal and the reasons are predictable. The router counts every packet that crosses the gateway including devices Windows cannot see, retransmissions, and protocol overhead, which adds roughly 5 to 10 percent on top of application-level data. Windows counts application payload as reported by the socket layer, so the router's number will always be higher.

Other devices on the same network are the most common explanation. A phone, a smart TV, and a game console all share the router's total but appear nowhere in Windows. If your router says 400 GB this month and Windows says 90 GB, the difference is almost certainly the other devices, not a Windows reporting bug.

VPN tunnel traffic double-counts inside Windows under some configurations. The tunnel adapter logs the encrypted payload while the underlying physical adapter logs the same bytes, so a 5 GB month of VPN use can appear as 10 GB in aggregate adapter counters even though the Settings per-app list deduplicates it. Adapter-level counters in Resource Monitor are the most affected by this.

A much rarer cause is traffic that never touches a Windows counter at all. Wake-on-LAN, out-of-band management on business hardware, and firmware-level update agents on some OEM systems report outside the operating system. If the router shows traffic while the PC is asleep, the accounting gap is upstream of Windows. Check the router's per-device log rather than the Windows total in that case.

Matching Your Windows Usage to a Carrier Bill

Reconciling Windows against a carrier bill follows a fixed sequence once you accept the numbers will never match exactly. The goal is to explain the gap, not to eliminate it, because protocol overhead and other devices guarantee a difference. Work through the layers in order rather than trying to fix the discrepancy at the Windows level.

1: Pull the carrier's billing cycle dates and the billed total from the carrier's app or statement. 2: Note the router's total for the same cycle from its admin page. 3: Open Settings > Network & internet > Data usage and set the 30-day window to match the carrier cycle as closely as the rolling counter allows. 4: Compare the Settings total to the router total and attribute the difference to other devices and overhead. 5: Compare the router total to the carrier bill and attribute the remainder to metering differences and off-network usage on other lines.

If step 5 still leaves an unexplained gap above 10 percent, the likely culprits are data used on the carrier's own network outside Wi-Fi, or a shared data plan where another line consumed the allowance. Both live outside Windows entirely and no amount of per-app auditing on the PC will find them.

The practical takeaway is a split rule. On a metered connection, trust the Settings per-app list for identifying which app to throttle and the router for deciding whether you are over. On an unmetered home connection, ignore all three for budgeting and use the per-app list only to catch background anomalies.

FAQ

Does Windows reset app data usage automatically each month?

Only if you set a monthly data limit with a restart date, which triggers the reset on that day. Without a limit, the Settings total rolls on a continuous 30-day window rather than clearing on the first of the month. Task Manager's App history never resets automatically at all; the Delete usage history button is the only thing that zeroes it. Set the restart date to your carrier's billing date if the figure needs to match a statement.

Why does Task Manager show an app using data when I have it closed?

Background processes and startup entries keep running after a window closes. Edge's startup boost, OneDrive's sync engine, and most game launchers continue downloading and checking for updates with no visible window. Check the Startup apps list in Task Manager and the app's own background permission settings. In Edge specifically, turning off "Continue running background extensions and apps when Microsoft Edge is closed" under System and performance stops most of it.

Can I see data usage for a single day rather than a month?

Not reliably with built-in tools. Settings aggregates the 30-day window and Task Manager shows a cumulative total, and neither offers a per-day breakdown without third-party software. For a single-day view, delete the App history in Task Manager before the test, run the day normally, and read the total at the end. That gives you one day of process-level data with no extra installs, though it wipes your prior totals.

Does the per-app data usage list include traffic from other user accounts?

No. Windows stores network usage per user profile, so the Settings breakdown shows only the signed-in account's traffic. On a family PC the household total is the sum of each profile plus traffic from Windows services and any app installed for all users. Sign in to each account and add the figures, or use the router's per-device log, to see the full picture.

How many megabytes are in a gigabyte as Windows counts it?

Windows uses 1,048,576 bytes for a megabyte and 1,073,741,824 bytes for a gigabyte in its file and network displays. Carriers bill in decimal units where 1 GB is 1,000,000,000 bytes, so a Windows figure of 10 GB equals roughly 10.74 GB on a carrier bill. The gap widens as usage grows, which is why a plan can feel exhausted before Windows shows it as full.

What happens to background data when I turn on the data limit?

Windows blocks background traffic for apps that respect the metered-connection flag, which includes Windows Update, Delivery Optimization, and OneDrive when its metered setting is on. Apps that ignore the flag continue downloading, and those are the ones the per-app list will expose. Turning on the limit does not stop traffic from an app that never checks the connection's metered status, so audit the list after the first cycle.

Is the data usage figure different on Windows 10 and Windows 11?

The underlying accounting is the same, but the path differs. Windows 10 puts the per-app breakdown behind a "View usage details" link under Settings > Network & Internet > Data usage, while Windows 11 22H2 and later shows the app list directly on the Data usage page. Windows 10 also labels the limit button "Set limit" where Windows 11 says "Enter limit," and the Windows 11 page exposes the per-connection dropdown more prominently.