Short answer: when iOS says there is not enough space to update, the goal is not to delete as much as possible — it is to free two to three times the size of the update before you start it again. Work in this order: delete the already-downloaded update package, empty Photos → Recently Deleted, offload big apps you never open, remove offline media. On most phones that takes about ten minutes and is enough for a major version.
The error is honest, not a bug: for a short while your phone is asked to hold the old system, the downloaded package and an unpacked copy of the new one at once. The sections below cover what that space is spent on, how much each cleanup move really returns, which popular tricks do nothing or cause damage, and when the borrowed space comes back.
Why an update needs more room than the download
An over-the-air update is not a single file that lands in place. It runs as a sequence, and several steps need disk space at the same time:
- The download. The whole package sits on your phone before anything is installed. A point update is often under 1GB; a major version is commonly several GB.
- Unpacking. The package is compressed, so iOS expands it before installing. That unpacked copy coexists with the download until installation finishes.
- Staging while the old system is still installed. New system files are written before the old ones are removed, so both exist for a while.
- Working room. Swap space for virtual memory, logs and temporary files must stay available throughout the process.
That is where the rule of thumb comes from: an update wants roughly two to three times the package size free. A 5GB update can ask for 10-15GB of headroom. The number in Settings → General → iPhone Storage is not the same thing as one large free block the installer can actually use, which is why a phone with several GB showing can still be refused; the mechanism and the per-capacity figures are set out in the headroom guide at the end of this page.
Where the message appears changes what you do
The same sentence shows up at three different moments, and the correct first move is different in each:
- Before the download starts. iOS refuses to begin. Nothing is half-downloaded and nothing is at risk yet — free space now, then start.
- While the update is preparing or verifying. The download is complete and the unpacking step ran out of room. Deleting the downloaded update reclaims the entire package immediately and is the cleanest reset; then free more and download again. If the screen is sitting there rather than failing outright, that is usually preparation still working rather than a failure — the guide at the end of this page covers a verifying screen that will not move, and restarting it throws away work that was about to finish.
- During installation, with the Apple logo and a progress bar. Do not interrupt this. If it fails here, the phone returns to the update screen; free space before trying again rather than tapping straight away.
What each cleanup move really returns
| Move | What it usually frees | Cost or risk |
|---|---|---|
| Delete the downloaded update in iPhone Storage | Exactly the package size: under 1GB for a point update, several GB for a major one | You re-download it later on Wi-Fi. No data lost, and it is the safest move when the message appears before installation |
Empty Photos → Recently Deleted | Often several GB; tens of GB if you deleted a lot recently | Permanent. Those photos are unrecoverable once the album is emptied, so check it before you clear it |
| Offload large apps you have not opened in weeks | Roughly 0.5-5GB each, occasionally more | Documents and data are kept, but the app must be re-downloaded and some apps ask you to sign in again |
| Delete offline video, music, podcast downloads and cached maps | A few GB, up to 20GB+ if you travel with a library | You re-download it, which costs data and time; rented titles can expire while deleted |
| Turn on Optimize iPhone Storage for iCloud Photos | The biggest single win: tens of GB on a large library | May need a paid iCloud+ tier, and originals must finish uploading first. Never delete local copies before the upload is confirmed |
| Delete and reinstall one cache-heavy messaging app | Often 5-20GB of local cache and attachments | The riskiest move here: history and attachments go with the uninstall unless they are backed up or migrated first |
| Clear attachments inside Messages | Roughly 0.5-10GB | Attachments are deleted permanently, so keep the ones you still need |
The order to do it in
Work down the list and stop as soon as the update has room. There is no benefit in freeing more than you need:
- Delete the downloaded update if you are blocked before installation. It is instant, exact, and fully reversible by downloading again.
- Empty Recently Deleted. Two taps, usually several GB, and it is space you already decided to give up. Open the album first and recover anything you want back.
- Offload the big unused apps. Sort the storage list by size or Last Used and take the top one or two. Offloading keeps your data, so these are cheap gigabytes.
- Remove offline media. Downloaded shows, playlists, podcasts and maps are convenience only, and they are the easiest space to reclaim without losing anything you cannot get back.
- Then photos and videos. Export to a computer, or turn on iCloud Photos with Optimize iPhone Storage. The largest win, but also the slowest to do safely because the upload has to complete.
- Only then, an app reinstall. Effective for cache-heavy apps, but do it after the cheaper moves, and only with chat history backed up or migrated.
- Erasing and restoring is a last resort, not a cleanup step. Exhaust the moves above first.
Steps one to four are a ten-minute job on a modern phone, and they usually return enough for a major iOS update.
What does not work, and what is risky
- Tapping the update again and again. Retrying frees no space. Each attempt can leave a partial download behind, and a download interrupted repeatedly is more likely to fail verification. Free space first, then retry once.
- Deleting System Data. There is no supported way to do it, because it is a reporting bucket rather than a folder — can you clean System Data explains what it actually holds and why the number moves on its own.
- Third-party cleaner or "storage booster" apps. iOS sandboxing means no app can delete another app's files or system files, so they return almost nothing, and the ones that ask you to install a configuration profile want far more access than the job needs.
- "Closing all apps" or clearing RAM. That is a memory action, not a storage action. It frees no space at all.
- Deleting folders in the Files app to empty it. You remove your own documents and app data, not cache.
- Restarting during installation. While the Apple logo and progress bar are on screen, the system is being written. Interrupting that is how an update becomes a damaged installation, which is a far worse problem than a space warning.
- Erase and restore from a backup to gain space. The backup carries the same caches and app data back, so you spend an hour and end at the same number.
- Deleting built-in Apple apps. Some can be removed, but the total saving is small, and the space they hold is not what is blocking a multi-gigabyte update.
When the borrowed space comes back
None of this space is yours to manage, and none of it is lost:
- When installation completes, the staged copy becomes the live system and the old files are released, so the largest chunk returns right away.
- The downloaded package is not always deleted at the same moment. iOS often keeps it for a while and reclaims it later. If the update succeeded and you want the space now, deleting it from iPhone Storage is safe.
- Index and cache rebuilds — Spotlight, Photos, Mail — hold space for a day or two, and longer on a large photo library. This is why free space can look worse after a successful update than before it.
- A restart releases some temporary files immediately, and one night plugged in on Wi-Fi lets the background work finish.
To tell normal from a real problem, check the free-space number once a day rather than every hour. A number that is trending upward means the system is reclaiming, so leave it alone. A number that is still flat or still shrinking after roughly three days means something else is holding the space, and the difference between temporary holding and genuine growth is the subject of the guide at the end of this page on storage that stays full after an update.
Making the next update uneventful
The cheap fix is to free space before the download, not after the failure. Keep 10-15% of the device free as a standing rule, and look at the storage screen before a major version ships rather than on the day it arrives. Then start the update plugged in, on stable Wi-Fi, with the screen off.
If this happens at every update, the honest answer is capacity rather than technique. A phone that cannot hold both a system update and your library needs either more iCloud storage or a larger device; manual cleanup is a fix for the update in front of you, not a maintenance habit worth building your week around.