# How to Use macOS Content Caching to Reduce Network Bandwidth in Offices
When Apple releases a major iOS update or a new version of macOS, corporate networks and school internet connections are frequently crippled. If an office has 200 employees, and everyone’s Mac, iPhone, and iPad simultaneously attempts to download a 5GB software update from Apple’s servers, the network must handle a terabyte of redundant internet traffic.
To solve this, Apple builds a powerful, enterprise-grade feature directly into every Mac: **Content Caching**.
Content Caching turns a designated Mac on your network into a local proxy server for Apple software. When the first device requests an update, an app, or iCloud data, the caching Mac downloads it from Apple, saves a local copy, and serves it to the requesting device. When the next 199 devices request that same file, they receive it instantly over the local Gigabit LAN from the caching Mac, rather than downloading it again from the internet.
This guide explains how to configure macOS Content Caching to drastically reduce bandwidth consumption and speed up deployments.
## Prerequisites for the Caching Server
You do not need a specialized “server” machine to run Content Caching; any modern Mac can perform the role. However, to maximize effectiveness, the chosen Mac should meet these criteria:
1. **Wired Connection:** The Mac must be connected to the network via Ethernet. Serving large files over Wi-Fi will bottleneck your internal network.
2. **Always On:** The Mac must be configured to never sleep. (A Mac Mini is the ideal hardware for this role).
3. **Storage Capacity:** The Mac should have a significant amount of free storage space (at least 200GB, preferably 1TB or more) dedicated to the cache.
4. **Network Position:** The caching Mac must be on the same public IP address (behind the same NAT router) as the client devices it intends to serve.
## Step 1: Prevent the Mac from Sleeping
Before enabling the service, ensure the Mac is always available.
1. Open **System Settings**.
2. Navigate to **Displays > Advanced**.
3. Turn on **Prevent automatic sleeping when the display is off**.
4. (Optional but recommended) Navigate to **Energy Saver** (if using a desktop Mac) and ensure “Wake for network access” and “Start up automatically after a power failure” are enabled.
## Step 2: Enable Content Caching
Apple has intentionally made enabling this enterprise feature incredibly simple.
1. Open **System Settings**.
2. Navigate to **General > Sharing**.
3. Scroll down the list of services and toggle **Content Caching** to the **On** position.
4. Click the **Info (i)** button next to Content Caching to configure its behavior.
## Step 3: Configure Caching Parameters
Within the Content Caching settings, you must define exactly what types of data the Mac is allowed to store.
### Cache Type
You can choose what the Mac caches:
– **All Content:** Caches software updates, App Store apps, and user iCloud data (photos, documents).
– **Shared Content Only:** Caches only software updates and App Store downloads. (Recommended for strict corporate environments where caching personal iCloud data poses privacy or liability concerns).
– **iCloud Content Only:** Caches only user data.
*Select **Shared Content Only** for a standard corporate bandwidth-saving deployment.*
### Storage Limit
By default, macOS will use all available space on the startup drive for the cache, aggressively purging older cached files when space is needed for the user’s personal files.
To prevent the cache from filling the drive:
1. Click the **Options…** button.
2. Use the slider under **Cache Size** to set a hard limit (e.g., 500 GB).
3. If you have an external Thunderbolt or USB 3.0 SSD attached to the Mac, you can click **Edit…** under Cache Location and move the entire cache to the external drive, preserving your internal SSD storage.
4. Click **OK**.
## Step 4: Verify the Cache is Working
Content Caching operates entirely in the background. Client devices (iPhones, iPads, other Macs) on the same network automatically discover the caching server via Bonjour and Apple’s cloud directory. You do not need to configure anything on the client devices.
To verify that the server is successfully intercepting and caching traffic:
1. On the Caching Mac, open the **Activity Monitor** (Applications > Utilities > Activity Monitor).
2. Click on the **Cache** tab at the top. (This tab only appears if Content Caching is enabled).
3. The Activity Monitor will display real-time metrics:
– **Data Served from Cache:** The amount of bandwidth you have successfully saved.
– **Data Dropped:** Data that could not be cached.
– **Data from Origin:** Data the server had to download from Apple because it wasn’t currently in the local cache.
To test it in real-time, grab an iPhone connected to the same network, open the App Store, and download a large app (like GarageBand).
You should see the “Data from Origin” metric spike on the Mac.
Delete the app from the iPhone, and download it a second time. This time, you should see the “Data Served from Cache” metric spike, and the app will download to the phone almost instantly.
## Advanced Configuration: Peering and IP Ranges
For large organizations with complex subnets, Apple provides advanced configuration options via the Terminal command `AssetCacheManagerUtil`.
If your company spans multiple subnets, client devices on Subnet B might not automatically find the Caching Server on Subnet A via Bonjour. You can configure DNS TXT records on your corporate DNS server to explicitly point all clients to the Caching Server’s IP address.
For the vast majority of small-to-medium offices, however, simply toggling the switch to “On” and connecting the Mac via Ethernet is sufficient to drastically reduce internet bandwidth congestion and accelerate Apple device deployments.