Relaunch
Download Buy
Blog / Privacy and maintenance

A large app library does not explain memory pressure by itself

Installed app count describes your library. Current memory pressure depends on running work, so inspect active applications before choosing a cleanup action.

By Nicholas Gaston, maker of Relaunch ·

Separate installed capacity from active work

A grid page can contain many apps that are not running. Those installations use storage, but the number of icons is not a live measure of their memory use. A single active tool doing substantial work can matter more than several idle installations.

Read the current view instead of guessing

Use Relaunch’s Memory light and running-app memory information when pressure is the question. Save work before quitting software you no longer need. The app’s size on disk and its current active resources are different numbers.

An application not brought forward recently may still be exporting, uploading or doing another background job. Review its actual task before interpreting an idle-app suggestion as a command to stop it.

Use Cleanup for the disk-space question

When storage is the issue, inspect installation sizes and unused-file candidates. Hiding a launcher icon changes neither the installed app’s size nor an active process. Choose whether you need a calmer view, more disk space or fewer running tasks before acting.

Describe the pressure with context

  1. Note which work was running.
  2. Inspect the Memory light and app list.
  3. Record Relaunch and macOS versions for support if the view seems wrong.
  4. Avoid changing many unrelated settings before testing the same workload again.

Put it into practice.

More on privacy and maintenance.

Make room for your apps.

Every feature. One-time purchase. Made for macOS 26.

Find your plan