Quick guide
The short answer
Start with App Store updates. Then check Homebrew apps, apps with a Check for Updates menu, and any developer update tools. For apps without an updater, visit the developer's website. Save your work and back up important files before installing.
Before you start
- Save your work and close the apps you plan to update.
- Check that your important files have a recent backup.
- Read the release notes for apps you rely on. A major update can change file formats, plugins, or licensing.
Keep a copy of an app before replacing it directly. That copy saves the program, not your documents or settings. See the backup guide.
1. Update App Store apps
- Open the App Store.
- Choose Updates in the sidebar.
- Choose Update next to an app, or Update All for the listed apps.
Update All applies only to apps installed from the App Store. You can turn on Automatic Updates in App Store settings.
2. Update Homebrew apps
If you use Homebrew, open Terminal and check which apps it manages:
brew update
brew list --cask
brew outdated --caskReview the list before installing. To update the eligible outdated casks, run:
brew upgrade --caskFor command-line tools, use brew outdated and brew upgrade without --cask. Some apps need extra checks. The Homebrew guide explains skipped apps and the --greedy option.
3. Check each app's own updater
Open apps that did not appear in the App Store or Homebrew list. Look for Check for Updates in the app menu or settings.
Some apps use Sparkle, an updater built into the app. Others use tools such as Microsoft AutoUpdate or Adobe Creative Cloud. Follow the developer's instructions for those apps.
4. Check developer websites
For apps without an updater, visit the developer's official website. Read the installation steps for the newer version. Avoid update links from unexpected popups or emails.
If the developer provides a checksum, you can compare it with the downloaded file. A checksum helps check that the download matches the published file.
Optional Terminal check for a downloaded file
Replace App.dmg with the name of your downloaded file. Compare the result with the developer's published SHA-256 value.
shasum -a 256 ~/Downloads/App.dmg5. Check that the updated apps work
Open each updated app before removing its backup. Check the features and files you normally use. A successful installation does not guarantee that a new version suits your work.
Start with apps you can do without briefly. Leave important work apps until you have time to check them carefully.
How macCurrent can help
macCurrent finds updates across several sources and installs supported updates. You can review where an update comes from and what will change, then install it or follow the action shown.
For supported direct updates, macCurrent can install the new version and save the old app first. It checks the download before replacing the app. Updates that need the App Store, an administrator, or the developer's own installer still need that step.
An optional setting can install supported updates after scheduled checks. It does not turn every update into an automatic installation. Read how update checks work, or follow the installation steps.
See the Acorn update walkthrough for one real example, including the saved old app and the version checked afterward. We checked this example ourselves, not every app or update method.
Frequently asked questions
Is there one button to update every Mac app?
No. App Store Update All covers App Store apps only. Homebrew and other apps use their own update tools.
Does brew upgrade --cask update every app?
No. It updates eligible casks managed by Homebrew. Other apps need the App Store, their own updater, or the developer's website.
Should I quit apps before updating?
Save your work and quit apps that will be replaced. Follow the updater's instructions if it handles quitting and reopening for you.
Can macCurrent install updates automatically?
It can install supported updates when the required checks pass. Other updates still need review or the App Store or developer's installer.