Is it safe to delete iOS files on your Mac?

Yes, for four of the five things people mean by “iOS files” on a Mac. The fifth — a device backup — is only safe once you’ve confirmed which iPhone or iPad it belongs to and which date it’s from, because the folder holding it won’t tell you either one on its own. Below is the map of all five piles, a deep look at the two nobody else writes about — backup identity, and the software-update files still sitting in a folder named after an app that hasn’t shipped on macOS in years — and what each deletion actually costs to reverse.

“iOS files” on a Mac are five different piles, not one

Search “ios files mac” and most results are built around a single meaning — usually the device-backup folder. That’s one pile. There are four more, and confusing them is exactly how someone deletes the wrong thing. Here’s the full set, with a one-line verdict for each.

Every one of these piles already has decent writing somewhere on the web — MacPaw alone covers backups and software-update files in two separate, accurate how-tos (last updated August 18, 2025). What’s missing, including there, is the identity check before you delete a backup, and a straight answer on what’s actually inside that software-update folder rather than “itunes leftovers.” That’s the gap the next two sections fill.

Before you delete a backup, confirm which device and which date it is

Open ~/Library/Application Support/MobileSync/Backup and every folder inside it is named with a long device identifier — a UDID, not “John’s iPhone.” Nothing in the folder name tells you which phone made that backup, or when. That information exists, it’s just one level deeper: each backup folder contains an Info.plist file recording metadata about the device and the backup itself, alongside Manifest.plist and Status.plist (iMazing’s technical breakdown of the backup format). Reading it by hand means opening the folder and finding that file yourself.

Finder does the same lookup for you, in plain language. Connect a device, select it under Locations, and click Manage Backups — the sheet that opens lists every backup on the Mac by device and date, not by folder name (Apple’s own instructions for locating and managing backups cover this exact screen). That’s the list to work from, not the raw folder view in Finder.

One detail changes the math further: unless you’ve archived a backup, Finder replaces it the next time that device backs up again — a lock icon in Manage Backups marks the ones you’ve protected from being overwritten (MacRumors’ guide to archiving iPhone backups). So for most people, “the backup for my old iPhone” is one folder, not a history — there’s nothing else of that device’s local backup to lose, only iCloud’s copy, if one exists.

We already cover the actual safety verdict — when an old backup is genuinely safe to remove — in what’s safe to delete on a Mac; the mechanics above are what that verdict depends on, and neither page needs to repeat the other.

Deleting through Finder vs. deleting the raw folder yourself

Manage Backups’ Delete Backup button removes exactly the device-and-date pair you selected from that list, and nothing else. Deleting the raw folder yourself skips that lookup entirely — you’re choosing based on a UDID string, a modification date in Finder’s list view, or a guess. Guess wrong on a Mac that’s backed up three different phones over the years, and you can delete the only copy of the wrong one.

It isn’t a hypothetical failure mode, either. Apple’s own community forums have documented cases where deleting the entire Backup folder — rather than one backup folder inside it — left Finder unable to complete the next backup attempt at all, throwing an unrelated-looking error until the folder structure was rebuilt (Apple Support Communities, 2021). The fix exists. It’s still an avoidable afternoon.

Xcode’s DeviceSupport and Simulator files — the developer piles, already covered

If you’re the kind of person who has an iPhone plugged into Xcode more often than not, DeviceSupport symbols and Simulator runtimes are the two piles that actually matter to you — and we’ve already written the deep version: the exact paths, what Xcode rebuilds automatically, and the FAQ answer on whether it’s safe to clear the Simulator’s DeviceSupport files specifically. Short version, so you don’t have to click through for the summary: both are safe to clear for anything you’re not actively testing against, and Xcode fetches what it needs again the next time it needs it.

.ipsw files: the software-update pile macOS never asks you to clean up

