BlanciPhone Backup Stuck at 0 KB, and Storage Numbers That Can't Be True
Someone posted a screenshot recently: a 128 GB iPhone, and the storage screen reporting 504.8 GB of app data. Twenty-three people replied with backup advice. Nobody mentioned that the number was impossible.
It's the most useful signal on the screen. A phone cannot hold four times its own capacity, so the figure isn't a measurement — it's a symptom. The storage index is corrupted, and once you know that, three separate problems collapse into one explanation.
What the index is, and how it breaks
iOS doesn't add up your files every time you open the storage screen; that would take far too long. It maintains a running database of what exists and how big it is, and reports from that. Same database that tells iCloud what needs backing up.
When that database desynchronises from the actual filesystem — usually after an interrupted restore, a failed update, a migration between devices, or a disk that filled completely mid-write — you get entries for files that aren't there, double-counted items, or sizes that are simply wrong. Nothing crashes. iOS keeps trusting the database, and the database is lying.
Why the backup hangs at 0 KB
Before a backup starts transferring, iOS calculates the total size from that same index. With a corrupted index the sum is nonsense — 504 GB against a 5 GB iCloud plan, say — so the process either refuses to begin, or begins, immediately hits a file the index describes but the disk doesn't have, and stalls.
What you see is a progress bar at 0 KB, or 'Backup Failed' with no explanation, or a backup that runs all night and completes nothing. It is not your Wi-Fi, not your iCloud plan, and no amount of retrying will change it. That's why the usual advice does nothing here.
How to confirm it in a minute
Open Settings → General → iPhone Storage and look for internal contradictions rather than large numbers:
- Any figure larger than the phone's capacity. The clearest possible proof. A single app claiming more than the device holds needs no further diagnosis.
- The bar and the list disagree. Add up the coloured segments, compare to the app list below. They should roughly match; a large gap is index drift.
- A category that never changes. Delete several gigabytes and watch. If the number is identical afterwards, it isn't being measured — it's being recalled from a stale record.
- 'System Data' that swallows everything. This category is partly a genuine catch-all and partly where mis-indexed files accumulate. On its own it proves nothing; alongside the signs above it fits the pattern.
One thing that isn't this problem: space that doesn't free after deleting photos. That usually has a much more ordinary cause — either Recently Deleted still holding everything for 30 days, or an iCloud plan too small for your library. Rule both out before concluding anything is corrupted.
The fix, in the only safe order
A corrupted index isn't repairable from inside iOS. There's no rebuild command. The database is regenerated when the system is written fresh, which means erase and restore — and the whole difficulty is getting a trustworthy backup first, from a phone whose backup mechanism is the thing that's broken.
1. Back up over a cable, not to iCloud. Connect to a Mac or PC — Finder on modern macOS, iTunes or the Apple Devices app on Windows — and back up locally. A wired backup transfers files directly rather than working from the size calculation that's failing, so it frequently succeeds where iCloud hangs. Tick the option to encrypt the backup: it's the only way Health data, saved passwords and Wi-Fi networks come back with you.
2. Verify it exists before you erase anything. In Finder's device screen, check the backup is listed with today's date and a plausible size. This takes ten seconds and is the only thing standing between you and a very bad afternoon.
3. Erase, then restore from that backup. Settings → General → Transfer or Reset iPhone → Erase All Content and Settings, then restore from the local backup during setup. The index is rebuilt from what's actually on disk, and the numbers become real again.
4. Check the storage screen before restoring apps and photos. On the freshly erased phone the figures should be small and sane. If something is still impossible at that point, the problem is hardware and it's an Apple Support conversation, not a software one.
What not to bother with
Restarting doesn't rebuild the index. Neither does toggling iCloud Backup, signing out and back in, or deleting and re-downloading apps — that last one can even make things worse by adding fresh entries to a database that's already wrong. Resetting All Settings leaves the filesystem untouched, so it changes nothing here either.
The wired backup is the step people skip, and it's the one that matters. Everything else in this list is optional.
Afterwards
Interrupted writes on a disk that's completely full are one of the reliable ways to get here in the first place, which makes chronic 99%-full living an actual risk rather than just an annoyance. Some headroom is cheap insurance.
For most people the headroom has to come out of the photo library, because that's where the space went. That's a long tail of small decisions rather than one big cleanup, and it only works if you never get asked about the same photo twice — which is the entire idea behind Blanc. If you'd rather start with the mechanics, what's actually eating your iPhone storage is the place to begin.