# What Is mobileassetd on Mac and Why Is It So Busy After an Update?

> mobileassetd downloads fonts, voices, language data and Apple Intelligence models. Why it spikes after updates, how to see what it fetches, what not to delete.

Published: 2026-11-10 | Updated: 2026-11-14

mobileassetd is the macOS daemon that downloads and maintains the parts of the system that are not built into the main install: fonts, dictionaries, Siri and dictation voices, linguistic data, Apple Intelligence models, software update data and, for developers, Xcode's simulator runtimes and documentation. It runs from `/usr/libexec/mobileassetd` as root and sits near 0% CPU most of the time. When it gets busy, it is usually right after a macOS update or right after you turn on a feature or language that needs new data, and it settles once those downloads finish.

## What it does

Apple calls these downloadable pieces mobile assets. Rather than ship every voice and language model with macOS, the system fetches them when a feature needs them and replaces them when Apple publishes a newer version. mobileassetd is the process that checks for them, downloads them, verifies them and removes old copies.

Its launchd job, `/System/Library/LaunchDaemons/com.apple.mobileassetd.plist`, shows two scheduled tasks: a repeating asset scheduler set to a four-hour delay at maintenance priority, and a daily health report that waits for mains power and a network connection. On the Mac used for this page, after almost four days of uptime, it looked like this:

```text
root  479  0.0% CPU  27 MB  /usr/libexec/mobileassetd
CPU time used since boot: 1 min 6 s
```

A helper, `com.apple.MobileAsset.DownloadService.Builtin`, runs beside it and does part of the transfer work, so search Activity Monitor for both names.

## Why it spikes after an update

A new macOS version often comes with new versions of the assets, so mobileassetd catches up over the following hours. The same thing happens when you:

- turn on Apple Intelligence, which downloads the on-device models ([what that storage is](https://mole.fit/blog/apple-intelligence-storage-mac));
- add a language, a keyboard, a dictation language or a spoken voice;
- install Xcode or a new simulator runtime;
- connect to the network after a long time offline.

A slow or interrupted connection stretches this out, and so can a nearly full disk, since a download has to land somewhere before it is unpacked.

## See what it is downloading

The unified log names each asset type. This counts which types mobileassetd mentioned in the last hour:

```bash
/usr/bin/log show --last 1h --predicate 'process == "mobileassetd"' \
  | grep -o 'com_apple_MobileAsset_[A-Za-z0-9_]*' | sort | uniq -c | sort -rn | head
```

Use the full `/usr/bin/log` path: zsh has a built-in command called `log` that answers `too many arguments` instead. Over six hours on this Mac, the types mentioned most were the Metal toolchain, a music asset for video apps, fonts, developer documentation and linguistic data. The names are usually readable enough to tell you which feature asked.

For the network side, Activity Monitor's **Network** tab shows bytes received under its name. Rising received bytes followed by falling CPU usually means the job is making progress.

| You see | Likely cause | Try |
| --- | --- | --- |
| High CPU for hours after a macOS update | New assets for the new version | Keep the Mac on power and Wi-Fi and let it finish |
| A spike after turning on a feature or language | That feature's models or voices | Let it finish, or turn off what you don't use |
| Heavy traffic on a phone hotspot | First-time downloads | Wait until you are on regular Wi-Fi |
| Busy for days, same bursts again and again | Downloads failing and retrying | Check free space, finish any pending update, restart |
| Busy whenever Xcode or a simulator opens | Developer documentation or runtime assets | See [cleaning up the iOS Simulator](https://mole.fit/blog/how-to-clean-up-ios-simulator-mac) |

## Where the assets live

Most downloaded assets sit in `/System/Library/AssetsV2`, one folder per asset type. You can measure it without changing anything:

```bash
du -sh /System/Library/AssetsV2
du -sk /System/Library/AssetsV2/* 2>/dev/null | sort -rn | head
```

On this Mac the folder held 94 entries and `du` reported 22 GB, which is an undercount, because four folders, the Apple Intelligence model folders among them, returned `Operation not permitted` even to a read. The largest readable folders were:

```text
7.33 GB  iOSSimulatorRuntime
3.23 GB  AppleDeveloperDocumentation
2.35 GB  UAF_Siri_Understanding
1.76 GB  UAF_LinguisticData
1.50 GB  MacSoftwareUpdate
1.08 GB  Font8
```

A developer Mac looks very different from one without Xcode. The folder is flagged `restricted`, which means System Integrity Protection guards it, and update data can also appear under `/System/Volumes/Update/MobileAsset/AssetsV2`.

## Can you quit or stop it

You can end it in Activity Monitor, but launchd starts it again and the downloads resume later, so quitting only delays them. There is no supported switch for the process. What you control is the demand:

- remove voices you do not use in **System Settings › Accessibility › Read & Speak** (**Spoken Content** on earlier versions), where the info button next to **System voice** lists them;
- remove languages you no longer need in **System Settings › General › Language & Region**;
- finish any pending update in **System Settings › General › Software Update**.

## What not to delete

- Do not delete anything under `/System/Library/AssetsV2`. SIP blocks it, and if you did get around SIP, the features that use those assets would break and macOS would download them again.
- Do not disable SIP to clean this folder. The space you would gain comes back, and the protection you turned off does not.
- Do not remove simulator runtimes from that folder by hand. Use Xcode or `xcrun simctl runtime delete`, so CoreSimulator updates its own records.
- Do not treat a CPU spike as malware. The real binary is signed by Apple with the identifier `com.apple.mobileassetd`; check with `codesign -dv /usr/libexec/mobileassetd`.

## Where Mole fits

[Mole](https://mole.fit/) lists `mobileassetd` in **Status** with its CPU and memory when it is busy, and the table's search finds it when it is not. **Why is this running?** in its menu shows the executable and the launchd service that started it. Because it runs from a system folder, Mole shows no **Terminate** or **Force Quit** for it. Mole does not list or remove anything inside `/System/Library/AssetsV2`. The one exception is Xcode simulator runtimes: Clean can list them as **Xcode Simulator Runtimes**, and it removes a runtime you choose through `simctl`, Apple's tool, never by deleting files. For the wider picture after an update, see [why a Mac is slow after a macOS update](https://mole.fit/blog/mac-slow-after-macos-update).

## FAQ

### What is mobileassetd on Mac?

It is the system daemon that downloads and updates extra system content such as fonts, dictionaries, voices, language data and Apple Intelligence models. It runs from `/usr/libexec/mobileassetd`.

### Why is mobileassetd using so much CPU?

It is downloading, verifying or unpacking assets, most often after a macOS update or after you turn on a feature or language. It calms down once those downloads finish.

### Can I delete /System/Library/AssetsV2?

No. System Integrity Protection guards it, the features that use those assets depend on it, and macOS downloads them again. Reduce it by removing voices, languages or features you do not use.

### Can I quit mobileassetd?

You can, but launchd restarts it and the downloads resume later. Leaving it to finish on power and Wi-Fi is the quicker way out.

### Why does mobileassetd use so much data?

First-time downloads, such as a new macOS version, Apple Intelligence models or a new language, can be large.

---

Canonical HTML page: https://mole.fit/blog/mobileassetd-mac
Blog index for agents: https://mole.fit/blog/llms.txt
Site index for agents: https://mole.fit/llms.txt
