Why some apps can't be moved
Storage Studio won't move apps that macOS or their updater would break or undo, such as built-in apps, Apple-signed apps and apps that are open. Here is each reason in plain English, and what you can do instead.
Storage Studio won't move an app when the move could break it, or when macOS or the app's updater would quietly undo it. Those apps carry a Blocked badge and have no Move button. A few more carry Override, which means you can move them, but only after reading the specific risk. The reason is always written under the app's name on the Internal tab.
Apps that are blocked
| What the row says, in short | Why it's blocked |
|---|---|
| Storage Studio cannot relocate itself | It needs to stay where it is to do its job |
| System app | Apps built into macOS are protected by macOS itself |
| Already relocated | It's on your drive already. Use the Moved tab to bring it back |
| Apple-signed app | macOS or the App Store may update it where it was installed, undoing the move |
| Currently running | An open app can't be copied safely |
| Setapp | Setapp re-downloads apps it thinks are missing |
If it's only running, quit the app, click Refresh, and its badge is worked out again.
Apps that need an override
These can be moved after you click Override → Move and confirm. The sheet names the exact risk:
- Installed by macOS (system-owned). The app was put there by an installer as a protected app. Moving it needs your administrator password, and if it came from the App Store, its updates may not follow it to your drive.
- An updater that reinstalls apps. Some updaters put a new copy back where the app used to be. Storage Studio watches for this and redoes the move. See Apps that update or reinstall themselves.
- Fixed locations inside the app. Parts of the app point to its original location, so they may look in the wrong place after a move.
- A helper tool or background item. The app installed something that starts by itself and expects the app at its original location. It may not start if your drive isn't connected yet when you log in.
Flowchart outline: What you can do when an app can't be moved
- The app has no Move button
- leads to Is it only because the app is open?
- Is it only because the app is open?
- Yes: leads to Quit it, click Refresh, then Move
- No: leads to Do you still use the app?
- Do you still use the app?
- Yes: leads to Leave it on your Mac
- Rarely: leads to Offload it
- No: leads to Uninstall it
Reasons that appear when you click Move
A move can also stop at the last moment, with the reason shown at the bottom of the window. Nothing is changed when this happens:
- Your drive isn't set up for Storage Studio yet. Run the Setup Wizard first. See The Setup Wizard.
- There's already a copy on the drive with the same name.
- File names that differ only in capital letters. If the app contains two files whose names differ only in capitals, and your drive treats capitals differently from your Mac, those files would clash on the drive.
- You cancelled the password prompt for an app installed by macOS.
What you can do instead
- Offload is offered for every app, including blocked ones, as long as your drive is connected. It archives the app and its data on your drive. If an offload fails twice for the same app, its button changes to Can't offload and the reason is shown on the row.
- Uninstall is also offered for every app on the Internal tab, and everything it removes can be put back.
See also: App safety levels · Moving an app to your external drive · App safety level