Is it safe to delete Xcode’s Archives folder?
- Partly. Archives of builds nobody runs any more can go. Keep the archive of every version people still use: Apple says to retain the archive of each build you distribute, because its debug symbols (dSYMs) are what make that version’s crash reports readable.
- What it costs you: for each archive you delete, the ability to add symbol names to that build’s crash reports on this Mac, and to export or upload that exact build again. Your source code isn’t in it.
- Does it come back? No. Archiving the same code again makes a new build with a different build UUID, and a dSYM only works with the binary it was made with.
- SiftMac’s verdict: You decide
1. What it is
When you choose Product › Archive, Xcode builds your app for release and saves the result as an archive, a .xcarchive bundle that appears in the Archives organizer (Window › Organizer). From there you validate it, upload it to App Store Connect for TestFlight or the App Store, or export it to distribute some other way.
Release builds keep their debug symbols in separate dSYM files instead of inside the app, and when you archive, Xcode gathers the app’s binaries and all their dSYMs into the archive. Each binary and its dSYM share a build UUID. Apple’s documentation points out that building the same source with a different Xcode version or different build settings gives a different UUID, and only an identical pair works together.
So an archive is the one copy of two things you can’t make again:
- The exact build you shipped, which the organizer can export or upload again.
- Its dSYMs, which Xcode and tools like
atosuse to turn the memory addresses in a crash report into function names, files and line numbers.
2. Where it is
~/Library/Developer/Xcode/Archives
Xcode files archives in one folder per day you archived, and names each archive after the scheme with the date and time. Finder shows an archive as a single item; Control-click it and choose Show Package Contents to see the build in Products and the symbols in dSYMs. In Xcode, Window › Organizer › Archives lists the same archives grouped by app, with their version and build numbers.
3. How big it gets
An archive is roughly your release build plus its dSYMs, so apps with many frameworks or large assets make bigger ones. Xcode doesn’t remove old archives on its own, so an app you’ve shipped often leaves a long trail of them. To see the total, and which days take the most:
du -sh ~/Library/Developer/Xcode/Archives
du -sh ~/Library/Developer/Xcode/Archives/* | sort -h
4. How to delete it safely
- Decide which versions still matter: anything people still run from the App Store or TestFlight, and builds you sent to customers or testers directly. Keep those archives.
- In Xcode, choose Window › Organizer and click Archives. Pick an app in the sidebar to see its archives with version and build numbers.
- Select the archives of versions nobody uses any more and delete them. Or, with Xcode quit, move whole dated folders from
~/Library/Developer/Xcode/Archivesto the Trash in Finder and empty it.
If you might still look at crashes from a build but want the space, keep just its symbols: open the archive’s package contents and copy the dSYMs folder somewhere you’ll keep, named by version and build. When Xcode can’t symbolicate an address, Apple suggests finding the matching dSYM with Spotlight, so keep the copy in a folder Spotlight indexes.
If you uploaded symbols with a build to App Store Connect, the crash reports Apple delivers to Xcode’s Crashes organizer already carry symbol names. A crash-reporting service you use may still need the dSYMs, so check it has them before deleting the archive.
5. What happens afterwards
- Deleted archives disappear from the Archives organizer. Your projects, your source code and the builds already on Apple’s servers aren’t affected.
- Crash reports from that build still arrive, but Xcode only adds symbol names to them if the matching dSYM is still on your Mac.
- You can’t export or upload that exact build again. Archiving the same code again makes a new build.
- The folder fills again with every Product › Archive, so it’s worth a look after each few releases.
6. What to clear instead
The other big folders in ~/Library/Developer come back on their own: DerivedData rebuilds with your next build, device support files are copied again when you plug in a device, and old simulators can be removed with Xcode’s own tools. Start with those before you touch archives.
Questions
Will deleting an archive remove my app from the App Store or TestFlight?
No. Once a build is uploaded it lives on Apple’s servers. The archive is your local copy, used to export that build again and to read its crash reports.
Can I keep the dSYMs and delete the rest?
Yes. The dSYMs folder inside the archive is what symbolication needs. Copy it out, label it with the app version and build number, and keep it somewhere Spotlight indexes before you delete the archive.
What about archives I never distributed?
If nobody outside your Mac ever ran a build, there are no crash reports to read from it, so its archive can usually go.
Is Archives the same as DerivedData?
No. DerivedData is build output Xcode makes again from your code; deleting it only costs a slower next build. An archive is a finished build you can’t recreate exactly, which is why it’s You decide rather than Rebuilds.
How SiftMac handles it. SiftMac leaves archives alone: its Developer files category lists old DerivedData, device support files and simulators, never Archives. The space map shows how much the folder takes, so you can decide what goes in Xcode’s Organizer.
Download SiftMac · scanning is free, and so is your first 2 GB of cleaning · See how it works