Why Is My Mac Using So Much Data? The Top Culprits

You glance at your ISP's app and notice you used 180 GB this month. You do not stream 4K Netflix on your Mac. You do not download games. The number does not add up — and the more you stare at it, the more suspicious you get. So why is my mac using so much data, exactly? The answer is almost always one of eight specific things, and most of them are easy to verify once you know where to look.

This post walks through the top culprits in rough order of how often they are the answer, with concrete steps to confirm each one. You can run through the list in about fifteen minutes and almost always find the offender.

1. macOS update downloads

This is the most common culprit, and the most invisible. macOS downloads updates in the background, often pre-fetching them before you ever see the "Update Available" banner. A single point release can be 4 to 12 GB. A full macOS major upgrade is 12 to 15 GB, and if it gets interrupted and re-downloads, you can hit 30 GB without ever clicking "Install."

If you have multiple Macs on the same network, each one downloads its own copy unless you have Content Caching enabled.

How to verify

• System Settings → General → Software Update. If it says "Updating" or shows a progress indicator, that is your traffic.
• Look at softwareupdated in Activity Monitor's Network tab.
• Check your iCloud Apple ID device list — every Mac is downloading independently unless caching is on.

How to mitigate

Turn on Content Caching (System Settings → General → Sharing → Content Caching) on one Mac on your network. Other Apple devices will pull updates from it instead of from Apple's servers. Saves enormous amounts of bandwidth in multi-Mac households.

2. iCloud Photos

The second most common answer. iCloud Photos can push or pull tens of gigabytes silently — especially right after you sign in to a new Mac, restore from backup, change the "Optimize Mac Storage" setting, or import a phone full of 4K video.

A common scenario: you toggle "Download Originals to this Mac" and walk away. Two hours later, 40 GB has moved.

How to verify

• System Settings → Apple ID → iCloud → Photos. Note the storage setting.
• Open Photos. Scroll to the bottom of the main view. There is a status line that says things like "Uploading 1,247 items" or "Downloading 8,930 items."
• In Activity Monitor, look for cloudd and photoanalysisd.

How to mitigate

Set Photos to "Optimize Mac Storage" if you do not need full-resolution copies locally. Pause iCloud sync (the status line at the bottom of Photos has a pause button) while on a metered connection.

3. Time Machine to a network destination

Time Machine to a NAS, an Apple Time Capsule, or a network share will push every changed file across your local network. On its own that does not eat your internet data plan — but if your "network destination" is actually a remote NAS over a VPN, or you are tethered, every Time Machine snapshot becomes WAN traffic.

The first backup is the worst: hundreds of gigabytes. Subsequent ones are smaller (deltas only) but still routinely multi-gigabyte after a busy day.

How to verify

• System Settings → General → Time Machine. Check the destination — is it on your LAN or somewhere remote?
• During a backup, look at backupd in Activity Monitor's Network tab.
• If you tether your Mac to a phone hot-spot and Time Machine kicks off, you will see it instantly.

4. Cloud sync clients (Dropbox, Google Drive, OneDrive, iCloud Drive)

Sync clients are dutiful. They will re-upload large files whenever they think anything has changed — including when an attribute change makes a file look different to the sync engine. Unzipping a 5 GB archive into a synced folder will trigger a 5 GB upload. So will moving files in or out of a synced folder.

Dropbox and Google Drive can also do "smart sync" / "stream files," and toggling that setting can re-download large amounts of data.

How to verify

• Each sync client has a status menu showing what is currently syncing — open it and read the file list.
• In ova or Activity Monitor, sort by network usage and look for Dropbox, Google Drive, OneDrive, or bird (the iCloud Drive daemon).

How to mitigate

Pause syncing on metered networks. Most clients have a "pause" button in their menu bar dropdown. For Dropbox and OneDrive specifically, check whether you accidentally added a huge folder (videos, photos, virtual machine disks) to a synced location.

5. Browser background tabs and extensions

A single open Chrome or Safari window with twenty tabs can quietly use 1 to 5 GB per day. The worst offenders:

• Streaming sites that auto-play next episodes
• Webmail with constant background polling and image preloads
• Slack/Discord/Teams web clients that keep WebSocket connections busy
• Tabs running miners or aggressive ads via compromised extensions
• Cloud IDEs and remote-development sessions

