Why is mobileassetd using so much CPU on my Mac?

mobileassetd is part of macOS. It downloads, unpacks and updates the extra pieces macOS and Apple’s apps fetch on demand instead of shipping in the installer: Siri voices and speech recognition, translation and dictation languages, fonts, dictionaries, wallpapers, on-device models and, if you use Xcode, simulator runtimes. High CPU from it means one of those is arriving, usually right after a macOS update or after you turn on a feature that needs one. It settles once the download is unpacked.

Updated November 18, 2026. Checked against Apple’s support pages and Multimeter 1.1.

What mobileassetd is

The program lives at /usr/libexec/mobileassetd, next to other macOS background processes, and belongs to Apple’s MobileAsset system, the same one iPhone and iPad use (hence the name). What it fetches is kept in /System/Library/AssetsV2, one folder per kind of asset, named like com_apple_MobileAsset_Font8 or com_apple_MobileAsset_DictionaryServices_dictionaryOSX.

On the Mac we wrote this on (macOS 27, Xcode 27.1), that folder had 134 kinds of asset and took 73 GB. 64 GB of it was Xcode’s simulator runtimes: 39 GB for iOS, 13 GB for watchOS, 7.6 GB for visionOS and 4.2 GB for tvOS. Siri, speech and language data added up to about 3.5 GB, and Xcode’s developer documentation another 1.6 GB.

The one-minute check

  1. In Activity Monitor (Applications, Utilities), click CPU and type mobileasset in the search field. You may also see helpers named like com.apple.MobileAsset.DownloadService. The Mac’s own mobileassetd runs as root; while an iPhone or iPad simulator is running you’ll also see copies under your user name, which belong to the simulator.
  2. Click the Network tab. Apple says it lists how much each process has sent and received; a large Rcvd Bytes number for mobileassetd means it’s downloading.
  3. To see where the space goes, open Terminal and run du -sh /System/Library/AssetsV2/* | sort -h | tail. The last lines are the biggest kinds of asset.

Common causes, and what to do

A macOS update just finished

After an update, macOS refreshes the assets that go with it, so mobileassetd often runs for a while next to Spotlight reindexing and photo analysis.

What to do: leave the Mac awake, plugged in and online for an hour or so. It finishes on its own.

You turned on a feature that needs a download

A new Siri voice, a dictation or Translate language, a downloadable font, Apple Intelligence: each arrives as an asset, so turning one on starts a download and an unpack.

What to do: let it finish. The feature’s own setting usually says when it’s ready.

Xcode is downloading a simulator

Simulator runtimes are the biggest assets by far, several gigabytes each, and Xcode fetches them through the same system after an Xcode update or when you pick a new platform.

What to do: to see and remove them, open Xcode, Settings, Components. In Terminal, xcrun simctl runtime list shows them with their sizes, and xcrun simctl runtime delete --notUsedSinceDays 30 --dry-run shows what a cleanup would remove before you run it without --dry-run.

What not to do

  • Don’t force quit mobileassetd. macOS starts it again, and the download starts over.
  • Don’t delete folders in /System/Library/AssetsV2 by hand. Features that rely on them stop working until macOS downloads them again. Remove simulators from Xcode, and turn off the feature (a voice, a language) to give back its space.
  • Don’t count on Finder for the total. Storage settings file most of this under System Data. See Why is my Mac storage full?

Multimeter keeps the totals in the menu bar, so you can tell a big download from a stuck Mac without opening Activity Monitor:

  • CPU: total use across all cores, every 3 seconds on power and about every 6 on battery. Yellow above 70%, red above 90% by default.
  • Network speed: total download per second across Wi-Fi and Ethernet. A multi-gigabyte asset shows up as a long, steady download.
  • Disk space: how full the startup disk is, counting space macOS can free on its own as free, like Finder. A simulator download moves it by gigabytes.

Multimeter’s built-in meters show totals for the whole Mac, not processes, so they won’t say the CPU is mobileassetd. If you want the name too, the Busiest process recipe is a Script meter that shows the top process name and its % CPU. Five live meters use about 3% CPU, and they pause while the displays sleep.

Multimeter is $19.99 once, no subscription, for macOS 13 or later. Get Multimeter

How you know it’s done

mobileassetd sits near zero in Activity Monitor, its Rcvd Bytes stop climbing in the Network tab, and the feature you turned on says it’s ready.

Questions

What is mobileassetd on Mac?

Part of macOS, at /usr/libexec/mobileassetd. It downloads and unpacks assets macOS and Apple’s apps fetch on demand, such as voices, languages, fonts, dictionaries, models and Xcode simulator runtimes.

Is mobileassetd a virus?

No. It is a macOS background process. The Mac’s own copy is /usr/libexec/mobileassetd and runs as root; copies under your user name come from a running Xcode simulator.

Where does mobileassetd store its downloads?

In /System/Library/AssetsV2, one folder per kind of asset. Run du -sh /System/Library/AssetsV2/* | sort -h | tail in Terminal to see the biggest.

Why is /System/Library/AssetsV2 so big?

Usually Xcode simulator runtimes, several gigabytes each. On our test Mac they were 64 of its 73 GB. Remove the ones you don’t use in Xcode, Settings, Components, or with xcrun simctl runtime delete.

Can I stop mobileassetd?

Not for long: macOS restarts it, and the download starts over. Let it finish, or turn off the feature that asked for the download.

Can Multimeter show mobileassetd?

Its built-in meters show total CPU, network speed and disk space, not processes. The Busiest process recipe, a Script meter, shows the top process name and its % CPU in the menu bar.

Sources

Next

Put it in your menu bar

$19.99 one-time. No subscription. Needs macOS 13 Ventura or later.