Help and privacy
iPhone Storage vs iCloud: What's Taking Up Space?
A phone can run out of space while iCloud still has room. A closer look at installed apps, offline maps, photo metadata, and temporary files helps explain which number you are seeing and what to do next.
Free space in iCloud is not free space on the phone
You can have plenty of room in iCloud and still see an iPhone storage warning. The two numbers describe different places: storage inside the device and storage associated with your iCloud account. Buying more of one does not increase the capacity of the other.
That distinction becomes particularly noticeable while traveling. Photos accumulate, offline apps keep the information needed without a connection, and an export or download may leave a local copy behind. Before deleting anything, work out which storage is full and what the large items actually contain.
Apple's explanation of device and iCloud storage is a useful starting point. On the phone, open Settings > General > iPhone Storage. For iCloud usage, open Settings > your name > iCloud. Treat those as separate inventories.
Why an offline travel app needs storage
Mapsake does not need to duplicate your original photo library to build a travel map. It still needs more than a list of country names.
The installed app contains its code, interface assets, translations, an offline place directory, and geographic data. That reference data lets the app search for places and resolve supported photo coordinates without sending every point to a remote geocoder. It takes space even before you import a trip.
Your own Mapsake data adds another layer: saved places, dates, notes, trip records, photo metadata, and the indexes that make those records useful. A reference to a photo and its location is much smaller than another original image, but a large library can still produce a meaningful metadata store.
There can also be caches and temporary files. For example, Immich previews may use a local thumbnail cache, and preparing an export creates a file before you choose where to keep it. These categories have different jobs and different rules for removal.
Read the categories before reading the total
The important distinction is what a file represents:
- Installed app and reference data: the software and bundled information that make the app work. Removing your travel history does not shrink this part of the installed app.
- Saved travel data: the authoritative record of your places, trips, and edits. This is the part to preserve and back up.
- Photo metadata and derived indexes: information used to connect the source library with the atlas. It is not simply a second copy of every original photo.
- Caches: material the app may be able to regenerate or fetch again. Rebuilding it can still take time or require a connection.
- Temporary copies: files created for a particular operation. Some are disposable after that operation; others may belong to a pending import, feedback draft, or export you still need.
An unfamiliar filename or a large ZIP file is not enough evidence that something is safe to delete. “Temporary” describes where a file is stored, not necessarily whether its work has finished.
Inspect Mapsake's storage without changing it
Mapsake's Storage inspector is available under Settings > Advanced, and from Storage Consumption. It measures the app's accessible files and groups them by their role.
- Ouvrir Storage inspector and let the scan finish.
- Review the breakdown to see which categories account for the space.
- Check for a partial-report notice. Some protected files may not be measurable.
- Utilisez Refresh when you want a new measurement after an operation or cleanup.
The scan does not open file contents, upload the inventory, or delete files. Sending diagnostic information is a separate feedback action with its own controls.
The result may not exactly match iPhone Storage. The operating system and an app do not necessarily see or classify the same files, and inaccessible locations can leave the app's inventory incomplete. Use the inspector to understand Mapsake's categories rather than expecting its total to reproduce every byte attributed by iOS.
What the cleanup control can remove
The inspector can offer Remove old temporary copies when it finds eligible files. The cleanup is deliberately narrow: recognized Mapsake sharing and raw-export temporary copies older than seven days, subject to another check when you confirm removal.
Files that changed since the scan can be kept. Unknown archives, pending imports, feedback, databases, photos, and manually added places remain protected. Copies you intentionally exported to Files are separate from the temporary copies handled by this control.
The cleanup result reports how many eligible files were removed and how many were kept after rechecking. There is no universal amount you should expect to recover. A device with old export or sharing copies can have more to reclaim than a device that never created them.
Recent releases also reduce the app's bundled data and retire recognized obsolete sharing scratch files. Those improvements do not require removing destinations or narrowing your travel history.
What about Optimize iPhone Storage?
If Photos is the large category, Apple's Optimize iPhone Storage option can keep smaller local versions while full-resolution originals remain in iCloud Photos. Originals may need to download when you use them. This is a Photos setting, separate from Mapsake's cleanup controls. Apple describes the options here.
Before a trip with limited connectivity, think about which photos and documents you want available on the device. Space saved through cloud storage can come with a later download requirement.
Deleting a photo is also different from optimizing its local copy. With iCloud Photos, deleting an item can propagate to the other devices using that library. Do not use deletion as a substitute for understanding where the originals are stored.
Offloading and deleting are different actions
iPhone Storage may offer Offload App et Delete App. Offloading removes the app while keeping its documents and data; deleting the app also removes its related data. Apple's storage guide explains the distinction.
That makes deleting and reinstalling a poor first troubleshooting step for a private travel record. First understand the storage breakdown and make a separate export of any data you need to preserve. Do not assume that turning on sync proves every local change is already recoverable elsewhere.
The inspector's targeted temporary-copy cleanup is a different operation from either system action. Its purpose is to remove recognized leftovers while leaving the travel record in place.
Start with one measured change
If you are trying to free space before a trip, record the starting figures, identify the large category, and make one relevant change. Recheck after it finishes. This makes it easier to tell whether the space came from photos, an app update, downloads, or old temporary copies.
For Mapsake, the useful question is not just “why is this app large?” It is which part is the installed offline atlas, which part is your history, and which part is a disposable copy. Once those are visible, the next step can be specific instead of a guess.