"iOS 28 update requires 6.1 GB, you have 4.8 GB available" — and you're staring at a phone with 40 GB free according to the storage screen you just checked. This exact contradiction has confused iPhone owners every beta season for years, and it isn't a bug or Apple being cagey — it's a byproduct of how over-the-air updates actually work.
This guide covers why the advertised download size understates the real requirement, how to think about a planning figure before iOS 28 even exists, and exactly what to do when your phone refuses to budge.
Why the download size is not the space you need
When Settings shows a figure like "iOS 28 Public Beta — 5.8 GB," that number describes one thing: the compressed package your phone pulls from Apple's servers. It does not describe how much free space the installer needs, and those are very different quantities. Here's what actually happens on your phone during an update, roughly in order:
- The compressed package downloads and sits on your phone as-is — that's the number in Settings.
- The package gets unpacked into the files and system components it contains, which take up meaningfully more room uncompressed.
- The new system is staged alongside your current one, because iOS builds the update on a spare partition before committing to it — your old system stays intact and bootable until the new one is verified. That's why a failed update rarely bricks a phone: the fallback is right there.
- The old download and staging files get cleaned up after the swap completes.
For a window measured in minutes, your phone is holding the compressed download, the unpacked update, and enough working room to build and verify the new system — all at once. That's the real requirement, and it's why practical experience with iOS updates points to needing several times the advertised download size in truly free storage, not just slightly more than it. "I have exactly enough space" is the wrong goal — you want a healthy multiple of the download size, with room to spare, before you tap install.
A realistic planning figure — without inventing a fake one
You'll find pages stating a precise gigabyte figure for an iOS beta that doesn't exist yet. Ignore those. It's August 2026 as you're reading this, iOS 28 isn't due until June 7, 2027, and nobody has downloaded a real build to measure. Any exact number today is invented — reason from history instead, since Apple's updates have followed a consistent shape for years:
- Point updates (the x.1, x.2 releases through a cycle) tend to be smallest, often well under 2 GB.
- Major annual releases — the iOS 27-to-28 jump will be one — run larger, commonly multi-gigabyte, because a new major version touches far more of the system.
- Developer beta 1 of a new major version is typically the largest single download of the cycle, since it carries a full year's worth of new code and assets.
- Builds shrink slightly as the cycle progresses and Apple trims debugging instrumentation, though modestly compared to the jump between major versions.
The useful takeaway isn't a number — it's a habit: before you install any iOS 28 beta build next year, check the actual download size iOS shows on your device (our beta build tracker lists each build as it lands), then clear several times that amount in free space. That works regardless of the real figure, which is why it's more durable than a guess. For the mechanics of getting a build onto your phone, see our guides to installing the developer beta and installing the public beta.
"Update requires X GB" — but you have more than that free
This is the scenario behind most storage support-forum posts every beta season: iOS states a requirement, your Storage screen shows you comfortably exceed it, and the update still refuses. Two causes account for almost every case.
A previous update attempt left staging files behind
If an earlier download was interrupted — a dropped Wi-Fi connection, a low battery shutdown, you backed out partway through — iOS doesn't always clean up completely after itself. The partial download or partially staged update can sit on your device consuming space with no clearly labeled culprit, quietly reducing what's actually available even though nothing on your Home Screen looks different.
The requirement is measured at a different moment than your Storage screen
The "you need X GB" prompt is checked the instant you tap install, against whatever transient files already exist from the download that's begun. Your Storage screen, checked minutes earlier or later, can legitimately show a different number as caches and background processes shift things around. A gap of a few hundred megabytes between the two is normal and not worth chasing.
How to free space properly
If you're genuinely short on storage rather than dealing with a stuck leftover, here's the order that actually moves the needle — from most to least impactful.
Delete the stuck update first
Go to Settings → General → iPhone Storage, find the iOS update entry if one is listed, and delete it. This alone recovers several gigabytes on many phones and should always be your first move.
Offload apps you don't use daily
Still in iPhone Storage, tap into a large app you rarely open and choose Offload App. This removes the app binary but keeps its documents and data, and the icon stays on your Home Screen — reinstalling later restores everything. Games with large asset bundles are usually the biggest wins.
Empty Photos' "Recently Deleted"
Deleted photos and videos don't actually leave your phone for 30 days — they sit in Photos → Albums → Recently Deleted taking up the same room as before. Open it and select Delete All to reclaim that space immediately instead of waiting out the countdown.
Check Messages for the attachment hog it usually is
Years of photos, videos, and voice memos sent through Messages accumulate silently, and on a phone used daily for a while, Messages is routinely one of the single largest entries in iPhone Storage. Tap into it from the Storage screen to see the breakdown, and consider auto-deleting conversations after a year in Settings → Apps → Messages → Keep Messages.
Skip the "clear cache" apps entirely
Third-party storage-cleaner apps can't reach most of what's actually consuming your space — iOS sandboxes apps from each other's data and won't grant the system-wide access they'd need. At best they nag you toward a subscription; at worst they're just noise. The built-in iPhone Storage screen is the only tool you need, and it's free.
| What's consuming it | How to reclaim it | What you typically get back |
|---|---|---|
| Stuck or previous update download | Settings → General → iPhone Storage → delete the update entry | Substantial — often the single biggest recovery available |
| Rarely used apps with large asset bundles | Offload individual apps from iPhone Storage | Meaningful, varies a lot by app — games are usually the biggest |
| Photos "Recently Deleted" album | Photos → Albums → Recently Deleted → Delete All | Can be significant if you've deleted media recently |
| Messages attachments (photos, videos, voice memos) | Review the Messages entry in iPhone Storage; enable auto-delete after 1 year | Often one of the largest categories on a phone used daily for years |
| Browser and app caches | Usually self-managed by iOS; rarely worth manual intervention | Minor, and third-party "cleaner" apps can't do this safely anyway |
The "System Data" mystery
You free up space, install the update, check Storage again a day later — and a category called "Other" or "System Data" has ballooned to several gigabytes you swear weren't there before. This alarms people every cycle, and it's almost never worth acting on.
Right after any iOS update, your phone spends a day or two rebuilding indexes in the background: Spotlight reindexes every app and file, Photos re-analyzes your library, and Siri suggestions rebuild their model of your habits. That work generates temporary files filed under System Data while it's in progress — necessary housekeeping, not a leak.
Give it a day or two, ideally on Wi-Fi overnight, and the number normally settles back down on its own. Resist the urge to panic-wipe the phone chasing this figure — it resolves itself.
Updating via a computer instead
If you've offloaded everything reasonable and your phone still can't clear enough space — an older phone with small base storage and a large photo library, say — updating through a Mac or PC sidesteps the problem.
When you update or restore an iPhone connected to a computer via Finder (or iTunes on older systems), the download and staging happen primarily on the computer's storage, which almost certainly has far more room to spare than your phone does. The device itself only needs enough free space to receive and install the final result, not to hold every intermediate copy. It's also a faster, more reliable path for a first-day beta install where cellular or spotty Wi-Fi would otherwise make the over-the-air download crawl.
Before you do this — or any beta install — make sure you have a proper backup in place first. Our backup guide before the iOS 28 beta walks through creating an archived, computer-based backup, which is worth doing anyway since it's the same connection you'd use to update through a computer. For everything else around enrollment and installation, the main iOS 28 beta guide covers the rest.