Identify data that has no independent copy
Make an inventory of photos, downloads, voice notes, device-only documents, messaging media, authenticator access and app data. A phone can show a working cloud account while an individual app still stores important material locally. Check the storage location of each item that would be hard to recreate.
For each important category, make a copy that can be opened from another device or computer. A cloud icon or “sync enabled” label is not enough; open a representative file from the destination and confirm that the actual content is there.
Prove that photos, files and messages have synchronized
Check the last successful backup or sync timestamp, then use a computer or separate device to open representative photos, files and important messages where the service permits it. Files listed as pending, stored only in Downloads or held inside an app may not be covered by the device’s general cloud-backup indicator.
Also confirm that your recovery email, recovery phone, passkeys, security keys, or second trusted device still work. The account data may remain perfectly safe in the cloud while you are locked out of it, which is why access recovery belongs on the backup list.
- Transfer authenticator access before the reset.
- Keep backup codes off the device being erased.
- Test at least one independent recovery route while the current session still works.
Protect sign-in credentials before the reset
Check whether your authenticator app supports secure migration or backup, and verify the recovery process for the accounts it protects. Keep provider-issued backup codes and a working alternate sign-in method somewhere safe outside the phone. Do not rely on an untested screenshot or a second factor that will disappear with the reset.
This is also the place to check folders created by messaging or editing apps. Those files can sit outside the obvious photo library and are easy to miss in a quick “photos are backed up” review.
Check app-specific backups rather than assuming device backup covers them
Open the backup or export settings inside messaging apps, password managers and any software that stores work locally. Confirm what is included, which account receives it and whether it can be restored on the intended replacement phone. Record the steps for apps that require a manual transfer or separate export.
If the phone is being sold or transferred, follow the manufacturer’s ownership-transfer instructions and confirm that the next owner will not be blocked by your account state.
Separate billing and account ownership from local data removal
Erasing a phone does not automatically end mobile service, app subscriptions or family plans. Write down which account owns each paid service and preserve purchase evidence you may need to reinstall apps or regain access. Cancel or transfer a service independently only if that is part of your actual plan.
This distinction prevents a common false assumption: an empty phone can still be tied to active cloud services, licences, and recurring payments.
Use a stop rule if restoration has not been verified
Before pressing Erase, confirm at least one external copy of irreplaceable data and a tested method of signing in again. Review the backup date and try a sample restore where feasible. If a crucial password, authenticator or local file has no proven recovery path, complete that step before the reset, not afterward.
If you cannot verify a category independently, treat it as not yet protected. That conservative rule is especially useful for local app data and authentication credentials, which are harder to recreate than downloadable apps.
This page is about backup coverage
This guide is organized around the data and access categories worth checking before a factory reset. It is designed as an inventory so you can compare what is on the device with what has actually been copied or synchronized elsewhere.
For the higher-risk case where a reset is already planned without a confirmed backup, use the factory-reset decision guide. That page focuses on the go/no-go checkpoint rather than the backup inventory itself.
Related consequence reports for “What to back up before a factory reset”
- What happens if you factory reset an iPhone?Devices & Accounts
- What happens if you factory reset a phone before backing it up?Devices & Accounts
- What happens if you lose access to your authenticator app?Security & 2FA
- What happens if you remove a Google Account from an Android phone?Devices & Accounts
- What happens if you sign out of iCloud on your iPhone?Devices & Accounts
- What happens if you remove Microsoft 365 from one PC?Devices & Accounts
Continue in this topic
Find more distinct decisions and source-backed consequence reports in the Devices & Accounts topic hub.
Official sources for “What to back up before a factory reset”
- Apple Support — Before you sell or give away iPhone/iPadOfficial source ↗
- FTC — Before you upgrade your phoneOfficial source ↗
- NIST — Digital Identity Guidelines: AuthenticationOfficial source ↗
- FTC — Use two-factor authenticationOfficial source ↗
- Google Account HelpOfficial source ↗
- Apple Support — Sign out of iCloudOfficial source ↗
- Apple Support — Change which apps sync with iCloudOfficial source ↗
- Microsoft Support — Uninstall Microsoft 365Official source ↗