Block App Internet Access on Mac
Learn when to block a Mac app, how to avoid breaking expected workflows, and how local firewall rules help keep the decision precise.
Read: Block App Internet Access on MacStart with the built-in Activity Monitor, compare process traffic, then use iNTM when you need app history or connection details.
Written by iNTM · Content updated:
Start with Activity Monitor > Network to compare sent and received data by process. For repeated activity, open iNTM Traffic Monitor, select a time range, compare the app chart, and select the relevant app to inspect its remote connections. Identify the source before deciding to block it.
Open Applications > Utilities > Activity Monitor and select Network. Compare the sent and received data columns by process; sort the relevant column to bring larger amounts to the top.
Note the values, start a file transfer or sync you recognize, and compare again after a short interval. A large accumulated total alone does not prove that a process is busy now. Browser traffic can represent several tabs or helper processes.
For recorded history and remote endpoints, open iNTM Traffic Monitor, choose a time range, and select the relevant app in the chart. Its connection panel shows remote addresses, ports, protocols, and traffic amounts.

Compare the app’s remote domain or IP with the service you were using, then review the same app over another time range. Backups, updates, and cloud sync can explain background activity.
Use the built-in view when a process snapshot answers your question. If a connection is unwanted, follow the blocking guide to create a targeted app or endpoint rule, and confirm that required features still work.
Leave Activity Monitor > Network open, note your browser’s sent and received amounts, and start a file transfer you recognize. Compare the change, pause the transfer, and watch again. This gives you a known cause before investigating background traffic.
Not every traffic spike is suspicious. Cloud sync, software updates, media playback, telemetry, browser tabs, and developer tools can all use bandwidth in the background. The goal is to identify the app first, then decide whether the behavior makes sense.
Before creating a firewall rule, inspect whether the endpoint belongs to a service the app actually needs. Blocking too broadly can break login, sync, update checks, or real-time collaboration features.
Note whether you were uploading, downloading, streaming, or syncing. Compare the same app over the same period, then check its remote endpoint. A process name alone does not identify the purpose of a connection, and browser traffic may cover more than one tab or service.
Apple documents the built-in macOS tools below. iNTM features are described in our product overview. Product
Yes. Activity Monitor’s Network tab shows sent and received data by process and overall network activity. Use iNTM when you need recorded app history, remote connection details, or local firewall rules.
Yes. Activity Monitor’s Network view shows sent and received data by process. iNTM adds app traffic history, remote endpoint details, and local firewall control for a deeper investigation.
Yes. iNTM helps reveal background traffic by showing app-level upload and download activity together with connection details.
Yes. iNTM can create local firewall rules around a specific app, domain, IP address, port, or protocol.
Learn when to block a Mac app, how to avoid breaking expected workflows, and how local firewall rules help keep the decision precise.
Read: Block App Internet Access on MacSee how iNTM connects app traffic, endpoint inspection, and history.
Mac Network Monitor