iPhone Slow After an iOS Update — What's Actually Happening
Short answer
Give it 24 to 48 hours on charge before changing anything. After an update, iOS rebuilds the Spotlight index, re-optimises every installed app and re-uploads photo analysis data, and all three run in the background using real processor time. If the phone is still slow after two days of normal use, the cause is storage pressure or one misbehaving app, not the update itself.
On this page
Everyone who updates an iPhone and finds it sluggish assumes the update broke something. For the first day or two, it almost certainly did not. iOS has a substantial amount of catching up to do after a version change, and it does that work in the background while you are trying to use the phone.
The useful question is not whether it is slow, but whether it is still slow after the catch-up work has finished. That answer is two days away, and almost every piece of advice people apply in the meantime is wasted effort.
What iOS is actually doing after an update
Three jobs run concurrently, and all three are genuinely expensive.
Spotlight re-indexes everything. Every message, note, email, contact and document gets read and written into the search index. On a phone with years of Messages history this is the largest single task and it is disk-heavy, which is why the phone feels unresponsive rather than merely slow.
Every installed app is re-optimised. iOS compiles parts of each app for the specific device and OS version, and an update invalidates that work. A phone with 120 apps has 120 of these to get through, and they are queued rather than done at install time.
The Photos library is re-analysed. Face recognition, scene classification and the Memories system all re-run against changed models. On a library of tens of thousands of photos this takes the longest of the three by elapsed time, though it is throttled more aggressively than the others.
All of this is heavily throttled when the phone is unplugged and in use, and runs far faster when the phone is locked, on Wi-Fi and charging. Which gives you the single most effective action available: leave it on a charger overnight before drawing any conclusions.
Work out which problem you have
| Symptom | Likely cause | Act now? |
|---|---|---|
| General sluggishness, first 48 hours | Background indexing | No, wait |
| Hot and draining, first 48 hours | Same work, running hard | No, wait |
| Still slow after two days on charge | Storage pressure or an app | Yes |
| One specific app is slow, rest is fine | That app needs updating | Yes |
| Random restarts under load | Battery, not the update | Yes |
The one symptom that is never the indexing period is restarts. A phone that reboots when the camera opens or during a call has a battery that cannot deliver peak current, which is covered in why iPhone battery health drops fast.
Once the waiting period is over
Check free space first
This is the most common real cause, and an update makes it worse by consuming several gigabytes for the installer and keeping the previous system files around temporarily.
iOS needs working room. A phone with under about 10% free space behaves badly in ways that look nothing like a storage problem: apps relaunch instead of resuming, the keyboard lags, photos take a moment to open.
Open Settings → General → iPhone Storage and look at the available figure. If it is small, that is your answer, and the full walkthrough of what is taking up iPhone storage goes through the categories in order of likely payoff. The System Data figure in particular tends to balloon after an update, which the System Data explainer covers.
Update your apps
An iOS release frequently changes framework behaviour, and apps that have not been rebuilt against it can be noticeably slower or crash-prone until the developer ships an update. Open the App Store, tap your profile picture, and update everything.
This is the fix for the case where one app is slow and the rest of the phone is fine.
Restart properly
A restart clears temporary caches, releases memory held by leaked processes, and resets any background task stuck in a retry loop. It is genuinely useful here, unlike most of the advice attached to this problem.
Hold the side button and either volume button until the power-off slider appears, slide it, wait ten seconds, then hold the side button to boot. On older models with a Home button, hold the side or top button alone.
Turn off a few background consumers, if it helps
Worth trying on older hardware, and mostly placebo on recent models:
- Settings → General → Background App Refresh — set to Wi-Fi only, or turn off for apps you do not need updating in the background.
- Settings → Accessibility → Motion → Reduce Motion — replaces the zoom animations with cross-fades. It does not make the phone faster, but it makes it feel more immediate, which on an older device is the complaint being made.
- Settings → Siri & Search — turn off Show in Search for apps you never search for, which trims what Spotlight has to index next time.
What does not help
- Force-quitting every app from the app switcher. Background apps are suspended and consume no processor time. Relaunching them from cold is more expensive than resuming them, so the habit costs performance rather than saving it.
- Cleaner apps. iOS sandboxing prevents any app from reading another app’s files. Nothing installed from the App Store can clear a cache it cannot see.
- Resetting all settings as a first move. It wipes Wi-Fi passwords, keyboard dictionary, wallpaper and privacy permissions, and it has no bearing on indexing work.
- Disabling Spotlight entirely. The indexing happens anyway; you just lose search.
When the update really is the problem
It does occasionally happen, usually with an x.0 release. The symptoms are specific rather than general: a particular feature broken, a consistent crash in one place, Bluetooth or Wi-Fi misbehaving on a model that was fine before.
Apple ships point releases quickly when that occurs, so the practical response is to update again rather than to roll back. Downgrading is only possible while Apple is still signing the previous version, which is typically a short window after a new release, and it erases the phone to do it.
Realistic expectations
A phone two days past an update, left on a charger for at least one night, should feel the way it did before. Most that do not are short of storage, and freeing several gigabytes resolves it within an hour.
What an update will not do is make a five-year-old phone feel new. Each release asks a little more of the hardware, and on an older device the honest outcome is that it runs acceptably rather than quickly. That is worth knowing before spending a weekend on it.