How to Track Daily Internet Usage on a Mac

Your ISP just sent the email: you used 940 GB of your 1 TB monthly cap, with eight days to go. You have no idea where it went. Was it the 4K Apple TV updates? The kid's Roblox sessions? The Time Machine backup that re-uploaded your entire photo library after you swapped drives? You need to track daily internet usage on a Mac so the next time the email arrives, you can answer "I know exactly where it went" instead of "I'd better stop streaming for a week."

This is a guide to setting up that visibility — what to track, how to store it, and how to use the data to make actual decisions.

Why per-day matters more than per-second

When you set out to track daily internet usage on a Mac, the natural instinct is to install something that shows real-time MB/s and call it done. That's the wrong unit. Real-time monitoring tells you what's happening right now. Daily monitoring tells you what's normal — and what isn't. The difference matters because:

• A 200 MB spike in five minutes might be a one-off (someone joined a Zoom call). The same 200 MB happening every five minutes for an hour is a problem.
• ISP caps are billed per month, but the only way to plan for a monthly cap is to track per-day rolling averages.
• Most "expensive" traffic is invisible at the per-second level — it's the slow drip from a backup tool that runs continuously, not a single dramatic spike.

A useful daily tracker answers questions like:

• How much data did this Mac use yesterday, total?
• Which app used the most data this week?
• Are we trending toward our monthly cap, or under it?
• Was today an unusually heavy day? Why?

What macOS gives you out of the box to track daily internet usage on Mac

The honest answer: not much, when it comes to per-day historical data.

• Activity Monitor → Network shows cumulative bytes since each process started. Reboot and the counters reset. There's no per-day rollup.
• netstat -ib shows interface-level cumulative bytes since boot. Same problem — no history beyond the current uptime.
• nettop is a live view; it doesn't write to disk.

To track day-over-day, you have to capture and store the data yourself. That's a small amount of effort if you script it; or you install a tool that does it.

The DIY approach

If you only need system-wide daily totals (not per-app), you can roll your own with cron or launchd. The basic recipe:

1. At midnight every day, read netstat -ib and grab the cumulative bytes for your active interface.
2. Store the value with the date in a CSV.
3. Compute the difference from yesterday's reading.

A working launchd plist runs netstat -ib | awk '/en0/ {print strftime("%Y-%m-%d"), $7, $10; exit}' >> ~/.daily-net.csv daily. It's crude but it works.

What this approach doesn't give you:

• Per-app breakdown. netstat is interface-level; it doesn't know that Backblaze used 12 GB and Safari used 800 MB.
• Recovery from reboots. If your Mac sleeps through midnight, the cron doesn't fire. If it reboots and counters reset, your math goes wrong.
• Visualization. A CSV is data. A chart is information.

For most people, a tool that already does this is worth the few dollars over the time spent maintaining a script.

What a good daily tracker stores

A monitor designed for daily tracking should keep, at minimum:

• Per-day totals for upload and download per app, going back at least 30–90 days.
• Per-hour buckets for the last 7 days so you can answer "what was happening at 3 AM Tuesday?"
• Interface attribution so you can tell whether traffic went over Wi-Fi or ethernet (relevant when you're sometimes on hotspot).

The storage cost is small — even a year of per-app per-hour data is in the low megabytes. The privacy cost depends entirely on whether the data leaves your Mac. Some "monitor" apps upload usage data to a vendor cloud. Others keep everything local.

ova keeps everything local — no telemetry, no account required, no cloud sync. The history file is just a SQLite database on your disk.

Setting alert thresholds

Once you have daily history, you can set thresholds. The useful ones:

• Daily cap warning: alert when a single day exceeds, say, 50 GB.
• Weekly trend: alert when the rolling 7-day total projects to exceed your monthly cap.
• Per-app anomaly: alert when a single app uses 5x its 30-day average in a day.

You don't need a dashboard for this. A weekly habit of glancing at the per-day chart catches almost everything. If something is wrong, the chart looks wrong — a sudden vertical line on Tuesday, a flat plateau where there should be variation.

ISP cap planning

If you're on a metered plan, the math you actually want:

• Monthly cap ÷ days in billing cycle = target daily average.
• Cumulative usage so far ÷ days elapsed = actual daily average.
• If actual > target, you're trending over. The earlier in the cycle you notice, the more days you have to slow down.

For example: 1 TB cap, 30-day cycle = 33 GB/day target. If you're 10 days in and you've used 400 GB, your average is 40 GB/day — projected to hit 1.2 TB by end of cycle. You need to drop to about 30 GB/day for the remaining 20 days.

A daily tracker turns that calculation from a vague worry into an arithmetic problem. The whole point of being able to track daily internet usage on Mac is to keep the math local — to your machine, to the current billing cycle, to a chart you can pull up without logging into anything.

Daily totals, in the menu bar

ova keeps a local per-app time series so you can answer 'where did the gigabytes go?' a week from now.

Download for macOS

The apps that quietly cost the most

In our experience the heaviest contributors to monthly caps on a Mac, in rough order:

1. Cloud backup (Backblaze, Arq, iDrive) — silent, continuous, and especially expensive after a config change that triggers a re-upload.
2. Photos / iCloud Photos — initial upload of a large library, plus continuous incremental uploads of HEIC/JPG and 4K video.
3. Video streaming — Netflix at 4K is roughly 7 GB/hour. YouTube at 1080p is around 2 GB/hour.
4. Software updates — macOS updates are 10–15 GB. Xcode updates regularly hit 8 GB. Adobe Creative Cloud updates are individually small but constant.
5. Steam, Epic Games, Battle.net — game updates are routinely 30–80 GB.
6. Cloud sync — Dropbox, Google Drive, OneDrive moving large folders.

If you can name your top 3 from this list and roughly how much each used last week, you've already won most of the cap-management game.

Reading the chart

When you look at a per-day chart, you're looking for shapes:

• A flat baseline plus occasional bars: healthy. Most days are similar; some are bigger because you actually did something.
• A steady upward ramp: a process is using more over time. Often a backup tool that's still in initial seed.
• A sudden vertical spike: investigate. Was it a stream, an update, a sync re-bootstrap?
• A sustained plateau higher than usual: a setting changed somewhere. Maybe a new device joined your network. Maybe you turned on iCloud Photos.

Per-app charts disambiguate. If the system-wide chart spikes on Tuesday and the per-app view shows it was Backblaze, that's a different conversation than if it was Steam.

A reasonable workflow

Once a tracker is installed and has accumulated a week of data:

1. Each Sunday: glance at last week's per-day chart. Identify any day that's 2x the median.
2. For any flagged day: open the per-app view for that day. Note the top three apps.
3. For unexpected entries: investigate. Was the backup re-seeding? Did a streaming session run longer than expected?
4. Each month: compare total to your ISP cap. If trending over, find which 1–2 apps to dial back.

Five minutes a week. That's the entire ongoing effort, and it's enough to never be surprised by an ISP email again.

Wrapping up

If you want a small, local tool for daily tracking:

• ova is about 3 MB, runs on macOS 14 and up (Apple Silicon and Intel), and keeps a per-app time series locally on your Mac.
• It samples at about 1 Hz, so you also get real-time visibility for the moments you need it.
• No account, no telemetry, no cloud. The data stays on your machine.

One-time payment, lifetime updates, 14-day refund if it doesn't suit how you work. Install it, let it accumulate a week of data, and the next time your ISP sends a usage warning, the answer will already be on your menu bar.