Short answer: System Data keeps growing because it is the bucket iOS uses for everything that does not belong to a named category — caches, logs, the Spotlight index, offline media, leftover app container files — and it grows by design as you use the phone. Apple publishes no normal size for it, so every "it should be under X" figure you read is an estimate. Judge yours with three questions instead: does it match how you use the phone, does the space come back, and is low space actually blocking you.
System Data is a bucket, not a folder
Open Settings → General → iPhone Storage and read the bar. Every other row maps to something you can name: Apps, Photos, Media, Mail, Messages, Books, iCloud Drive. The row labelled System Data is what remains after those are accounted for — which is exactly why it has no delete button and no folder you can open.
Apple's own storage documentation describes that remainder as "non-removable logs and caches, Spotlight index, and system data, such as Keychain and CloudKit database", alongside the non-removable assets the system needs, such as Siri voices, fonts and dictionaries (How to check the storage on your iPhone and iPad). In practice the bucket also absorbs app caches, offline media kept so playback works without a network, message attachments, and container leftovers from apps you updated, offloaded or deleted.
Two consequences follow from that definition, and they carry the whole article:
- It is defined by exclusion. Nothing deliberately "puts things into System Data"; things land there because they are not Apps, Photos, Media, Mail or Messages. Apple even notes on the same screen that cached and temporary data might not count as usage at all. The figure is a calculation, not an itemised ledger — which is why arguing about whether a particular number is acceptable is arguing about an approximation.
- It is not a to-do list. A large figure is not the same thing as a problem. Apple's guidance for the same bucket is short and unbothered: to free up space, your device removes cached and temporary files, so you don't have to.
For where each storage row's contents actually go, see what the "Other" category is.
Why it grows: three ordinary reasons, and one that is not
Growth is normal and has ordinary causes. They stack, which is why the figure can climb quickly for a week and then flatten.
- Apps cache as they work. Video, map and social apps write images, tiles and stream buffers so the next open is fast. Apple's description of these files is that the device creates them when you stream or view content so it loads faster the next time — and that the device removes them when it needs more space. More use means more cache, and a cache cleared today is often refilled within weeks.
- The system rebuilds indexes. After an update, a restore, or a large import of photos, the Spotlight, Photos, Mail and Messages indexes are rewritten, and old and new copies can coexist while that happens. That is space held by work in progress, released when the work finishes — days rather than minutes on a full library. It is the same background work that makes a new phone warm: see why a new iPhone runs hot and the settling-in period after an update.
- You put some of it there yourself. Offline playlists, downloaded shows, saved map regions, attachments you kept, and the full-resolution originals of your photo library when iCloud Photos is set to keep them on the device. This is real content rather than junk: deleting it frees space, but it was never a leak.
- What is not an explanation: a "leak". If the figure climbs while you install nothing, shoot nothing and download nothing — and the space never comes back — that is a signal worth investigating. It is the exception, not the default reading of a growing number.
When iOS reclaims it, and why it can look stuck
Reclaiming is not something you do to the phone. It runs on a trigger, and knowing the trigger explains most of the confusion.
- The trigger is need. Apple's wording is that the device removes these cached and temporary files when it needs more space. As storage gets tight, iOS trims the coldest caches first and free space recovers without you touching anything.
- That is why a high figure can sit still for weeks. With plenty of free space there is no pressure to trim, so nothing gets trimmed — not because the space is stuck, but because nothing has asked for it. "It never goes down" frequently means "it was never needed".
- Reclaiming lags behind writing. Tidying competes with whatever you are doing in the foreground, so most of it happens while the phone is idle, locked, on power and on Wi-Fi. A phone that is never left charging overnight gives those jobs less room to run. (This is a practical observation, not an Apple figure.)
- Part of the bucket cannot be reclaimed at all. Read Apple's list again — Siri voices, fonts, dictionaries, the Keychain database. A meaningful share of the total is permanent furniture, so a target of "near zero" was never achievable.
How to judge your own number, when no range is published
The honest starting point: Apple documents what System Data contains and states that the device clears cached files itself, but publishes no size range for it. Any figure presented as normal — "5-10 GB is fine", "over 20 GB is a problem" — has no Apple source. It is one person's phone, or an estimate dressed up as a specification. The same reasoning applies to any "healthy ceiling" you see quoted for System Data specifically.
So compare against things that are genuinely knowable about your phone:
① Does it match your own usage? A phone that streams long video, navigates and keeps map data offline writes far more cache than one that mostly messages and reads. Compare your figure with your own figure a week ago; comparing it with a stranger's screenshot is meaningless, because the total scales with your storage size, your apps and your habits.
② Does the space come back? The decisive property is reversibility, not size. Leave the phone locked, on power and on Wi-Fi overnight — ideally once an update or restore is a few days behind you — and read the figure in the morning rather than mid-afternoon. A number that drifts up and down, or drops after a heavy week, means the system is doing its job. One-way growth, with nothing installed and nothing new downloaded, is the only pattern that counts as a signal.
③ Is low space actually blocking you? If you can still install an app, take photos and install a system update, the number is not a problem, whatever it says. If free space blocks those things, you have a storage problem — and a growing figure is one of its symptoms, not its cause. Start from why free space affects speed instead of from the number.
④ Does it arrive with sustained heat and clearly faster drain? Then the story is probably background work that has not finished rather than storage at all, and it belongs with the post-update settling period.
Five "clean System Data" tricks that do nothing or backfire
This is the part search results get wrong most often, because most of the advice is aimed at a folder that does not exist.
① Cleaner apps and configuration profiles. System Data is calculated by exclusion, so no app can enumerate it, let alone delete it. A cleaner cannot deliver what it promises; a "cleaner" that asks you to install a configuration profile is requesting access to your device in exchange for nothing. Skip both.
② Deleting folders you do not recognise in the Files app. Apple counts content in the "On My iPhone" directory under Apps, not under System Data. So this deletes your documents while the figure you were trying to move does not budge: two losses, no gain. The full do-and-don't list is in Can you clean System Data?.
③ Force-quitting every app from the app switcher. It frees nothing on disk. Worse, an app you killed comes back cold and rebuilds its cache from scratch, so the ritual can raise the number and spend battery doing it. iOS manages memory itself; the app switcher is a list of recent apps, not a list of things wasting space.
④ Erasing and restoring from a backup. A restore returns your app data, and the apps begin filling caches again within days, so the number you erased is largely rebuilt. Only setting the phone up as new changes the baseline, and that costs you your data. Keep erase-and-restore for a phone whose free space genuinely blocks use — not for a figure that looks alarming.
⑤ Turning off features such as Background App Refresh or Siri to shrink it. These change what the phone does next; none of them deletes what is already stored, and the non-removable assets Apple lists — voices, fonts, dictionaries — cannot be switched off at all. Turning off Background App Refresh buys you staler content, not a smaller bucket.
There is a quieter sixth: aiming at a number you read online. If the target came from a forum thread, you are optimising toward somebody's estimate. Watch your own trend instead.
What genuinely moves the number
Ordered from gentlest to most disruptive. Stop as soon as the phone stops complaining — the goal is comfortable free space, not a small figure.
- Time, under the right conditions. Locked, on power, on Wi-Fi, overnight: that is when reclaiming and index rebuilds get their best chance.
- Use each app's own controls. Download lists in video and podcast apps, storage screens inside messaging apps, offline map regions you no longer travel through.
- Delete and reinstall the app holding the largest cache. In the storage list, open the app and read its Documents & Data figure. Confirm anything important is synced first, because reinstalling removes local data.
- Empty Photos → Recently Deleted. Deleted items keep holding space for up to 30 days until you clear them.
- Check the iCloud Photos setting. "Download and Keep Originals" keeps the full library on the device; "Optimize iPhone Storage" moves originals to iCloud and leaves smaller versions locally.
- Keep free space in reserve. This project's rule of thumb is 10-15% free — not because it lowers System Data, but because headroom is what lets iOS trim caches and do its scratch work without making you wait: see how much free storage an iPhone needs. Treat that figure as a rule of thumb, not an Apple number.
- Erase and set up as new — last resort only. When space genuinely blocks daily use, and with the understanding that it means starting over.
Expect it to come back. Caches are rebuilt by exactly the activity that filled them, so a figure drifting upward over a month is the design working, not the cleaning failing.
A closing note on versions: the bucket, the trigger and the tricks that fail are the same on any iOS 17 or later, which is why this page is about the framework rather than one release. What changes from release to release is timing and scale — that is what the version-specific pages are for: System Data huge after iOS 27 and how to reduce System Data on iOS 27 read this same framework against a single release.