Guide

How to back up a Mac app before updating

Updated June 10, 2026 · ~4 min read

Most Mac updates go fine. But every so often a new release crashes on launch, drops a feature you depend on, or breaks compatibility with a file or plugin. If the update replaced the old app in place, getting back to the working version can be surprisingly hard. A quick backup beforehand turns a bad afternoon into a thirty-second rollback.

When a backup actually matters

You rarely need this for App Store apps — you can re-download previous purchases through your Apple Account — or for most vendor-managed updaters that keep their own rollback paths. It matters most for direct-download updates, where a new DMG or ZIP overwrites the app in /Applications and the old build is simply gone.

Option 1: Make a manual copy

Simple and reliable. The downside is that it is easy to forget in the moment, and copies pile up without versioning.

Option 2: Time Machine

If Time Machine is running, you already have historical copies of your Applications folder. To restore, open the app's folder in Finder, enter Time Machine, step back to a date before the update, and restore the older app bundle. This works well but depends on having a recent backup from before you updated.

Option 3: Automatic, per-app backups

The most reliable approach is to back up automatically as part of the update itself, so it never depends on remembering. macCurrent can create a path-aware backup of an eligible app immediately before a direct replacement update, keep a configurable number of backups per app (up to three per app identity), and restore from the app's context menu. Backup readiness, update history, and restore activity stay attached to the specific app you are reviewing.

See the security model for how backups, restore, and cleanup are scoped, or download the free beta for Apple Silicon Macs on macOS 15 or later.

Related guides