How to Restore an iPhone From a Backup

Published August 20, 2026 · Last reviewed September 2, 2026

Choosing the method

The encrypted-backup detail matters. A computer backup only includes saved passwords, Wi-Fi settings, Health data, and call history if you tick Encrypt local backup. An unencrypted computer backup will restore your apps and leave you signing into every one of them by hand.

Before you start

Action

Take a fresh backup and confirm the timestamp updated.

Why it helps

Restoring to yesterday's backup means losing today. The confirmation matters more than the action.

Verification

Last Successful Backup shows a time within the last few minutes.

Action

Note anything two-factor — authenticator apps, banking apps — and check each one's transfer process before you wipe or hand over the old phone.

Why it helps

Some authenticator apps do not migrate in a backup, and losing them can lock you out of accounts entirely.

Verification

You have either transferred the authenticator or written down recovery codes.

Action

Keep the old phone until the new one is fully verified, and do not erase or trade it in the same day.

Why it helps

A restore that misses something is recoverable while the source device still exists; afterwards it is not.

Verification

The old phone is intact and still holds its data.

Action

Ensure enough iCloud storage if you are restoring from an iCloud backup.

Why it helps

A backup that never completed is not a backup, and this is the moment that failure becomes visible.

Verification

The backup you intend to restore appears in the list with a recent date and a plausible size.

What restores, and what arrives separately

A restore is not a single event. The backup itself brings your settings, home screen layout, Messages, and app data. Then a second wave arrives over hours: apps re-download from the App Store, iCloud Photos re-syncs, Music and Podcasts re-download, and iCloud Drive files pull down on demand. The phone is usable quickly and complete a day later.

Things that do not come from the backup at all:

• Passwords — these come from iCloud Keychain when you sign in, or from an encrypted computer backup.
• Apple Pay cards — re-add manually; card details never leave the original device.
• Face ID and Touch ID — must be re-enrolled.
• Some authenticator apps — check each one's migration process before wiping the old phone.
• eSIM — usually needs transferring, either during setup or via your carrier.
• Content from streaming apps — offline downloads are re-downloaded, not restored.

Verifying the restore

1. Open Messages and check a conversation from several years ago, not just a recent one.
2. Open Photos and confirm the total count roughly matches, then wait for syncing to finish before judging.
3. Open two or three banking or authenticator apps and confirm you can still sign in.
4. Check Wi-Fi connects automatically at home, which tells you settings came across.
5. Confirm the eSIM or SIM is active and you can make a call.

If the restore stalls

A restore that appears stuck is usually still working — large libraries take hours. Leave it on Wi-Fi and power overnight before intervening. If it genuinely fails, restarting the restore from the same backup is safe. The one thing not to do is erase the old phone while the new one is still incomplete.

How it works

A restore rebuilds the device in layers, and understanding the layering is what stops people panicking mid-way. The backup contains your settings, app data, and layout — but not the app binaries themselves, because those can be fetched from the App Store. So iOS first applies settings and data, then queues every app for download, then lets each app open its restored data container. This is why a freshly restored phone shows the right home screen with greyed-out icons: the arrangement came from the backup, and the apps are still arriving.

A second, separate wave comes from sync services rather than from the backup at all. iCloud Photos, Contacts, Notes, iCloud Drive, and Keychain are not inside the backup file; they live in your account and re-populate once you sign in. This is also why photo counts look wrong for a day and then correct themselves, and why passwords appear without ever having been in the backup.

Direct transfer is the most complete method because it copies the device state peer-to-peer rather than reconstructing it, which avoids both the storage limit and the upload step. Its cost is that both phones are occupied for the duration. The encryption difference in computer backups exists for a security reason: credentials, Health data, and call history are only written into a backup that is itself encrypted, so an unencrypted local file cannot leak them if it is copied.

Worked example

Moving from a four-year-old iPhone with 84 GB used to a new one, using iCloud Backup because the old phone's screen is cracked and Quick Start pairing is unreliable.

The preparation catches two problems that would otherwise have been discovered too late. First, the last successful iCloud backup is eleven days old, because the storage plan is 200 GB and the account is nearly full. Freeing space and running a manual backup takes 40 minutes and produces a backup timestamped that morning. Second, the authenticator app in use does not migrate through a backup; recovery codes for four accounts are exported to a password manager before anything else happens.

The restore itself takes 55 minutes to reach a usable home screen, and about six hours before every app has finished downloading. Photos reports 31,400 images against roughly 34,000 expected — which resolves itself by the following morning as iCloud Photos completes.

Verification finds one genuine gap: the eSIM did not transfer and needs a five-minute call to the carrier. Messages from 2021 are present, Wi-Fi connects automatically, banking apps sign in, and the authenticator is re-established from the exported codes. The old phone is kept, untouched, for two weeks before being traded in — which is the step that would have made any missed item recoverable.