You may not realize a tab is even open — modern browsers happily background-suspend a tab visually while the JavaScript keeps running.

How to verify

• Chrome: chrome://discards and chrome://process-internals/#processes show per-tab and per-process memory and activity.
• Safari: Develop menu → Show Web Inspector for live network activity per tab.
• A bandwidth monitor like ova will show "Google Chrome" climbing without you doing anything.

How to mitigate

Use a tab-suspending extension or a browser like Arc/Safari that aggressively sleeps inactive tabs. Audit extensions — uninstall anything you do not use weekly.

6. Slack, Discord, Telegram, and other chat helpers

Chat apps are surprisingly chatty. They keep persistent connections open, prefetch media, sync read receipts, and refresh giant emoji libraries. Slack in particular pulls thumbnail previews of every link shared in any channel you are in.

In a busy workspace with image-heavy channels, Slack can use 200 to 500 MB per day passively. Multiply that by Discord and Telegram and you are at a gigabyte before you say a word.

How to verify

• Watch the helper processes (Slack Helper, Discord Helper, Telegram Helper) in Activity Monitor's Network tab. The count of helpers is one clue — Electron apps often spawn five or six.
• A monitor that folds helpers under their parent app makes this much easier to read.

How to mitigate

Leave channels you do not actively read. Disable image previews in Slack settings. Quit chat apps overnight if you do not need notifications.

See ova in action

A glance-able menu bar bandwidth monitor — local, signed, ~3 MB.

Download for macOS

7. Video calls and screen-sharing

A high-quality Zoom, Google Meet, FaceTime, or Microsoft Teams call uses 1 to 3 Mbps in each direction. That is 450 MB to 1.4 GB per hour. Screen-sharing pushes that closer to 2 GB per hour because the video stream becomes higher-resolution.

If you take three one-hour calls per day, that is 3 to 6 GB without anything else happening. Add a multi-person call where you are both presenting and receiving streams from a dozen attendees and the number doubles.

How to verify

• During a call, watch the live rate — zoom.us, Microsoft Teams, Google Meet (in Chrome) will be your top consumer.
• Most of these apps have a built-in network stats panel: Zoom under Statistics, Teams under Call Health.

How to mitigate

Most call apps let you cap video resolution or turn off HD video. Doing so cuts bandwidth roughly in half. Audio-only calls drop to 50–100 kbps, which is negligible.

8. Background screen-sharing, remote desktop, and VPN

If you use Apple Screen Sharing, Jump Desktop, AnyDesk, TeamViewer, or a VPN that routes all traffic, those will appear in your bandwidth picture. A persistent VPN does not technically add traffic, but it can hide which app caused the traffic — and some "split tunnel" misconfigurations end up double-encapsulating, doubling the apparent throughput.

How to verify

• System Settings → Network. Look for VPN interfaces, virtual interfaces (utun0, utun1), or screen-sharing daemons.
• Check screensharingd, VPN Tracker, or your VPN client of choice in the network process list.

Answering "why is my mac using so much data" in five minutes

Reading a list is one thing. Pinning the culprit in your specific case is faster with a real per-app monitor. The general flow:

1. Install ova (or another per-app bandwidth tool) and let it run for a day or two.
2. The next time the total looks high, scrub the timeline and find the spike.
3. Check which app owned the spike. That is your answer.
4. Decide whether to disable, pause, or just accept the traffic.

Most of the time the spike will be one of the eight things above. Once in a while it will be something more interesting — an updater that ran wild, a misbehaving extension, a sync that should have been paused. Either way you will know in seconds, not by guessing.

What to do next

A short, ordered checklist for when "why is my mac using so much data" hits you again:

1. Check System Settings → Software Update. Cancel any in-flight downloads if needed.
2. Open Photos and look at the status line at the bottom.
3. Check each cloud sync client's menu bar status.
4. Pause Time Machine if it is mid-backup.
5. Quit and relaunch your browser; note the data usage drop.
6. If the answer is still not obvious, install a per-app bandwidth monitor like ova and watch for a day.

Network traffic on a Mac is usually not mysterious — it is just opaque by default. A few minutes with the right view and almost every "where did 80 GB go" question has a boring, specific answer.