Short answer: "verifying" is not a hang — it is a real preparation step in which iOS unpacks the downloaded update and checks it. On a stable Wi-Fi network, plugged in, with enough free space, it normally finishes on its own. Give it uninterrupted time first; act only when it genuinely stops making progress, and read the section on restarting before you consider one.
The reason this deserves care rather than a quick fix is simple: what you do at this screen decides whether a slow update becomes a failed one.
What "verifying" actually does
The stage you are looking at has several jobs to do before the system is replaced:
- Unpacking the package. The downloaded file is compressed; iOS expands it into the components it will install.
- Checking integrity. The system verifies that the download is complete and matches what Apple published, which is why an interrupted or corrupted download can send it back to the start.
- Preparing to write. It stages data and lines up the space needed for installation.
This work is local, CPU- and storage-heavy, and mostly disk-bound — which is why it can look frozen while the phone is genuinely busy, and why a phone with very little free space can sit at this screen far longer than expected.
How long, and what is normal
| What you see | Reading | What to do |
|---|---|---|
| Progress moves slowly, or pauses and continues | Normal preparation | Leave it plugged in on Wi-Fi |
| A long pause with the screen still showing activity | Still working | Wait; do not tap around |
| It sits for a very long time with no movement at all | Possibly stuck | Check the three conditions below, then restart |
| It fails and returns to Software Update | The download is damaged | Delete and re-download the update |
| A progress bar under the Apple logo | Installation has started | Never interrupt it |
The last row is the important boundary. While the screen shows verifying, you are still in preparation. Once the Apple logo appears with a progress bar, the system is being written, and interrupting that is what actually risks a damaged installation — the recovery route for that situation is in How to force restart a stuck iPhone, and it is a measure of last resort, not a shortcut.
Check the three conditions before touching anything
Most long waits at this screen trace back to one of three conditions. All three are cheap to check.
① A stable connection. Preparation pulls data and checks it against Apple's servers. If the Wi-Fi drops or the phone switches networks midway, the check can stall and restart. Join a stable network, and stay on it.
② Enough free space. Installation and unpacking need continuous free space, not just a few spare gigabytes at the end of the disk. The working rule is to keep 10–15% of storage free; that is the headroom the system needs, and the reason a phone that says "several GB free" can still be blocked. In Settings → General → iPhone Storage you can see where space has gone — and, if an update is already downloaded, remove it to reclaim its space before starting over. The mechanism is explained in Several GB free but "not enough storage"?.
③ Power. Stay plugged in. A long preparation run draws power, and if the battery drops the system may postpone work. Keeping the phone on the charger with the screen off gives it the best conditions.
If all three are fine and it is still not moving, the download is the remaining suspect — continued in the next section.
If it truly stops moving
Work through these in order, and stop as soon as the update proceeds:
① Give it genuinely uninterrupted time. Twenty minutes of a phone left alone is worth more than an hour of tapping the screen to check. Do not open other apps, do not lock and unlock repeatedly, and do not start another download.
② Restart the phone — at this step only, and with the caveat above. Because installation has not begun while the screen says verifying, a restart does not damage the system partition. It does cancel the preparation work, so it is a deliberate choice rather than a harmless nudge. A normal power off and on is enough; the more forceful sequence is in How to force restart a stuck iPhone.
③ Delete the downloaded update and start again. If it failed or stalled at the same point, a fresh download on stable Wi-Fi is usually the fix. Check that you have 10–15% free first — iOS 27 storage full after update covers what to clear, in the order that costs least.
④ Update from a computer. Connecting the iPhone to a Mac or PC and updating from there avoids the phone's Wi-Fi download entirely and is a legitimate alternative when on-device updates keep stalling. Back up first, because this route rewrites the system and a backup is your safety net.
⑤ If it still will not complete, stop escalating. Repeated failed installs are worth a support conversation or a service check rather than more attempts. Do not install profiles, "update repair" utilities or third-party firmware tools — none of them can make an incomplete download complete, and they add risk to a device that is currently recoverable.
Preventing the same stall next time
The conditions that let an update finish are the same ones that stop it from stalling, and they are all cheap to arrange in advance:
- Plug in before starting, and leave the phone charging throughout;
- use stable Wi-Fi rather than a hotspotted or congested connection;
- free up space first, aiming for more than the usual 10–15% headroom before a major update;
- start when you do not need the phone for a while, so a slow preparation step is an inconvenience rather than an emergency;
- if you are still deciding whether this update is for you, the trade-offs are set out in Should I update to iOS 27?, and how long the phone takes to settle afterwards is covered in How long does iOS indexing take?.
The honest summary: this screen rewards patience and punishes curiosity. Check the three conditions, then leave it alone — that is what finishes the update fastest.