If content caching is not working on Mac, start with System Settings > General > Sharing on the cache Mac. Confirm that Content Caching is on, the indicator is green, and the selected cache mode matches what your other Apple devices need.
If the Mac content cache is not showing up, do not clear the cache first. A sleeping host, delayed client discovery, unsupported network addressing, limited storage or a management restriction can all make a healthy cache appear broken.
Start with the Content Caching settings
On the Mac intended to provide the cache, open Apple menu > System Settings > General > Sharing. Turn on Content Caching, then open its information or options panel. Wait for the status indicator to settle before testing another device.
Apple uses the indicator to show the broad service state:
| Indicator | What it suggests | What to do |
|---|---|---|
| Green | Content Caching is on | Test a client and check activity evidence |
| Yellow | The service is unavailable or starting or stopping | Wait briefly, then check settings and host availability |
| Dark grey | Data is being moved | Let the move finish before judging the cache |
| Light grey | Content Caching is off | Turn it on if this Mac should provide cached content |
The labels and appearance can vary slightly between macOS releases. Apple’s Content Caching settings guide is the right reference for the version installed on the Mac.
Next, check the content selection. The available choices are All Content, Only Shared Content and Only iCloud Content. Shared content covers software and app downloads distributed by Apple. iCloud content includes users’ iCloud items, such as photos and documents.
| Setting | Suitable when clients need | Not a complete match when |
|---|---|---|
| All Content | Both Apple software or app downloads and iCloud content | You deliberately want to exclude one category |
| Only Shared Content | Apple software and app downloads | Clients mainly need iCloud content |
| Only iCloud Content | Users’ iCloud content | Clients need software or app downloads cached locally |
Choosing Only Shared Content will not make the Mac cache iCloud items. Choosing Only iCloud Content will not provide the shared software and app content you expected. If you change this selection, restart a test client to prompt a fresh discovery attempt.
Apple states that iCloud cache data is received, stored and transmitted in encrypted form, and that the cache cannot decrypt it. Turning iCloud caching off removes cached iCloud data from the cache immediately, so treat that setting as an operational change rather than a harmless test.
Give clients time to discover the cache
Apple devices discover caches automatically through Apple’s lookup service. This means you normally do not enter the cache Mac’s address manually on every client. It also means that a newly enabled or changed cache may not be visible straight away.
Restarting a client device prompts immediate discovery. If you do not restart it, Apple says the device can take some time to notice the change. During that period, it may use another available cache or download directly from Apple. That behaviour does not prove the new cache is malfunctioning.
This distinction explains many reports of “Mac content cache not showing up”. The service may be available, while the client is still using an earlier discovery result. Test with one client first, restart that client, and then observe whether a later download produces activity on the cache Mac.
A useful sequence is:
- Confirm Content Caching is green on the host Mac.
- Confirm the client and host are on the network you expect.
- Restart one client rather than changing several settings at once.
- Repeat a suitable Apple download or update request.
- Check the cache activity view for evidence that data was served.
Do not interpret a single direct download as proof that caching is unavailable. A client may not have discovered the cache yet, the selected cache mode may not include the requested content, or the requested item may not be available for caching in the way you expect.
The same habit helps when a Mac is part of a larger content workflow. If you are using it to prepare media for an always-on channel, keep the local troubleshooting separate from the publishing workflow described in how to run a devotional YouTube stream from a cloud server. A problem with Apple’s cache does not itself indicate a problem with YouTube delivery.
Check whether the cache Mac is awake
Content Caching works only while the Mac is awake. If the host sleeps overnight, clients cannot use it during that period, even if the Sharing setting remains enabled and the cache files are intact.
Check the status indicator before changing storage, DNS or advanced settings. If the Mac is asleep, wake it and test again. For a Mac that operates without someone using its screen, review the Mac’s energy settings and the local policy governing sleep. Avoid assuming that closing a laptop lid, disconnecting a display or leaving the Mac logged out has the same effect on every model and macOS release.
Apple points administrators towards the caffeinate command-line utility when a Mac must remain awake for a task. Before using it in production, check the current Apple guidance on changing Content Caching settings and confirm that keeping this particular Mac awake fits your power, heat and maintenance requirements.
A permanently awake Mac is not automatically a good cache host. It still needs adequate storage, a supported network arrangement and permission to run the service. Treat awake status as one checkpoint in the diagnosis, not as a complete fix.
For a small office, write down the intended role of the machine. Is it a Mac used by someone during the day, a shared desktop, or a dedicated host? If it is also used to create a 24/7 stream, separate the duties where possible. Guidance on OBS settings for a 24/7 YouTube stream in India may help with the publishing side, but it does not replace Apple’s requirements for Content Caching.
Check network addressing and scope
Apple documents a specific addressing requirement for content caches. Each cache should have either a local IP address in RFC 1918 private address space, or a non-RFC 1918 local address that is identical to its public IP address. Apple says caching is unsupported when a non-RFC 1918 local address differs from the public address.
The private ranges listed in Apple’s documentation are:
10.0.0.0to10.255.255.255172.16.0.0to172.31.255.255192.168.0.0to192.168.255.255
These are configuration ranges, not performance figures. Check the address assigned to the cache Mac and compare it with the way the site connects to the wider network. Do not assume that every address beginning with 172 is private; the documented private range begins at 172.16 and ends at 172.31.
In a managed or multi-subnet network, also check whether settings such as Local Subnets Only, listen ranges, peer or parent configuration and DNS discovery are intentionally limiting which clients can find or use the cache. A cache can be healthy for one subnet and unavailable to another because of site policy or routing.
There is no universal router or firewall change that fixes every discovery problem. The correct setting depends on the network layout, address allocation, DNS and management policy. If you do not administer those parts of the network, give the network administrator the cache Mac’s address, client subnet, current Content Caching status and the time of a failed test.
Apple’s deployment documentation for Content Caching explains automatic discovery and client fallback. Read it alongside your actual network design rather than copying a setting from a different site.
Check storage, cache location and limits
A cache can be available but unable to retain useful content because its selected volume is full or its configured cache limit is too restrictive. Open the Content Caching options and inspect the selected volume, available space, configured limit and storage already used.
When multiple volumes are available, macOS lets the administrator select a cache volume. Apple also allows a cache-size limit to be set. Content can be removed to make room when the configured limit or available space on the chosen volume is reached. That eviction is not necessarily corruption.
A practical check is to record four things before resetting anything:
- The volume currently selected for caching.
- The free space on that volume.
- The configured cache-size limit.
- Whether the requested content belongs to the selected cache mode.
If the cache location is being moved, caching stops temporarily while the data moves. Wait for the move to finish before testing. Interrupting a storage change and immediately starting unrelated troubleshooting can leave you unsure which condition affected the result.
An external SSD is optional. It can make sense when the Mac has a separate, suitable volume and the existing internal storage is needed for other work. Apple’s documentation supports selecting another available volume; it does not say that an external drive is necessary, or that one will fix client discovery, sleep or unsupported network addressing.
If the Mac is also a media workstation, avoid placing a cache on a volume that is already close to full because of recordings, exports or source files. For example, a person preparing clips for adding new podcast episodes to an always-on YouTube stream should check whether the same disk is being used for both episode production and cached Apple content.
Check management restrictions
On an organisation-managed Mac, a user-level toggle may not control the final result. A configuration profile or declarative management setting can prevent Content Caching from being activated or can control how it behaves.
If the setting is unavailable, keeps reverting, or appears enabled but does not activate, ask the administrator to inspect the applicable management configuration. Check whether the Mac is enrolled, which profile applies to it, and whether the device is intended to act as a cache host at all.
Do not try to defeat a restriction by repeatedly switching the service off and on. User-level changes cannot override a policy applied by device management, and repeated changes make the resulting logs harder to interpret.
Management can also affect network scope, storage choices and whether the Mac may serve clients across particular subnets. If a cache works on an unmanaged test Mac but not on the managed host, treat the policy difference as evidence worth investigating, not as proof that the cache data is damaged.
Verify activity before clearing the cache
When you ask “how do I clear the Mac content cache?”, first establish whether clearing it is necessary. Activity Monitor has a Cache view that shows Data Served and Data Served From Cache. Apple says non-zero served values indicate that the cache is working.
If the Cache view is absent, Apple advises enabling Content Caching and reopening Activity Monitor. Test with content that matches the selected mode, then check the figures again. A cache that has served nothing may simply have had no eligible request from a discovered client.
For administration, Apple documents these AssetCacheManagerUtil checks:
AssetCacheManagerUtil settings
AssetCacheManagerUtil status
AssetCacheManagerUtil canActivate
AssetCacheManagerUtil isActivated
It also documents operations including activate, deactivate, reloadSettings, flushCache, flushPersonalCache and flushSharedCache. The exact command behaviour and available options can depend on the macOS release, so verify the command list against the installed version. Apple’s command-line guide is useful for administrators, but it should not be treated as permission to change undocumented plist keys.
Advanced logs use the com.apple.AssetCache subsystem and can be viewed in Console or through the log command. Look at the time of a controlled test and correlate the host status, client restart, requested content and network path. A log line without that context is rarely enough to identify the cause.
Flushing removes cached content and causes it to be fetched again when needed. It does not normally fix a sleeping host, delayed client discovery, unsupported addressing or a management restriction. Use a flush when you have a reason to remove the stored content, not as the first response to every “content caching not working on Mac” report.
Use a short, repeatable diagnosis
When the cache fails overnight, use the same order each time so that a simple state problem is not confused with damaged data.
First, record the time and the client that failed. Then check the host’s status indicator, whether the Mac was awake, and whether the client was restarted after a setting change. Confirm that the requested content belongs to the selected mode. Only then inspect the host address, subnet scope, storage and management controls.
For a small site, keep a brief test record with these fields:
| Check | Result to record |
|---|---|
| Host status | Green, yellow, dark grey or light grey |
| Host availability | Awake or asleep during the test |
| Client discovery | Restarted, or allowed time to discover |
| Content type | Shared, iCloud or both |
| Network path | Client subnet and host address |
| Storage | Selected volume, free space and configured limit |
| Activity | Data Served and Data Served From Cache |
| Policy | Relevant management profile or restriction |
This method gives you a useful escalation note if the issue needs help from an administrator. It also prevents a common mistake: clearing the cache, seeing a later successful download and assuming the flush fixed discovery. The later success may instead have followed a client restart, the end of a move, the host waking, or a delayed lookup.
If the Mac is not the right operational host for another always-on task, document that separately. A locally maintained stream may need a different arrangement, such as the workflow discussed in how to restart a YouTube stream automatically if FFmpeg stops on Hetzner. Content Caching and live-stream continuity solve different problems.
Once the cache is working, review it occasionally rather than changing settings after every direct download. Look for a consistent relationship between client requests and served activity, and keep the host awake and within the intended network scope.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
Why isn’t my Mac using the content cache?
Check that Content Caching is enabled and green, the host Mac is awake, and the selected mode includes the content being requested. Restart the client to prompt discovery, then check Activity Monitor for Data Served and Data Served From Cache.
What should I do if the Mac content cache is not showing up?
Restart one client after enabling or changing the cache, because discovery can otherwise take some time. If it still does not appear, check the host address, subnet restrictions, DNS discovery and any management policy before clearing stored data.
How do I clear the Mac content cache?
Use the documented AssetCacheManagerUtil flush operation or the reset control in Content Caching settings, after checking activity and storage first. Clearing content makes it get fetched again as needed and does not repair sleep, network addressing, discovery delay or administrative restrictions.
Can an external drive fix content caching issues on a Mac?
An additional volume can provide a suitable place for cached data when the current volume lacks space. It will not, by itself, fix an unavailable service, a sleeping host, an unsupported address arrangement or a policy that prevents caching.