Every time you install an iOS or iPadOS update, or restore a device, through Finder — or through Apple Configurator, which some IT teams still use — rather than over the air on the device itself, the full firmware file for that update, an .ipsw, downloads to your Mac first. It lands in ~/Library/iTunes/iPhone Software Updates or ~/Library/iTunes/iPad Software Updates, depending on the device — a folder path that survives from the iTunes era even though standalone iTunes hasn’t shipped on macOS since Catalina; Finder just kept using the same address. MacPaw’s own guide to these files documents the identical path, and current Apple Support Community threads on the same folder corroborate it.

These files are not small. One Mac user restoring an iPad in 2026 reported a single .ipsw close to 10 GB in a MacRumors Forums thread; iPhone firmware files typically run a few gigabytes smaller. Nothing in Finder or macOS clears them once the update finishes successfully — they sit there until you delete them yourself, the opposite of a few older, now-outdated forum answers claiming no files remain after an install. If you’ve ever updated a device through Finder, even once, that folder is worth a look — it can hold firmware for iOS versions nobody on your Mac runs anymore.

Deleting them costs nothing beyond a re-download, and only if you update or restore through Finder again later — Finder fetches a fresh copy automatically when it needs one. Teams using Apple Configurator for device restores keep a separate cache of the same kind of file, documented at ~/Library/Group Containers/K36BKF7T3D.group.com.apple.configurator/Library/Caches/Firmware (mrmacintosh’s Apple Silicon restore-file reference) — worth checking too if you manage more than one device.

One thing this isn’t: your Mac’s own macOS installer app, the roughly 12–16 GB “Install macOS [name].app” that lands in Applications when you download a full installer. That’s a different file for a different operating system, and it deletes itself once installation finishes — nothing to clean up there at all.

What each of these actually costs to get back

What not to touch, even inside this narrower list

Three specific situations, not the general system-file warnings we’ve covered elsewhere: a backup for a device that’s mid-restore or mid-migration right now — Migration Assistant and Finder both hold a reference to it while the process runs, and pulling it out mid-copy is how you end up starting over. An .ipsw file Finder is actively downloading or verifying — let the progress bar finish before touching anything in that folder. And the one genuinely irreversible case from the table above: a local backup that’s the only copy left of a device you don’t own anymore and that was never in iCloud. Everything else on this page costs you time, not data.

Why System Data won’t shrink the moment you delete these

Delete a stale backup or an old .ipsw file and the “System Data” number in Storage settings often doesn’t move right away — it updates on its own schedule, not the instant you empty the Trash. That’s a separate, already-answered question about how macOS counts and refreshes this category; see our full explainer on what’s actually inside System Data for the rest of it.

If you’d rather have this named for you than go hunting through four different folders, that’s the job SwoopByte Disk is being built for — a free System Data breakdown that names stale iOS device backups directly, with the device and a real size, instead of a folder full of hashes.

FAQ

How can I tell which iPhone or iPad a backup belongs to on my Mac?

Open Finder, select the device under Locations, and click Manage Backups — the list shows every backup by device and date, pulled from the Info.plist file inside each backup folder. The folders themselves are named with a device identifier, not a readable name, so this list is the fastest way to check without opening files by hand.

Is it safe to delete iOS software update (.ipsw) files from my Mac?

Yes, always. These files are downloaded once to install or restore an iOS or iPadOS device through Finder, and nothing on your Mac depends on them afterward. Deleting them only costs a re-download, and only if you update or restore a device through Finder again later.

Does deleting a local iPhone backup on my Mac also delete it from iCloud?

No. A local backup at ~/Library/Application Support/MobileSync/Backup and an iCloud backup are stored in completely separate places. Deleting one has no effect on the other.

What happens if I delete the wrong backup folder in MobileSync by hand?

You lose that backup permanently, with no undo beyond the Trash — and Apple’s own community forums have documented cases where deleting the entire Backup folder, rather than one folder inside it, left Finder unable to complete the next backup attempt at all. Use Finder’s Manage Backups list instead of guessing from folder names.

Why does Finder only keep one backup per iPhone instead of every one I’ve made?

Because an unarchived backup gets replaced the next time that device backs up again. Right-click a backup in Manage Backups and choose Archive to keep it permanently alongside future backups, marked with a lock icon.

Related guides