What Low Data Mode actually does on a Mac
Low Data Mode marks one network connection as expensive and asks macOS and your apps to use less data on it. Apple's Mac help describes it in a single line ("Reduce your data usage over the Wi-Fi network"). The fuller list is in Apple's iPhone and iPad documentation: automatic App Store updates and downloads are turned off, iCloud pauses updates, backups and iCloud Photos, Music stops high-quality streaming and FaceTime lowers its video bitrate. On the Mac you can expect the same kind of restraint from Apple's own software, but Apple does not publish a complete list for macOS.
The setting belongs to a network, not to the whole Mac. Your Mac can treat an iPhone hotspot as expensive while home Wi-Fi stays unrestricted.
It helps to be precise about what kind of feature this is. Low Data Mode is not a throttle, a bandwidth limiter, a firewall or a data meter. It counts nothing, caps nothing and never warns you that you are close to a limit, because it has no idea what your limit is. It is a single on/off flag attached to a network, and its job is to push deferrable work to a later, cheaper connection.
That explains both its strength and its weakness. It works instantly, costs nothing and needs no extra software, and Apple's own services are a large share of the background traffic on a typical Mac. A single deferred macOS update can be several gigabytes that stay off your data plan.
The weakness comes from the same design. Because the mechanism is a flag and not a filter, everything after the flag is voluntary. Section three explains why that matters. Keep it in mind while reading what the mode changes: each item is something Apple chose to make respond to the flag, in Apple's own code.
Where to turn Low Data Mode on
Open System Settings, select Wi-Fi in the sidebar, click Details next to the network you are connected to and turn on Low Data Mode. The switch sits in the same panel as Private Wi-Fi Address and Forget This Network.
The switch belongs to the network, not to the Mac. macOS saves it for that network name, so turning it on for your phone's hotspot leaves your home and office networks untouched. The catch: you can only set it for a network you are connected to or have saved. If you join a new hotspot on every trip, you have to remember to turn it on again for each one.
An iPhone's Personal Hotspot shows up on the Mac as an ordinary Wi-Fi network, so you configure it in the same place. If you connect by cable instead, open that connection's Details under System Settings > Network and check whether it offers the switch. Not every connection type does.
Once it is on, nothing shows it. There is no menu bar icon and no notification, and the only way to check is to open the same Details panel again. That is the feature's biggest usability problem: a setting you cannot see is a setting you forget, both on the hotspot and later at home, when you wonder why your photo library stopped updating.
One common mix-up: Low Data Mode on your iPhone and Low Data Mode on your Mac are separate settings. Turning it on for the iPhone that provides the hotspot reduces the iPhone's own traffic. It does nothing to restrain the Mac connected to it.
What changes when it is on
The biggest and most dependable effect is on updates. On a network marked for Low Data Mode, macOS holds back background downloads of system updates, and the App Store defers automatic app updates and downloads. On a Mac that has been offline for a few weeks, this is usually the largest saving available, because a macOS update or a few large app updates outweigh almost everything else you would do on a hotspot.
iCloud is the second big area. iCloud Photos pauses, so new photos from your phone do not arrive on the Mac and edits made on the Mac wait instead of uploading. Other iCloud sync and backup activity also backs off. That is useful, and it is also the behaviour most likely to surprise you, because paused sync looks exactly like broken sync. If a colleague says a file is not showing up, check whether your Mac is on a Low Data Mode network before you debug anything else.
Apple's other services follow the same pattern and do less in the background. Apps from other developers that use Apple's frameworks for background transfers can also be woken less often for network work, but only where the developer used those frameworks in the expected way.
Just as important is what does not change. Low Data Mode never touches a request you make yourself. A page you open loads in full, a download you start downloads, and a streaming app streams at whatever quality that app picks. Nothing is compressed or proxied. The mode only affects work the system would have done on its own initiative.
And because nothing is measured, you get no feedback. Low Data Mode cannot tell you it saved two gigabytes, because it never counted anything. For many people that is fine. If you are actually working within a data allowance, the missing numbers are where the built-in feature runs out.
The honest part: it is a hint, not enforcement
Under the switch, Low Data Mode is an advisory flag. macOS marks the network path as constrained and tells apps through the Network framework: a path reports isConstrained, a connection can be told through NWParameters to avoid constrained paths, and URLSession has a setting so a developer can say a transfer should not run on an expensive network. macOS sets the flag reliably. It does not police what apps then send.
The consequence is simple. An app that never reads the flag is not affected by it at all. Nothing at system level intercepts traffic from an app that did not opt in. If a developer never wrote the few lines that check whether the path is constrained, their software behaves on your metered hotspot exactly as it does on fibre at home.
That covers a lot of the software people run every day: a browser like Chrome, a sync client like Dropbox, Docker pulling a large image, a game launcher installing a patch, a backup agent starting its scheduled run, an Electron app checking for updates at launch. None of them have to look at the flag, some do not, and none of them tell you either way. Apple's services follow Low Data Mode because Apple wrote them to. Everything else runs on trust.
That is a reasonable design choice. Only the app knows which of its transfers can wait and which cannot, and a system that silently blocked traffic would break software in ways that are hard to diagnose. Cooperation works well when everyone cooperates.
The problem is the apps that do not. The promise depends on every developer whose code runs on your Mac, and you cannot check the result. Failure is silent too: no error, no prompt, nothing in a log you would ever read. You find out when your carrier texts you about your allowance. Per-app enforcement fills exactly that gap, which is why tools like NetMute work at the network layer instead of asking apps nicely.
Closing the gap with per-app enforcement
The other approach is to stop asking apps to behave and decide for them. NetMute is a per-app firewall and traffic monitor for macOS that enforces rules at the network layer, so it does not need an app's cooperation. If a rule says an app gets no network, it gets no network, whether or not its developer has ever heard of constrained paths.
The free version already covers the urgent case on a hotspot: the traffic monitor shows in real time which app is sending how much, and one switch takes any app offline. Temporary rules expire on their own, which is handy when you want to silence something for the next hour rather than for good.
With Pro you get what Low Data Mode cannot do at all. You set daily or monthly data limits per app plus a limit for the whole Mac, get a notification at a threshold you choose, and the app is blocked automatically when it reaches 100 percent. Limits belong to network profiles, so an app can have a tight limit on your hotspot and none at home, and profiles switch automatically by the network you join. Hotspot protection also lets captive portal logins through, so a strict profile does not lock you out of the sign-in page.
That answers the question Low Data Mode leaves open: not whether apps were asked to be careful, but how much each one actually sent.
The fair conclusion is that the two work together. Turn Low Data Mode on: it costs nothing and handles the traffic Apple controls, which is a large share. Then add enforcement underneath for the software that never agreed to the arrangement, so your data allowance depends on a rule you set rather than on how a developer wrote their update checker.