How to Catch Apps Uploading in the Background on Mac
Background uploads on a Mac can drain a data cap silently. Here is how to find the apps doing it, and decide what to keep.
- macOS
- Bandwidth
- Privacy
- Troubleshooting
Downloads are usually obvious — you click something, a number goes up. Uploads are the quiet ones. You sit down to write an email and your menu bar shows 25 Mbps going out, not in, and nothing on your screen explains why. Catching apps uploading background mac traffic is its own skill, and worth learning if you care about data plans, privacy, or just understanding what your machine is doing.
This post walks through why upload spikes deserve more attention than download spikes, the most common offenders, and a step-by-step diagnostic for finding the responsible app.
Why upload traffic deserves more attention
Most people only think about download. The bandwidth meter at the ISP usually shows a single big "down" number, and that is what gets cached in your head as "internet usage." But upload traffic has three properties that make it more important to monitor than download in some scenarios:
- Asymmetric plans punish it harder. Most home connections give you 10x more download than upload. A sustained 25 Mbps upload can saturate your link while download is barely touched, but everyone in the house will notice latency spike.
- Data caps count it. A 1 TB monthly cap is symmetric — uploaded gigabytes count exactly as much as downloaded ones.
- Privacy and exfiltration concerns. A program uploading gigabytes from your Mac is sending your data somewhere. Whether that is a benign backup or something you do not want, you should know.
A 5 GB download spike is usually a movie or an update. A 5 GB upload spike is always something taking your data and shipping it. Worth knowing what.
The usual suspects, ranked
In rough order of how often they turn up as the answer:
1. Time Machine to a network destination
Time Machine pushing to a NAS, Apple Time Capsule, or any networked drive will create giant sustained uploads. The first backup is the worst — hundreds of gigabytes. Subsequent ones are smaller (incremental) but still routinely 1 to 10 GB per snapshot.
If your "network destination" is reachable over the WAN (a remote NAS, a SMB share over VPN), every Time Machine snapshot becomes internet upload.
Verify: System Settings → General → Time Machine. Look for backupd in your bandwidth monitor.
2. iCloud Photos uploading originals
Toggling "Download Originals to this Mac" off and then back on, importing a phone full of 4K video, or signing into a new Mac will all trigger massive upload sessions. iCloud Photos is the biggest source of unexpected upload spikes on consumer Macs.
Verify: Open Photos, scroll to the very bottom of the main library view. There is a status line showing "Uploading 2,431 items" with a pause button. cloudd and photoanalysisd will be visible in your monitor.
3. Cloud sync clients (Dropbox, Google Drive, OneDrive, iCloud Drive)
Any change to a synced folder triggers an upload. Common surprises:
- Unzipping a 5 GB archive into Dropbox triggers a 5 GB upload
- Moving a folder into Google Drive triggers a re-upload of everything in it
- Re-syncing after a big metadata change (Spotlight reindex, ACL change) can re-upload thousands of files
Verify: Open the menu bar dropdown of each sync client — most show what they are currently syncing. In your bandwidth monitor, look for Dropbox, Google Drive, OneDrive, or bird (iCloud Drive).
4. Cloud backup (Backblaze, Arq, Carbonite)
Backup clients are the highest-volume uploaders by design. Initial backups can be days or weeks of upload. Even on incremental schedules, 5 to 50 GB per day is normal for active workstations.
Verify: Open the backup client's status panel. Backblaze in particular has a clear "uploading X MB/s" indicator.
5. Antivirus, EDR, and "security" telemetry
Enterprise security tools (CrowdStrike, SentinelOne, Sophos, Defender for Endpoint, Jamf Protect) and some consumer antivirus products send substantial telemetry — file metadata, process trees, network connection logs. On managed Macs this can be hundreds of MB to several GB per day.
This is the category most likely to surprise you because it is always on, never asks for confirmation, and rarely shows a UI.
Verify: Look for processes with names like mdatp, sentineld, falconctl, Sophos. If your Mac is managed by your employer, check System Settings → Privacy & Security → Profiles.
6. Video calls (always-on)
Even idle video calls upload your camera feed. A muted-but-video-on Zoom call uploads 1 to 2 Mbps continuously. Forgetting that you are still in a meeting after lunch is a real way to lose 1 GB silently.
Verify: Camera indicator (green dot near the top-right of the menu bar). If it is on and you are not actively talking to anyone, something is uploading your camera.
7. Screen recording, streaming, and remote desktop
OBS streaming to Twitch, RTMP outputs, or active screen-sharing tools all upload continuously while running. AnyDesk, TeamViewer, Apple Screen Sharing, and Jump Desktop will upload frames as long as a session is active.
Verify: Screen recording indicator in the menu bar. Check the relevant app's status.
8. Mac-as-a-server scenarios
If you have ever enabled File Sharing, run a local web server, hosted a Plex server, or installed Tailscale / Mullvad / a self-hosted VPN exit, your Mac is uploading whenever someone (you or a service) reaches it from outside.
Verify: System Settings → General → Sharing. Anything green there is a service accepting inbound connections — and inbound connections produce outbound responses.
A diagnostic playbook for apps uploading background mac traffic
Here is the step-by-step. It works for any unexplained sustained upload.
Step 1: Confirm the spike is real and from your Mac
Before blaming software, confirm it is your Mac and not another device on the network.
- Check your router's admin panel if you can. Some routers show per-device bandwidth.
- Disconnect every other device temporarily. If the upload disappears, it was not your Mac.
- If your Mac is the source, proceed.
Step 2: Open a per-app bandwidth view
Activity Monitor's Network tab will work, but it is awkward — counters reset on process restart and helpers are scattered. A dedicated tool like ova shows per-app upload rate live, with helpers folded under their parent app.
Sort by upload rate. Identify the top 1 or 2 processes.
Step 3: Match the process to a known category
Use the list above. If the top uploader is:
backupd→ Time Machinecloudd,bird,photoanalysisd→ iCloudDropbox,Google Drive,OneDrive→ that sync clientBackblaze→ cloud backupmdatp,sentineld,falconctl→ enterprise security- A browser → check open tabs, especially webmail, video chat, and cloud IDE tabs
- Something unrecognized → search the exact name; if it is suspicious, that is a different conversation
See ova in action
A glance-able menu bar bandwidth monitor — local, signed, ~3 MB.
Step 4: Pause and confirm
Once you have a suspect, pause it. Most upload-heavy apps have a pause button:
- Time Machine: System Settings → General → Time Machine → "Skip This Backup" or pause
- iCloud Photos: status line at bottom of Photos has a pause button
- Dropbox: menu bar icon → "Pause syncing"
- Google Drive: menu bar icon → "Pause syncing for 1 hour"
- Backblaze: menu bar icon → "Pause backup"
- OneDrive: menu bar icon → "Pause syncing"
If pausing the suspect makes the upload stop, you have confirmed it. If not, your top guess was wrong — go back to step 2.
Step 5: Decide what to do
Three reasonable responses:
- Let it finish. If it is a legitimate first backup or initial photo upload, it is going to upload that data eventually. Faster to let it run.
- Defer to off-hours. Pause now, resume overnight when you do not need the bandwidth.
- Mark the network as Low Data Mode. System Settings → Wi-Fi → (your network) → Details → Low Data Mode. This tells macOS to defer big background uploads on this network specifically.
How to spot upload spikes faster next time
The hard part is noticing the spike at all. A few practices help:
- Keep a per-app bandwidth tool in the menu bar. A glance answers "is anything uploading?" in under a second.
- Watch for the network indicator on the menu bar. Wi-Fi with both arrows active means upload + download.
- Treat sustained upload over 1 Mbps with no obvious cause as a thing to investigate. It is almost always one of the eight categories above.
When the upload is a privacy concern
Most upload spikes are mundane sync. Once in a while, they are not. Things that should make you look harder:
- An unrecognized app uploading consistently
- Any process whose name does not match an app you installed
- Spikes that happen at fixed intervals (suggesting a scheduled job)
- Upload that continues after you quit every visible app
If you suspect malware or unwanted software, check System Settings → General → Login Items & Extensions for anything you do not recognize, and System Settings → Privacy & Security → Profiles for management profiles you did not knowingly install. Persistent unexplained upload from an unknown process is one of the better signals you have that something is wrong.
What to do next
Three actions, in order of usefulness:
- Install a per-app bandwidth monitor like ova so future upload spikes have a name immediately.
- Run through System Settings → General → Sharing and Login Items & Extensions to see what you have given permission to talk to the network.
- Add Low Data Mode to your phone hot-spot SSID and any cafe networks you use occasionally.
Catching apps uploading background mac traffic stops being mysterious once you have the right view. Most of the time the answer is boring — a backup, a sync, a meeting you forgot to leave. Knowing which boring thing it is in five seconds beats wondering for an hour.